Agent skill
partner-marketing
When the user wants to plan a GTM partnership, joint launch, co-marketing, ecosystem, channel, referral, or co-sell motion.
Filed under Partnerships and channel.
From mia-ppp/PMM-Skills · 45 skill entries · 71 · pushed 2026-10-16
What it does when it runs
When the user wants to plan a GTM partnership, joint launch, co-marketing, ecosystem, channel, referral, or co-sell motion. For joint events, coordinate with events; for partnership operations, corporate development, or M&A, use the appropriate non-PMM owner.
Automated analysis of the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Ask about partner-marketing
Opens your assistant with this page's recorded context. Check the linked sources before relying on it.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/mia-ppp/PMM-Skills.git /tmp/PMM-Skills git -C /tmp/PMM-Skills sparse-checkout set "skills/partner-marketing" mkdir -p ~/.claude/skills/partner-marketing cp -R "/tmp/PMM-Skills/skills/partner-marketing/." ~/.claude/skills/partner-marketing/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from mia-ppp/PMM-Skills/blob/5281aa6e55ca12d2ad5f97c3bf45e8cf49488225/skills/partner-marketing/SKILL.md, which is licensed MIT (repository). 387 words, 7 headings.
Partner Marketing
Plan GTM partnerships and co-marketing. Own the joint audience/value hypothesis, narrative brief, contribution and approval map, activation plan, and learning. Do not expand into corporate development, M&A, or generic partnership operations.
Integration marketplace presence
For approved integration listings read marketplace brief. Keep bilateral GTM and partner approval separate from referral incentive mechanics.
Before planning
Read ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md.
Load the project manifest's relevant approved context and record sources used.
Read ../_shared/segment-selection.md only when choosing audiences; inherit
accepted segment decisions without redefining canonical ICP.
Workflow
Distinguish partner participants from end buyers when defining joint value and handing audience intelligence to asset owners.
- Define the business objective and partnership type: technology/integration, ecosystem, channel, strategic alliance, referral/co-sell, or joint launch.
- Establish evidence for audience overlap, mutual customer value, partner capability, and each party's contribution. Mark unsupported assumptions.
- Develop a joint narrative that preserves our approved canon. Label separately our approved claims, partner-approved claims, jointly approved claims, and unverified assumptions. Obtain explicit approval from both parties for joint claims and quotes.
- Define offer/CTA, distribution, sales/co-sell motion, owners, approvals, dependencies, dates, measurement, and learning. Separate sourced outcomes from influence claims.
- Route execution to channel owners and coordinate approval before publication.
Required output
Inputs and assumptions; objective and audience overlap; mutual value; party
contributions; joint narrative and claim-status table; offer/CTA; distribution
and sales motion; asset/approval owners; measurement; risks and evidence gaps.
Output quality: output-quality-check can verify the required plan, claim
provenance/status, bilateral approvals, ownership, measures, and no fabricated
partner facts or proof.
Handoffs and governance
This skill owns partner fit, mutual value, co-sell coordination, and joint
approvals. referral-program owns referral/affiliate mechanics, incentives,
and tracking. For a joint product release, launch-strategy owns release phases
and sequencing; this skill owns partner contributions and bilateral approvals.
Route joint event strategy to events; co-sell material to
sales-enablement; copy to marketing-copy; email to email-sequence or
cold-email; social activation to social-content; tracking to
analytics-tracking. This skill does not write final channel assets. Joint
market-facing messaging should pass messaging-consistency-audit and partner
approval. Any conflict with company canon goes to ssot-context-loop for
review; never change canon. A proposed quote remains DRAFT / REQUIRES APPROVAL
until approved by the named speaker and relevant parties.
Related skills
referral-program, launch-strategy, events, sales-enablement, marketing-copy, email-sequence, cold-email,
social-content, analytics-tracking, messaging-consistency-audit,
ssot-context-loop, output-quality-check.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- co-marketing by coreyhaines31 · 57,918
- community-marketing by coreyhaines31 · 57,918
- influencer-marketing by coreyhaines31 · 57,918
- marketing-council by coreyhaines31 · 57,918
- marketing-ideas by coreyhaines31 · 57,918
- marketing-loops by coreyhaines31 · 57,918
- marketing-plan by coreyhaines31 · 57,918
- marketing-psychology by coreyhaines31 · 57,918
Need help setting it up?
This page tells you what partner-marketing does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.