30f9b9a729
* feat: v2.0 skill renames and CRO consolidation BREAKING CHANGE: Users must reinstall skills after this update. ## Skill Renames (16) - ab-test-setup → ab-testing - analytics-tracking → analytics - aso-audit → aso - competitor-alternatives → competitors - email-sequence → emails - free-tool-strategy → free-tools - launch-strategy → launch - onboarding-cro → onboarding - paywall-upgrade-cro → paywalls - popup-cro → popups - pricing-strategy → pricing - product-marketing-context → product-marketing - referral-program → referrals - schema-markup → schema - signup-flow-cro → signup - social-content → social ## Consolidations (1) - page-cro + form-cro → cro (form content in references/form.md) ## Why 2.0? - Shorter, cleaner skill names - Consistent naming (no -strategy, -setup, -cro suffixes) - All cross-references updated across 100+ files Total skills: 40 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix(v2.0): update evals for renamed skills, fix validate script, clear warnings - Update 32 evals.json files to reference new skill names (page-cro → cro, product-marketing-context → product-marketing, etc.) — these were missed in the initial v2.0 rename pass since only SKILL.md and marketplace.json were updated. - Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk so frontmatter extraction works on macOS. - Move Copy Editing Checklist (56 lines) to references/checklist.md to bring copy-editing SKILL.md under the 500-line limit (508 → 457). - Add "see X" pointers to marketing-psychology description for skill discovery (cro, pricing, copywriting). - Update skill-request.yml issue template placeholder (page-cro → cro). All 40 skills now pass validation with zero warnings. * fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md Adds 48 new eval cases (6 per skill) for skills that previously had no evals: aso, co-marketing, community-marketing, competitor-profiling, directory-submissions, image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases). Strips leftover frontmatter from skills/cro/references/form.md — it was inherited from the old form-cro SKILL.md before consolidation. Reference files don't need frontmatter. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): rename paid-ads → ads One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates the skill directory, SKILL.md frontmatter, evals.json, README skill table, the v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in related skills (ad-creative, aso, competitor-profiling, customer-research, lead-magnets, marketing-ideas) plus the tools/integrations guides. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside each SKILL.md was still on 1.x. That mismatch would have caused the update-check flow to perpetually report 'update available' since it compares VERSIONS.md against local SKILL.md metadata versions. Caught by codex review (P1). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): add legacy product-marketing-context.md filename fallback Before this fix, users upgrading from v1.x who had a `product-marketing-context.md` file would lose automatic context loading — every skill only checked the new `product-marketing.md` filename. Now all 40 skills also accept the legacy filename (in either `.agents/` or `.claude/`), and the README migration command covers both legacy and current filenames. Caught by codex review (P1 + P2). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): re-sort README skills table alphabetically, fix ads box width The skills table had a few entries out of alphabetical order from the renames (co-marketing was after cold-email, ads was at the renamed position). Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the ASCII flow diagram to keep the box width consistent. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array README upgrade guide now includes: - A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so users don't end up with both old and new folders side-by-side after upgrading - The full v1 to v2 rename map for reference - Existing product-marketing-context.md migration steps (preserved) sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json -- Claude Code's plugin schema discovers skills via the `skills/` directory, and the explicit array was failing validation. The script now refreshes the description count and strips the stale array if present. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
4.6 KiB
4.6 KiB
PartnerStack
Partner and affiliate program management platform for SaaS companies with deal tracking, rewards, and multi-tier partnerships.
Capabilities
| Integration | Available | Notes |
|---|---|---|
| API | ✓ | Vendor API v2 for partnerships, deals, customers, transactions |
| MCP | - | Not available |
| CLI | ✓ | partnerstack.js |
| SDK | - | No official SDK; REST API with Basic Auth |
Authentication
- Type: Basic Auth (Vendor API)
- Header:
Authorization: Basic {base64(public_key:secret_key)} - Get credentials: Vendor dashboard > Settings > Integrations > PartnerStack API Keys
- Note: Separate Test and Production API keys. Test transactions can only be added to customers created with Test keys.
Common Agent Operations
List partnerships
GET https://api.partnerstack.com/api/v2/partnerships?limit=25
Authorization: Basic {base64(public_key:secret_key)}
Create a partnership
POST https://api.partnerstack.com/api/v2/partnerships
{
"email": "partner@example.com",
"group_key": "affiliates",
"first_name": "Jane",
"last_name": "Smith"
}
List customers
GET https://api.partnerstack.com/api/v2/customers?limit=25
Create a customer (attribute to partner)
POST https://api.partnerstack.com/api/v2/customers
{
"email": "customer@example.com",
"partner_key": "prtnr_abc123",
"name": "John Doe"
}
Record a transaction
POST https://api.partnerstack.com/api/v2/transactions
{
"customer_key": "cust_abc123",
"amount": 9900,
"currency": "USD",
"product_key": "pro_plan"
}
List deals
GET https://api.partnerstack.com/api/v2/deals?limit=25
Create a deal
POST https://api.partnerstack.com/api/v2/deals
{
"partner_key": "prtnr_abc123",
"name": "Enterprise Opportunity",
"amount": 50000,
"stage": "qualified"
}
Record an action (event-based rewards)
POST https://api.partnerstack.com/api/v2/actions
{
"customer_key": "cust_abc123",
"key": "signup_completed",
"value": 1
}
Create a reward
POST https://api.partnerstack.com/api/v2/rewards
{
"partner_key": "prtnr_abc123",
"amount": 5000,
"description": "Bonus for Q1 performance"
}
List leads
GET https://api.partnerstack.com/api/v2/leads?limit=25
Create a lead
POST https://api.partnerstack.com/api/v2/leads
{
"partner_key": "prtnr_abc123",
"email": "lead@company.com",
"name": "Potential Customer",
"company": "Acme Corp"
}
List partner groups
GET https://api.partnerstack.com/api/v2/groups
Manage webhooks
POST https://api.partnerstack.com/api/v2/webhooks
{
"target": "https://example.com/webhooks/partnerstack",
"events": ["deal.created", "transaction.created", "customer.created"]
}
API Pattern
PartnerStack uses cursor-based pagination. List responses include has_more and item keys for starting_after / ending_before parameters.
All responses follow the format:
{
"data": { ... },
"message": "...",
"status": "2xx"
}
Key Metrics
Partnership Metrics
partner_key- Unique partner identifiergroup- Partner tier/groupstatus- active, pending, archivedcreated_at- Partnership start date
Transaction Metrics
amount- Transaction value in centscurrency- Currency codeproduct_key- Associated productcustomer_key- Associated customer
Deal Metrics
amount- Deal valuestage- Deal pipeline stagestatus- open, won, lost
Reward Metrics
amount- Reward amount in centsstatus- pending, approved, paid
Parameters
Pagination Parameters
limit- Items per page (1-250, default: 10)starting_after- Cursor for next page (item key)ending_before- Cursor for previous page (item key)order_by- Sort field, prefix with-for descending
Common Filters
include_archived- Include archived recordshas_sub_id- Filter by sub ID presence
When to Use
- Managing SaaS affiliate and referral programs
- Tracking partner-driven revenue and attributions
- Automating partner onboarding and rewards
- Deal registration and pipeline tracking
- Multi-tier partnership programs (affiliates, resellers, agencies)
- Event-based reward triggers (signups, upgrades, etc.)
Rate Limits
- Not explicitly documented
- Use reasonable request rates; implement exponential backoff on 429 responses
Relevant Skills
- referrals
- affiliate-marketing
- partner-enablement
- saas-metrics
- launch-sequence