Co marketing
205 production GTM agent skills for Claude Code — sales, outbound, prospecting, RevOps, ABM, PLG, CS, automation. Framework-cited playbooks with artifacts + QA scripts.
npx -y skills add LeadMagic/gtm-skills --skill co-marketingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Execute co-marketing campaigns with partners — joint webinars, co-branded content, shared audiences, mutual promotion. Triggers on: "co-marketing", "joint marketing", "partner marketing", "co-branded campaign".
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
6.9 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it
Co-Marketing
Overview
Co-marketing is the fastest way to access a new audience with built-in trust. When a partner promotes you to their list, you borrow their credibility. This skill covers campaign design, asset creation, promotion coordination, and pipeline splitting.
Authoritative Foundations
- Co-Marketing Playbook — Named methodology governing recommendations in this skill's process.
- Crossbeam Partner-Led Growth — Named methodology governing recommendations in this skill's process.
- Crossbeam — Ecosystem-Led Growth — Ecosystem-Led Growth
When to Use
- "Run a co-marketing campaign"
- "Joint webinar with partner"
- "Co-branded content"
- "Partner content collaboration"
Step-by-Step Process
Phase 1: Partner Selection for Co-Marketing
- Audience overlap: Their audience contains your ICP. Not 100% — but a meaningful % would benefit from both products.
- Complementary, not competitive: Their product does something yours doesn't. The joint value proposition is clear.
- Audience size match: Your list is roughly comparable (within 3x). Otherwise the smaller partner gets disproportionate value.
- Execution reliability: They'll actually promote it. Vet by asking: "What was the last campaign you co-marketed? How did it perform?"
Phase 2: Campaign Formats
- Joint webinar: Co-presented by one person from each company. Customer story involving both products. 45 minutes. Split the registration list.
- Co-branded report/guide: Original research or definitive guide. Both logos. Both companies promote. Gated behind a form.
- Integration announcement: "Now [Partner] integrates with [You]" — blog posts, social, email blast, Product Hunt launch.
- Newsletter swap: You write for their newsletter, they write for yours. Simple, high trust.
- Social media takeover: Each company takes over the other's social for a day. Behind-the-scenes, tips, Q&A.
Phase 3: Promotion Coordination
- Shared promotion calendar: Agreed dates for each company's promotions
- Email sequence: Each company sends 2-3 emails to their list (tease, launch, last chance)
- Social promotion: 3-5 posts per company across platforms
- Paid amplification: Each company allocates $500-1000 for LinkedIn ads
- Sales enablement: Both companies arm their sales teams with talk tracks
Phase 4: Lead Management
- Form: Joint form (both brands). Clear opt-in language: "By registering, you agree to receive communications from [Company A] and [Company B]."
- Lead split: All leads go to both companies. Trust model — no "hiding" leads from each other.
- Follow-up: Each company runs their own follow-up sequence. Coordinate timing so prospects don't get hit by both simultaneously.
- Pipeline attribution: Tag as "co-marketing — [Partner Name]" in CRM.
Phase 5: Measurement & Iteration
- Registrations, attendees, leads generated, pipeline created, deals closed
- Cost: time invested + any paid promotion
- ROI: pipeline value / cost
- Partner debrief: what worked, what didn't, plan next campaign
Output Format
Co-marketing campaign plan with: partner brief, campaign format and assets, promotion calendar, lead management rules, and measurement framework.
Quality Check
Before delivering, verify:
- All required sections are complete
- Output matches the user's stated need
- Named frameworks are cited for key recommendations
- No vague claims — every recommendation has a specific action
- Deliverable is ready for operational use, not just conceptual
Common Pitfalls
- Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
- Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
- Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
Implementation Depth
Use this section when the user asks for a finished asset, not a high-level explanation.
Diagnostic Questions
- What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
- Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
- What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
- What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
- What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application
Map the recommendation explicitly to the named frameworks in this skill:
- Co-Marketing Playbook: apply only the part that directly improves the requested deliverable.
- Crossbeam Partner-Led Growth: apply only the part that directly improves the requested deliverable.
- Crossbeam — Ecosystem-Led Growth: apply only the part that directly improves the requested deliverable.
Deliverable Standard
A strong output from this skill includes:
- A crisp diagnosis of the current situation
- A recommended path with tradeoffs, not a generic list
- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
- A measurement plan with leading and lagging indicators
- Risks and edge cases called out before execution
Adaptation Rules
- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
Execution Artifacts
references/framework-notes.md— Named frameworks and reference tablestemplates/output-template.md— Deliverable shell for agent outputscripts/check-output.py— Lightweight deliverable validator
Related Skills
- partnership-strategy, webinar-strategy, content-marketing, social-media-strategy, partner-programs
What ships with it: 3 files
2.5 KB alongside SKILL.md, 1 of them executable
references/
- framework-notes.md835 B
scripts/
- check-output.pyruns850 B
templates/
- output-template.md850 B