partner-marketing
Skill2 starsChanged 29 days agoMITView on GitHub
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.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- TeqfocusAdmin/ClaudeSkillsRepotheir own version, first seen Sep 22, 2026
- the-nam-shub/e5-real-skillstheir own version, first seen Apr 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- the-nam-shub/e5-real-skills★ 10same name
- TeqfocusAdmin/ClaudeSkillsRepo★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- account-based-marketingSkill
- acquisition-conversionSkill
- ad-creativeSkill
- analytics-trackingSkill
- aso-auditSkill
- buyer-resourcesSkill
- cold-emailSkill
- community-marketingSkill
- competitor-alternativesSkill
- competitor-profilingSkill
- content-strategySkill
- customer-marketingSkill
- customer-researchSkill
- email-sequenceSkill
- eventsSkill
- go-to-market-strategySkill
- icp-and-buyer-personasSkill
- launch-readiness-checkSkill
- launch-strategySkill
- localization-claimsSkill
- market-entry-briefSkill
- market-entry-orchestrationSkill
- marketing-copySkill
- marketing-experimentationSkill
- market-intelligenceSkill
- messaging-consistency-auditSkill
- messaging-frameworkSkill
- objection-intelligenceSkill
- output-quality-checkSkill
- paid-adsSkill
- positioning-strategySkill
- pricing-strategySkill
- product-activationSkill
- product-communicationsSkill
- product-marketing-contextSkill
- referral-programSkill
- revopsSkill
- sales-enablementSkill
- search-discoverabilitySkill
- social-contentSkill
- ssot-context-loopSkill
- upgrade-conversionSkill
- website-buyer-journeySkill
- win-loss-intelligenceSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Do not expand into corporate development, M&A, or generic partnership operations.
- Very specific: line 22
Read ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md.
- Very specific: line 24
Read ../_shared/segment-selection.md only when choosing audiences.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

