mcpField
P
partner-co-marketing-launch-review

partner-co-marketing-launch-review

github.com/sylphxaiMarketing & growth142 installsUpdated today
Repository

About partner-co-marketing-launch-review

This skill turns partner co-marketing launch questions into plans and artifacts with owners, gates, metrics, and recovery paths. It supports several campaign formats and sets guardrails for proof, attribution, approvals, and data sharing.

Key features

  1. 01Identify partner type, audience, and commitments
  2. 02Classify co-marketing motions
  3. 03Plan narrative, assets, and approvals
  4. 04Define attribution, lead routing, and launch calendar
  5. 05Produce plans, decision tables, and checklists

Use cases

  1. 01Plan an integration launch or marketplace listing
  2. 02Prepare a joint webinar or case study
  3. 03Organize a referral campaign or reseller enablement
  4. 04Review approvals, lead follow-up, and attribution

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill partner-co-marketing-launch-review

After installing, type/partner-co-marketing-launch-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/partner-co-marketing-launch-patterns.md

Details

From the project README

Partner Co-Marketing Launch Review

Use this skill to convert a partner co-marketing, joint messaging, launch assets, approvals, attribution, leads, channels, and follow-up question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify partner type, shared audience, integration value, mutual proof, commitments, approval constraints, channel owners, and success metric.
  2. Read references/partner-co-marketing-launch-patterns.md.
  3. Classify motion: integration launch, marketplace listing, webinar, case study, bundle, referral campaign, reseller enablement, or ecosystem announcement.
  4. Define joint narrative, assets, approvals, UTM/attribution, lead routing, enablement, launch calendar, risk controls, and post-launch review.
  5. Produce co-marketing plan, state machine, decision table, event schema, asset checklist, and partner follow-up loop.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not claim partner endorsement, certification, customer logos, revenue impact, or roadmap commitment without approval and proof.
  • Do not launch without lead routing, attribution, and ownership for inbound follow-up.
  • Do not let one partner campaign confuse product positioning or create unsupported integration promises.
  • Do not share customer data or pipeline details across partners without consent and legal basis.

Output format

Partner launch context:
Partner / audience / proof / commitments:

Co-marketing launch plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Assets and approvals:
- <item> -> <policy, metric, edge case, support note>

Attribution and follow-up:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported