partnership-marketer
Expert partnership marketing guidance for building and scaling partner programs, co-marketing campaigns, and channel ecosystems. Use when developing partner strategy, creating co-marketing content, designing partner tiers, building affiliate programs, positioning in integration marketplaces, enabling channel partners, planning joint webinars, or structuring revenue sharing. Use for technology partnerships, reseller programs, strategic alliances, and partner relationship management.
What this skill does
# Partnership Marketer
Expert partnership marketing guidance for building scalable partner ecosystems, co-marketing campaigns, and channel programs — from partner selection to revenue attribution.
## Philosophy
Great partnership marketing creates multiplier effects:
1. **Strategic alignment** — Partners succeed when you succeed, and vice versa
2. **Mutual value creation** — Every partnership should benefit both parties measurably
3. **Scalable enablement** — Partners should be able to sell/integrate without hand-holding
4. **Compounding returns** — Strong partnerships generate referrals and expand networks
## How This Skill Works
When invoked, apply the guidelines in `rules/` organized by:
- `strategy-*` — Partner selection, program design, and strategic planning
- `comarketing-*` — Joint campaigns, content collaboration, and co-branding
- `marketplace-*` — Integration marketplace positioning and optimization
- `program-*` — Partner tiers, benefits, and program structure
- `enablement-*` — Partner training, content, and sales tools
- `revenue-*` — Revenue sharing, attribution, and commission structures
## Core Frameworks
### Partner Value Matrix
```
HIGH STRATEGIC VALUE
│
Technology │ Strategic
Partners │ Alliances
(Integrations) │ (Joint GTM)
│
─────────────────────────────────────────────────
│
Affiliate │ Channel
Partners │ Partners
(Lead gen) │ (Resellers)
│
LOW STRATEGIC VALUE
LOW REVENUE ◄─────────────────────► HIGH REVENUE
```
### The Partnership Lifecycle
```
┌─────────────────────────────────────────────────────────────┐
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ IDENTIFY │──▶│ ACTIVATE │──▶│ SCALE │──▶│ EXPAND │ │
│ │ (Select) │ │ (Launch) │ │ (Grow) │ │ (Deepen) │ │
│ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │
│ ▲ │ │
│ │ ┌──────────┐ │ │
│ └──────────────│ REVIEW │◀──────────────────┘ │
│ │(Optimize)│ │
│ └──────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
```
### Partner Program Tiers
| Tier | Criteria | Typical Benefits |
|------|----------|------------------|
| **Registered** | Signed agreement | Logo use, basic portal access |
| **Silver** | $10K revenue or 5 referrals | Co-marketing funds, training |
| **Gold** | $50K revenue or 20 referrals | Dedicated PM, joint campaigns |
| **Platinum** | $200K+ revenue | Custom pricing, executive sponsor |
### Co-Marketing Investment Formula
```
Co-Marketing Budget = Partner Tier Budget × Pipeline Potential × Strategic Value Score
```
| Factor | Multiplier Range |
|--------|------------------|
| Partner Tier Budget | Base allocation per tier |
| Pipeline Potential | 0.5x - 2x based on lead quality |
| Strategic Value Score | 0.8x - 1.5x based on brand alignment |
## Partnership Types at a Glance
| Type | Goal | Key Metric | Time to Value |
|------|------|------------|---------------|
| Technology/Integration | Expand functionality | Active integrations | 3-6 months |
| Affiliate | Lead generation | Referred revenue | 1-3 months |
| Reseller/Channel | Sales extension | Partner-sourced ARR | 6-12 months |
| Strategic Alliance | Market expansion | Co-sold deals | 6-18 months |
| OEM/White-label | Revenue diversification | Embedded revenue | 12-24 months |
## Key Partnership Metrics
| Metric | Formula | Target |
|--------|---------|--------|
| **Partner-Sourced Revenue** | Revenue from partner leads | 20-30% of total |
| **Partner-Influenced Revenue** | Partner involved in deal | 40-50% of total |
| **Partner Activation Rate** | Active partners / Total partners | 60%+ |
| **Partner NPS** | Partner satisfaction score | 50+ |
| **Revenue per Partner** | Total partner revenue / Active partners | Varies by tier |
| **Time to First Deal** | Days from signup to first closed deal | <90 days |
## Partner Enablement Stack
| Asset | Purpose | Priority |
|-------|---------|----------|
| Partner Portal | Self-service hub | CRITICAL |
| Sales Playbook | How to sell with/through you | CRITICAL |
| Integration Docs | Technical enablement | HIGH |
| Co-brandable Content | Marketing materials | HIGH |
| Demo Environment | Show capabilities | MEDIUM |
| Certification Program | Ensure quality | MEDIUM |
## Anti-Patterns
- **Quantity over quality** — 100 inactive partners < 10 engaged ones
- **One-sided value** — Partners who only take, never give (and vice versa)
- **No attribution** — Can't prove partner value, can't justify investment
- **Ignoring partner success** — Your success tied to theirs
- **Overcomplicating tiers** — If partners can't explain it, it won't work
- **Set and forget** — Partnerships need ongoing nurturing
- **MDF without accountability** — Marketing funds with no ROI tracking
- **Competing with partners** — Selling direct into partner accounts
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.