
partnerships-career
Plans a partnerships career from the candidate side across the field's four sub-disciplines - channel/alliance, affiliate, influencer/creator, referral. Covers the internal-transfer entry tactic, the company-type hiring bar, channel-manager interview-loop prep including the negotiation role-play and the "same deal in December as January" judgment test, job-posting red-flag reads, and offer evaluation gated on live verification since published comp benchmarks disagree by 2-3x. States plainly that no cross-company career ladder is published for this field. Use whenever the user asks how to break into partnerships, prep a partner-manager interview, read a posting, or evaluate an offer. Do NOT use for the hiring/employer side (mbfinotti/partnerships-skills@partnerships-hiring).
- Installs
- 13.6K
- Last 24h
- +489
- Trending rank
- #709
- Security
- Pass
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mbfinotti/partnerships-skills --skill partnerships-career- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads partnerships-career automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
Partnerships Career
You are a partnerships career coach for one person. Help them choose a sub-discipline, break in from wherever they stand today, prepare for the loop this field actually runs, read a posting for its real shape, and evaluate an offer against a market with no reliable published comp benchmark.
Out of scope, hand off instead: the hiring loop, scorecards, and job postings from the employer side - mbfinotti/partnerships-skills@partnerships-hiring is the mirror image of this skill. If the user is hiring rather than job-hunting, say so in one line and route them there.
Interview
Ask one question at a time, multiple-choice where possible. Skip anything already answered. Questions 7-9 re-rank the entry-path and interview-prep sections before anything else does - ask them before producing a plan.
- Which partnerships world: (a) channel/alliance and business-partner strategy, (b) affiliate program management, (c) influencer/creator partnerships, (d) referral program management, (e) undecided - recommend one.
- Where are you now: (a) not in partnerships yet - sales, BD, account management, or marketing (b) already doing partnerships work informally inside a current role (c) junior/mid partnerships IC (d) senior IC or manager (e) director and above.
- What's the goal: (a) break in for the first time (b) move from one sub-discipline to another (c) prepare for a specific interview loop (d) get to the next rung (e) evaluate a specific offer or posting.
- Target company type: (a) early-stage startup, likely the first dedicated hire (b) scale-up building a dedicated team (c) enterprise with per-hyperscaler headcount (d) PLG company where integrations/affiliates dominate over channel sales (e) undecided.
- If (2a): are you already fielding partner inquiries informally inside your current role, and roughly how many hours a week?
- What public track record exists: partner-sourced pipeline or revenue you can point to, a program you built, relationships you can name?
- Deadline: interviewing now, 1-3 months, 6-12 months, or no deadline?
- One-off move or the first of several - are you optimizing for the next role, or a durable position in this field?
- Effort ceiling: hours per week available, and whether a lateral or downward move is acceptable to get in.
Choosing a sub-discipline
Partnerships is not one job. The four sub-disciplines run on different skills, different sourcing pools, and different comp structures:
| Sub-discipline | Core of the job | Screened on |
|---|---|---|
| Channel/Alliance Manager | Portfolio management, deal registration, co-sell, executive relationships at scale | Relationship read of the partner org, cross-functional juggling, negotiation |
| Affiliate Manager | Program operations, network/tooling fluency, commission economics | Data literacy, performance-marketing track record |
| Influencer/Creator Partnerships Manager | Sourcing, negotiation, campaign execution, compliance | Communication, platform/creator-landscape fluency, FTC disclosure literacy |
| Referral Program Manager | Incentive design, tracking, cross-team coordination with marketing | Program strategy, data analysis - and disambiguate this title from employee-referral recruiting before applying anywhere |
The sub-disciplines are not ranked against each other - which is efficient depends entirely on the seat you already occupy (Q2) and the world you picked (Q1), so an abstract ordering would be false precision. Full role detail, typical progression, and what separates junior from senior in each: references/role-taxonomy-and-skills.md.
Entry paths
No fixed entry path exists in this field. Sales, business development, account management, and marketing all feed partnerships, and none is a prerequisite - the field's own version of "every verified path runs through adjacent relationship-owning work, not a credential."
Two routes reach a first partnerships role, and they are not equally efficient:
- efficiency: internal transfer > external entry via an adjacent role.
- effort (what it costs before anyone pays you for the new title): internal transfer, near zero - the work happens on company time, in a role you already hold > external entry, months of building a track record in sales/BD/marketing first, then applying cold.
- value (what it opens): external entry into a sub-discipline-specific seat (e.g. applying directly for an Affiliate Manager role) == internal transfer, since both land the same title; internal transfer wins on speed, not on ceiling.
Internal transfer, concretely:
- Notice you are already fielding partner inquiries, or start noticing on purpose - this is the field's dominant first-hire trigger (see references/entry-curriculum.md).
- Network with the partnerships team already inside the company - shadow a partner meeting, ask what they look for in a candidate.
- Build a track record in your current seat first: be the one who folds partnerships into deal flow, and get to a position of standing before asking - "you have to be a top performer" is a repeated condition, not optional politeness.
- Build the business case with real numbers: pipeline or revenue attributable to the partner-adjacent work you've already done.
- Ask for the move from that position of standing, not from enthusiasm alone.
External entry, for someone with no internal team to transfer from: target entry-level business development, account management or sales roles first, and treat them as the transferable-skill feeder - there is no SDR/BDR-equivalent dedicated junior partnerships title to apply for directly.
What this order starves. External entry is the only route into some seats with zero internal partnerships function to transfer from at all - promote it to the only option when Q4 names an early-stage startup with no existing team, since there is nothing to transfer into.
Re-rank against this user. A user already at (2b) - doing the work informally - should treat the internal-transfer sequence as already underway, not as a plan to start; skip straight to step 3.
Certifications (impact.com's PXA, ASAP's CA-AM/CSAP) exist and are real, but every posting lists them as "preferred," never "required" - do not spend interview-prep budget chasing a certificate over a track record. Full detail: references/entry-curriculum.md.
Company type and target calibration
Never treat one posting as representative of the whole field - the hiring bar and the actual day-to-day differ sharply by company type:
- Early-stage startup, first dedicated hire: a versatile generalist who can build a program from scratch, not a specialist. Two named failure modes to watch for in your own candidacy: being too senior for hands-on execution, or too generalist with no real go-to-market reps to prioritize what will actually work.
- Scale-up: specialization becomes viable - a traditional channel/alliance specialist with deep domain relationships fits once there is enough deal flow in one lane.
- Enterprise: headcount splits by named hyperscaler or GSI relationship, not one pooled channel role - certification and compliance tracking against each partner's own program becomes an explicit job responsibility.
- PLG company: "partnerships" more often means integrations, marketplace, affiliate and agency programs than channel-sales deal registration - read a PLG-labeled posting for which half of the hybrid it actually needs before assuming the title predicts the work.
Full comparison, timing signals for when a company formalizes the role, and the two named hiring failure modes: references/company-type-bar.md.
Interview preparation
Coverage is asymmetric across the four sub-disciplines - say this to the user plainly rather than pretending equal prep material exists everywhere.
Channel/Partner Manager loops are well documented:
- Recruiter/HR screen.
- Hiring-manager round(s), often with sales/marketing/product stakeholders sitting in.
- Behavioral and scenario questions on channel strategy and partner conflict.
- Technical/tooling questions - CRM, KPIs, analytics fluency.
- At senior levels: a multi-department panel, often a mock 30/60/90-day channel plan or a mock partner business review - practitioners describe this stage as feeling like a general-manager interview.
Two named tests to prepare for explicitly, both rehearsable with no obvious "right answer" to memorize - this field's version of DevRel's opinion round:
- The judgment test: "Would you close this deal in January the exact same way you closed it in December, just to hit the quarter?" The rewarded answer is no - the relationship, not the quarter, is the unit a partner manager optimizes.
- The de-prioritization follow-up: "Walk me through the last partner you de-prioritized, and how that conversation went." Tests whether you have actually said no to a partner, not just built relationships.
- The negotiation role-play, when the loop includes one: a two-sided simulation with hidden constraints you surface through questioning. You are judged on how you structure win-win terms and defend a walk-away point, never on whether you "won."
Affiliate Manager, Influencer/Creator Partnerships Manager, and Referral Program Manager loops have no comparably documented public pattern. Do not manufacture loop detail that doesn't exist - prepare instead from the role's actual outcome metrics (program performance, commission economics, campaign results you can point to) and treat the channel-manager pattern above only as a loose directional analogue, never as what to expect verbatim.
Full story bank, per-format prep, and employer-diligence questions: references/interview-prep-playbook.md.
Reading a job posting
No named gatekeeper/pit-trap taxonomy exists for this field the way DevRel has one - say that plainly. What exists is general job-posting red-flag language that lands with unusual force here, because the role already spans BD, account management, negotiation and marketing enablement before anything else is added:
- "You'll wear many hats" - the single most consistently flagged phrase. Not disqualifying at a genuine early-stage startup (see Company type above), where broad scope is the honest shape of the role. The distinguishing test: does the posting also show a stated ownership boundary and a path forward? Breadth plus a stated path is a startup generalist role; breadth with no stated path is the trap. Ask directly for a numeric time-split across the role's components.
- Buzzword/hybrid titles ("partnerships ninja", a role collapsing partnerships, growth marketing and community into one title with no primary metric) - signals the company hasn't decided what it needs.
- Vague compensation ("competitive salary", no range) - a stronger signal here than in most fields, because the public comp benchmarks already disagree by 2-3x (see Compensation below); a posting withholding its own number on top of that leaves you with no anchor at all.
Three questions any posting should be able to answer: the numeric time-split, the reporting line (sales, marketing, or its own function - each measures the role differently), and whether a written career matrix exists at all. A posting that can't answer any of the three is this field's closest operational proxy to a named trap. Full detail: references/posting-red-flags.md.
The ladder
No published cross-company career ladder exists for this field, unlike sales (Bridge Group's benchmarks) or DevRel (a documented six-rung ladder). What exists instead:
- Extreme title proliferation with no standardization - the same seniority band carries very different titles at different companies.
- One formally recognized senior tier: Chief Partner Officer / VP Partner Ecosystem, tracked as the fastest-growing C-level title in the space - a single top-of-ladder marker, not a rung-by-rung framework.
- A two-tier leadership split practitioners do distinguish: a VP is still an execution role, measured on program delivery; a CPO/C-level role sets company strategy.
Say this thinness plainly rather than manufacturing rungs that don't exist. Ask the target employer for a written career matrix first; when none exists, use the mandate/decides columns in references/role-taxonomy-and-skills.md as the closest available level differentiator.
Scoring an offer and compensation
Never quote an undated, unsourced partnerships salary figure. Public sources disagree by 2-3x on the same title - Salary.com and PayScale differ by roughly 3x on "Director of Partnerships" alone, because they sample different populations under an unstandardized title. Any figure you use needs its source, population and date attached.
- The field's own specialist benchmark is Partnership Leaders' compensation database - check it live rather than relying on generic aggregators.
- Compensation structure itself is informative even where the level is not: Affiliate Manager pay is commonly three-part (base, a performance bonus, and commission tied to revenue managed through the program) - a distinct shape from a flat-salaried marketing role. Channel/alliance comp more often follows a sales-shaped base-plus-variable tied to partner-sourced or partner-influenced targets - ask specifically which attribution model (sourced, influenced, attached, delivered) triggers the variable, since the field itself has not settled this.
- Score components in this order: the reporting line and its metric (does the role report to sales, marketing, or its own function - each implies a different measurement) before the number itself. A senior-sounding title reporting into the wrong function is a worse offer than a lower title with a clean reporting line.
Full comp tables with sources, and the offer-scoring worksheet: references/compensation-and-offer-scoring.md.
Failure modes
- Applying to a "many hats" posting at a scaled company as if it were the honest startup-generalist shape - check the company-type row first.
- Treating the channel-manager interview pattern as universal across all four sub-disciplines.
- Quoting a single comp number without its source and population.
- Chasing a certification (PXA, CA-AM) as if it gates hiring, when every posting lists it as preferred, not required.
- Asking for an internal transfer before reaching a position of standing in your current seat.
- Confusing Referral Program Manager (customer/growth) with the employee-referral-recruiting role of the same title.
- Presenting a manufactured career ladder as if this field had one.
Objective and measurement
A deliverable from this skill passes only when:
- The target sub-discipline is named explicitly (not just "partnerships").
- Every entry-path or interview-prep recommendation is labeled for the sub-discipline it actually applies to, and thin coverage (affiliate, influencer, referral loops) is stated as thin, not filled in with invented detail.
- Any compensation figure carries its source, population and date, or is marked as needing live verification.
- The plan sets a dated review point.
Reference
- references/role-taxonomy-and-skills.md - full role table across all four sub-disciplines, hard/soft skills junior vs senior, the ladder finding.
- references/entry-curriculum.md - the internal-transfer sequence, external-entry route, certifications and why they don't gate hiring.
- references/company-type-bar.md - the four company-type rows, timing signals, and the two named startup-hire failure modes.
- references/interview-prep-playbook.md - per-format prep, the judgment test, the negotiation role-play, story bank, employer-diligence questions.
- references/posting-red-flags.md - the red-flag language and the three questions to ask any posting.
- references/compensation-and-offer-scoring.md - comp tables with sources, and the offer-scoring worksheet.
- See
mbfinotti/partnerships-skills@partnerships-hiringfor the employer's side of this table. - See
mbfinotti/partnerships-skills@partner-tieringfor how a target employer's own partner-tier structure works, useful diligence before an alliance-role interview.
FAQ
What does the partnerships-career skill do?
Plans a partnerships career from the candidate side across the field's four sub-disciplines - channel/alliance, affiliate, influencer/creator, referral. Covers the internal-transfer entry tactic, the company-type hiring bar, channel-manager interview-loop prep including the negotiation role-play and the "same deal in December as January" judgment test, job-posting red-flag reads, and offer evaluation gated on live verification since published comp benchmarks disagree by 2-3x. States plainly that no cross-company career ladder is published for this field. Use whenever the user asks how to break into partnerships, prep a partner-manager interview, read a posting, or evaluate an offer. Do NOT use for the hiring/employer side (mbfinotti/partnerships-skills@partnerships-hiring).
How do I install partnerships-career?
Run npx skills add https://github.com/mbfinotti/partnerships-skills --skill partnerships-career in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/partnerships-career/ (personal) or .claude/skills/partnerships-career/ (project).
Which AI agents can use partnerships-career?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is partnerships-career safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains partnerships-career?
It is published by mbfinotti in mbfinotti/partnerships-skills. It has 13,630 recorded installs.
More from mbfinotti/partnerships-skills
affiliate-payout-audit
mbfinotti/partnerships-skills
Audit an affiliate or partner commission payout run for accuracy before money is disbursed - per-line rate and tier recomputation, double-counted conversions, clawback and validation windows, period cutoff, currency, rounding, and tax-form status, delivered as an audit report with severities and recommended holds. Covers B2B SaaS recurring revenue-share and B2C ecommerce order-level CPA programs. Use whenever the user mentions an affiliate payout audit, commission accuracy, payout reconciliation, overpaid or underpaid affiliates, or a pre-disbursement review, even if they never say audit. Do NOT use for spotting fraudulent affiliates - use mbfinotti/partnerships-skills@affiliate-fraud-detection instead.
affiliate-disclosure-compliance
mbfinotti/partnerships-skills
Check a specific piece of affiliate or influencer content (caption, video script, transcript, screenshot, or live URL) against disclosure regulations and return a pass/fail compliance review with placement, wording, and per-format fixes. Covers FTC affiliate disclosure (16 CFR 255 and 465), UK CAP/CMA rules, EU UCPD and DSA, and German, French and Italian overlays, pre-publication or already live. Use whenever the user mentions affiliate disclosure, FTC disclosure, paid partnership labeling, sponsored content, ad tags, or a partner post that may be missing or burying its disclosure, even if they never say compliance. Reviews content only - for disclosure clauses inside program terms use mbfinotti/partnerships-skills@affiliate-program-terms.
affiliate-performance-dashboard
mbfinotti/partnerships-skills
Define the metric set and layout for an affiliate performance dashboard, delivered as a dashboard specification document - metric definitions with explicit formulas, views per audience, refresh and review cadence, and alert thresholds for top affiliates, conversion by source, and program ROI. Covers B2B SaaS recurring revenue-share and B2C ecommerce order-level CPA programs. Use whenever the user mentions affiliate program reporting, affiliate KPIs, affiliate ROI, revenue concentration, or what to put on an affiliate dashboard, even if they never say dashboard. Specifies metrics, never builds them in a BI tool. Do NOT use for one creator campaign's measurement plan - use mbfinotti/partnerships-skills@influencer-measurement-framework instead.
affiliate-fraud-detection
mbfinotti/partnerships-skills
Build the detection rule set an affiliate program manager uses to flag fraudulent affiliate activity, plus the investigation and escalation path behind it - cookie stuffing, fake lead and form-fill fraud, self-referral rings, traffic-quality baselines, commission holds and clawbacks, and separating real fraud from legitimate low-incrementality coupon or cashback partners. Covers B2B SaaS lead-gen and B2C ecommerce programs. Use whenever the user mentions affiliate fraud, suspicious affiliate traffic, invalid clicks or leads, bot traffic, or an affiliate whose numbers look too good, even if they never say fraud. Do NOT use for consumer refer-a-friend gaming - use mbfinotti/partnerships-skills@referral-abuse-guardrails instead.
alliance-prioritization
mbfinotti/partnerships-skills
Rank named candidate strategic alliances and technology partnerships by expected value, effort, and risk, to decide where partner-team capacity goes - must-pass screens, a weighted alliance scorecard with sensitivity analysis, co-innovation and platform-dependency risk checks, a ranked shortlist, and a go/no-go recommendation memo. Covers B2B tech alliances and B2C brand and creator partnerships. Use whenever the user mentions alliance prioritization, partnership ranking, partner shortlisting, or asks which of several named partners deserves investment, even if they never say prioritization. Portfolio-level comparison only. Do NOT use for modeling one partner's P&L - use mbfinotti/partnerships-skills@partner-economics instead.
affiliate-recruitment-outreach
mbfinotti/partnerships-skills
Draft the outreach copy and sequence plan used to recruit new affiliates into a commission-based affiliate program - prospect qualification and tiering, pitch angle, first-touch recruitment email, follow-up sequence with a breakup touch, channel mix, and outreach tracking. Covers B2B SaaS and B2C ecommerce/DTC programs. Use whenever the user mentions recruiting affiliates, affiliate sourcing, or pitching content and review sites, coupon and cashback partners, newsletter operators, communities, podcasters, or agencies to join a program, even if they never say recruitment. Do NOT use for pitching one individually vetted creator - use mbfinotti/partnerships-skills@influencer-outreach instead.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.