[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M95H03RKFCTV4741X18AJJ":3,"skill-same:01M6M95H03RKFCTV4741X18AJJ":108},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6M95H03RKFCTV4741X18AJJ","suede-co-marketing",null,"Suede AI Co-Marketing Skills. Use when asked to \"find co-marketing partners\" or plan a joint campaign: evidence-backed fit, reciprocal value, format, roles, consent, shared KPIs and content. NOT FOR: affiliate\u002Freferral programs (suede-referrals), software release packaging (suede-launch-packaging), or partner-facing sales collateral (suede-sales-enablement).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-co-marketing\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"marketing","suede co marketing","co marketing","co","software release","when","value","referral","for","enablement","affiliate","fit","software","release","referrals","shared","campaign","evidence","packaging","marketing skills","plan","2026-11-10 10:12:30",false,"---\nname: suede-co-marketing\ndescription: \"Suede AI Co-Marketing Skills. Use when asked to \\\"find co-marketing partners\\\" or plan a joint campaign: evidence-backed fit, reciprocal value, format, roles, consent, shared KPIs and content. NOT FOR: affiliate\u002Freferral programs (suede-referrals), software release packaging (suede-launch-packaging), or partner-facing sales collateral (suede-sales-enablement).\"\nmetadata:\n  display-name: \"Suede AI Co-Marketing Skills\"\n  version: 2.1.0\n---\n\n# Suede AI Co-Marketing Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nWorks from product context and partner evidence; web research or supplied sources for scoring and file tools for campaign plans. Outreach, lead sharing and publication need separate existing authority.\n\nUse this co-marketing playbook to identify credible partners and design measurable joint campaigns with explicit roles and value exchange.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Partner Identification Framework\n\n### 1. Audience Overlap Analysis\n\nThe best partners share your audience but don't compete for the same budget.\n\n**Ideal partner characteristics:**\n- Same buyer persona, different problem solved\n- Adjacent in the workflow (before, after, or alongside your tool)\n- Similar company stage and customer size\n- Complementary, not competitive\n\n**Questions to identify partners:**\n- What tools do your customers already use?\n- What do they use before\u002Fafter your product?\n- Who else is selling to your ICP?\n- Which integrations do customers request most?\n\n### 2. Partner Scoring Criteria\n\nRate each candidate 1-5 on all six criteria, using these anchors. Score from\nevidence the user or a public source supplies; a criterion with no evidence is\nscored `?` and named as an open question, never guessed.\n\n| Criteria | 1 | 3 | 5 |\n|----------|---|---|---|\n| **Audience fit** | Different buyer, different problem | Same buyer, partial overlap | Same ICP, adjacent workflow step |\n| **Audience size** | Reach materially below yours | Same order of magnitude | At or above your reach on the shared channel |\n| **Brand alignment** | You would hedge before associating | Neutral; no known conflict | You would name them in your own marketing unprompted |\n| **Engagement quality** | Reach with no observable response | Some engagement, unverified | Documented engagement on the channel the campaign will use |\n| **Reciprocity potential** | Nothing of comparable value to offer | One-sided but tolerable | Both sides trade equivalent audience or asset value |\n| **Ease of execution** | No partnerships contact, no prior co-marketing | Contact exists, no track record | Partnerships team plus a shipped co-marketing history |\n\n**Pursue\u002Fdrop rule:** pursue only partners scoring **4+ on both Audience fit and\nReciprocity potential**. Anything below is reported as scored-and-dropped with\nthe failing criterion named: it is not silently omitted.\n\n**Shortlist cap: 5.** At the cap, rank the five and report; do not expand the\nlist. Additional candidates go in a named \"not pursued this round\" line.\n\n### 3. Where to Find Partners\n\n**Integration ecosystem:**\n- Your existing integration partners\n- Tools in the same app marketplace category\n- Platforms your product plugs into\n\n**Adjacent categories:**\n- Tools that solve the problem before yours\n- Tools that solve the problem after yours\n- Tools used by the same role but different workflow\n\n**Community signals:**\n- Who sponsors the same podcasts\u002Fnewsletters?\n- Who exhibits at the same conferences?\n- Who's active in the same communities?\n- Whose content does your audience share?\n\n**Data sources:**\n- Crossbeam or Reveal for account overlap\n- Customer surveys (\"what else do you use?\")\n- G2\u002FCapterra category neighbors\n- Job postings mentioning your tool + others\n\n---\n\n## Co-Marketing Campaign Types\n\nFour families, with per-format effort, lead sharing, and best-fit in\n[references\u002Fcampaign-formats.md](references\u002Fcampaign-formats.md). Open that file\nwhenever a campaign format is being chosen: the campaign plan must name its\nformat from it.\n\n- **Content partnerships**: when both sides can produce and both audiences read.\n- **Webinars & events**: when the goal is gated lead generation or education.\n- **Product & integration marketing**: when a live integration or shared customer exists.\n- **Community & social**: when the goal is exposure or list growth, not pipeline.\n\n---\n\n## Make Joint Content Work in Search and AI Answers\n\nJoint content can earn more than a shared list. Done right, it becomes the\npage that ranks and gets cited for the combined use case.\n\n- **Publish one canonical version.** Pick the host domain; the partner links\n  to it (or uses a rel=\"canonical\" copy) instead of duplicating it.\n- **Target the combined query.** \"[Tool A] + [Tool B] integration\", \"how to\n  [job] with [A] and [B]\": queries neither brand ranks for alone.\n- **Ship original data when possible.** A joint survey or benchmark across both\n  customer bases is a link asset neither could produce alone. Publish method,\n  sample size, and date.\n- **Both brands named consistently** in title, byline, and copy so AI answers\n  attribute the claim to both.\n- **Integration pages:** list the partner in each side's integration\n  directory with a link, a short how-it-works, and the shared customer story.\n\nTechnical checks route to `suede-seo-audit`; topic choice to\n`suede-content-strategy`.\n\n---\n\n## Brainstorming Partner Campaigns\n\nWhen brainstorming with a specific partner, consider:\n\n### 1. Shared Audience Moments\n\n- What trigger events matter to both audiences?\n- What seasonal moments align with both products?\n- What industry trends affect both customer bases?\n\n### 2. Combined Value Propositions\n\n- What can customers achieve with both tools that they can't with one?\n- What workflow does the combination enable?\n- What pain point does the integration solve?\n\n### 3. Unique Assets Each Brings\n\nInventory what each side brings across audience, content expertise, product\ncapabilities, brand credibility, and customer stories, and name which asset the\ncampaign actually depends on.\n\n---\n\n## Approaching Potential Partners\n\n### Outreach gate (draft-only, hard stop)\n\nOutreach drafts are produced; outreach is never sent. At the handover: stop, name\nthe four variables in one line each: recipient, channel, visible sending\nidentity, exact message, state that the outcome is a draft and nothing has been\nsent, offer **approve \u002F revise \u002F drop**, and wait for the user's pick. The same\ngate covers sharing any customer or overlap data with the partner.\n\n### Cold Outreach Template\n\n```\nSubject: [Your Company] + [Their Company] co-marketing idea\n\nHey [Name],\n\nI'm [Role] at [Your Company]. We [one-line description].\n\nI noticed we share a lot of the same audience, [specific observation about overlap].\n\nI have an idea for [specific campaign type] that could work well for both of us: [one-sentence pitch].\n\nWould you be open to a quick call to explore?\n\n[Your name]\n```\n\n### What to Prepare for the Call\n\n1. **Account overlap data** (if available via Crossbeam\u002FReveal)\n2. **2-3 specific campaign ideas** (not just \"let's do something\")\n3. **Your audience metrics** (list size, traffic, engagement)\n4. **Examples of past partnerships** (shows you can execute)\n5. **Clear ask** (what you want from them, what you'll provide)\n\n---\n\n## Structuring the Partnership\n\n### Key Questions to Align On\n\n- **Lead ownership**: gated\u002Fsplit (one shared form, agreed split, written data\n  and consent terms) or each-keeps-own (no shared list: the default until data\n  terms are agreed). The format chosen from `references\u002Fcampaign-formats.md`\n  names which arrangement it assumes.\n- **Promotion commitments**: What will each party do to promote?\n- **Asset creation**: Who creates what? Who approves?\n- **Timeline**: When does each phase happen?\n- **Success metrics**: How will you measure success?\n- **Follow-up**: Will you do more together if it works?\n\n### Simple Co-Marketing Agreement Outline\n\n1. **Campaign description**: What you're doing together\n2. **Responsibilities**: Who does what\n3. **Timeline**: Key dates and deadlines\n4. **Lead handling**: How leads are captured, shared, followed up\n5. **Promotion**: Minimum commitments from each side\n6. **Branding**: Logo usage, approval process\n7. **Costs**: Who pays for what (if any)\n8. **Metrics sharing**: What data you'll share post-campaign\n\n---\n\n## Measuring Co-Marketing Success\n\n- Leads generated (total and per partner)\n- Lead quality (MQL\u002FSQL conversion rate)\n- Revenue attributed\n- Audience growth (new subscribers, followers)\n- Content engagement (views, downloads, shares)\n\nBaselines and targets come from the user's current analytics, not from a generic\nbenchmark. Report only metrics both sides agreed to share.\n\n---\n\n## Co-Marketing Checklist\n\n### Partner Identification\n- [ ] List tools your customers already use\n- [ ] Check Crossbeam\u002FReveal for account overlap\n- [ ] Score candidates on all six criteria and apply the pursue\u002Fdrop rule (cap 5)\n- [ ] Research their past co-marketing activities\n\n### Campaign Planning\n- [ ] Agree on campaign type and goals\n- [ ] Define lead sharing arrangement\n- [ ] Assign responsibilities and deadlines\n- [ ] Set success metrics\n\n### Execution\n- [ ] Create shared assets (landing page, content, etc.)\n- [ ] Coordinate promotion schedules\n- [ ] Brief both teams on talking points\n\n### Post-Campaign\n- [ ] Share metrics with partner\n- [ ] Debrief on what worked\u002Fdidn't\n- [ ] Discuss future collaboration opportunities\n\n---\n\n## Output Format\n\nThis skill returns one of two deliverables. Copy the matching skeleton verbatim\nfrom [references\u002Foutput-templates.md](references\u002Foutput-templates.md), open that\nfile before writing either one.\n\n**Scored partner shortlist** must contain:\n\n1. The ranked shortlist (max 5) with all six criterion scores per partner\n2. A scored-and-dropped list naming the failing criterion for each\n3. Open questions for any criterion scored `?`\n4. Candidates not pursued this round\n5. A recommended first move with a format named from `references\u002Fcampaign-formats.md`\n\n**Joint campaign plan** must contain:\n\n1. Campaign format (named from the formats reference), goal, and its one proving metric\n2. Value exchange on both sides\n3. Responsibilities and timeline with an owner and approver per phase\n4. Lead handling: gated\u002Fsplit or each-keeps-own, with the capture path\n5. Promotion commitments, branding approvals, and maximum approved cost\n6. Measurement plan with agreed shared metrics and a debrief date\n7. An approval-status line stating nothing has been sent, published, or committed\n\n---\n\n## Task-Specific Questions\n\n1. Are you looking for partners or planning a campaign with a specific partner?\n2. What type of co-marketing are you most interested in? (content, events, integrations, community)\n3. What's your audience size? (email list, social following, traffic)\n4. Do you have existing integration partners?\n5. Have you done co-marketing before? What worked\u002Fdidn't?\n6. What's your timeline and budget for co-marketing?\n\n---\n\n## Tool Integrations\n\nThis pack does not ship partner-platform connectors. Use an authorized product\nUI, current export, API, or installed connector and verify the provider's\ncurrent official documentation before reading or changing partner data.\n\nSelect capabilities against the campaign:\n\n- Privacy-safe aggregate account overlap, with minimum cohort thresholds\n- Partner records, owners, approvals, commitments, and deal registration\n- Shared asset review, version history, deadlines, and publication approval\n- Source-specific links or codes and agreed lead\u002Frevenue attribution\n- Export, deletion, access control, and audit-history requirements\n\n---\n\n## Boundaries\n\n- Do not claim a partnership, audience overlap, endorsement, reach, or committed deliverable without evidence from both sides.\n- Do not contact partners, share customer lists, sign terms, spend budget, or publish joint work without explicit authorization.\n- Do not decide ownership, licensing, attribution, lead-sharing, or revenue-sharing terms for the parties.\n- Do not expose private customer or partner data to prove overlap; use approved aggregate or privacy-safe methods.\n\n## Routing\n\n- Need referral or affiliate mechanics -> use `suede-referrals`.\n- Need launch sequencing and release assets -> use `suede-launch-packaging`.\n- Need co-created editorial planning -> use `suede-content-strategy`.\n- Need partner-facing collateral -> use `suede-sales-enablement`.\n- Need earned media for a joint launch announcement -> use `suede-public-relations`.\n- From those skills, route partner selection and joint-campaign design back to `suede-co-marketing`.\n","# Suede AI Co-Marketing Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nWorks from product context and partner evidence; web research or supplied sources for scoring and file tools for campaign plans. Outreach, lead sharing and publication need separate existing authority.\n\nUse this co-marketing playbook to identify credible partners and design measurable joint campaigns with explicit roles and value exchange.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Partner Identification Framework\n\n### 1. Audience Overlap Analysis\n\nThe best partners share your audience but don't compete for the same budget.\n\n**Ideal partner characteristics:**\n- Same buyer persona, different problem solved\n- Adjacent in the workflow (before, after, or alongside your tool)\n- Similar company stage and customer size\n- Complementary, not competitive\n\n**Questions to identify partners:**\n- What tools do your customers already use?\n- What do they use before\u002Fafter your product?\n- Who else is selling to your ICP?\n- Which integrations do customers request most?\n\n### 2. Partner Scoring Criteria\n\nRate each candidate 1-5 on all six criteria, using these anchors. Score from\nevidence the user or a public source supplies; a criterion with no evidence is\nscored `?` and named as an open question, never guessed.\n\n| Criteria | 1 | 3 | 5 |\n|----------|---|---|---|\n| **Audience fit** | Different buyer, different problem | Same buyer, partial overlap | Same ICP, adjacent workflow step |\n| **Audience size** | Reach materially below yours | Same order of magnitude | At or above your reach on the shared channel |\n| **Brand alignment** | You would hedge before associating | Neutral; no known conflict | You would name them in your own marketing unprompted |\n| **Engagement quality** | Reach with no observable response | Some engagement, unverified | Documented engagement on the channel the campaign will use |\n| **Reciprocity potential** | Nothing of comparable value to offer | One-sided but tolerable | Both sides trade equivalent audience or asset value |\n| **Ease of execution** | No partnerships contact, no prior co-marketing | Contact exists, no track record | Partnerships team plus a shipped co-marketing history |\n\n**Pursue\u002Fdrop rule:** pursue only partners scoring **4+ on both Audience fit and\nReciprocity potential**. Anything below is reported as scored-and-dropped with\nthe failing criterion named: it is not silently omitted.\n\n**Shortlist cap: 5.** At the cap, rank the five and report; do not expand the\nlist. Additional candidates go in a named \"not pursued this round\" line.\n\n### 3. Where to Find Partners\n\n**Integration ecosystem:**\n- Your existing integration partners\n- Tools in the same app marketplace category\n- Platforms your product plugs into\n\n**Adjacent categories:**\n- Tools that solve the problem before yours\n- Tools that solve the problem after yours\n- Tools used by the same role but different workflow\n\n**Community signals:**\n- Who sponsors the same podcasts\u002Fnewsletters?\n- Who exhibits at the same conferences?\n- Who's active in the same communities?\n- Whose content does your audience share?\n\n**Data sources:**\n- Crossbeam or Reveal for account overlap\n- Customer surveys (\"what else do you use?\")\n- G2\u002FCapterra category neighbors\n- Job postings mentioning your tool + others\n\n---\n\n## Co-Marketing Campaign Types\n\nFour families, with per-format effort, lead sharing, and best-fit in\n[references\u002Fcampaign-formats.md](references\u002Fcampaign-formats.md). Open that file\nwhenever a campaign format is being chosen: the campaign plan must name its\nformat from it.\n\n- **Content partnerships**: when both sides can produce and both audiences read.\n- **Webinars & events**: when the goal is gated lead generation or education.\n- **Product & integration marketing**: when a live integration or shared customer exists.\n- **Community & social**: when the goal is exposure or list growth, not pipeline.\n\n---\n\n## Make Joint Content Work in Search and AI Answers\n\nJoint content can earn more than a shared list. Done right, it becomes the\npage that ranks and gets cited for the combined use case.\n\n- **Publish one canonical version.** Pick the host domain; the partner links\n  to it (or uses a rel=\"canonical\" copy) instead of duplicating it.\n- **Target the combined query.** \"[Tool A] + [Tool B] integration\", \"how to\n  [job] with [A] and [B]\": queries neither brand ranks for alone.\n- **Ship original data when possible.** A joint survey or benchmark across both\n  customer bases is a link asset neither could produce alone. Publish method,\n  sample size, and date.\n- **Both brands named consistently** in title, byline, and copy so AI answers\n  attribute the claim to both.\n- **Integration pages:** list the partner in each side's integration\n  directory with a link, a short how-it-works, and the shared customer story.\n\nTechnical checks route to `suede-seo-audit`; topic choice to\n`suede-content-strategy`.\n\n---\n\n## Brainstorming Partner Campaigns\n\nWhen brainstorming with a specific partner, consider:\n\n### 1. Shared Audience Moments\n\n- What trigger events matter to both audiences?\n- What seasonal moments align with both products?\n- What industry trends affect both customer bases?\n\n### 2. Combined Value Propositions\n\n- What can customers achieve with both tools that they can't with one?\n- What workflow does the combination enable?\n- What pain point does the integration solve?\n\n### 3. Unique Assets Each Brings\n\nInventory what each side brings across audience, content expertise, product\ncapabilities, brand credibility, and customer stories, and name which asset the\ncampaign actually depends on.\n\n---\n\n## Approaching Potential Partners\n\n### Outreach gate (draft-only, hard stop)\n\nOutreach drafts are produced; outreach is never sent. At the handover: stop, name\nthe four variables in one line each: recipient, channel, visible sending\nidentity, exact message, state that the outcome is a draft and nothing has been\nsent, offer **approve \u002F revise \u002F drop**, and wait for the user's pick. The same\ngate covers sharing any customer or overlap data with the partner.\n\n### Cold Outreach Template\n\n```\nSubject: [Your Company] + [Their Company] co-marketing idea\n\nHey [Name],\n\nI'm [Role] at [Your Company]. We [one-line description].\n\nI noticed we share a lot of the same audience, [specific observation about overlap].\n\nI have an idea for [specific campaign type] that could work well for both of us: [one-sentence pitch].\n\nWould you be open to a quick call to explore?\n\n[Your name]\n```\n\n### What to Prepare for the Call\n\n1. **Account overlap data** (if available via Crossbeam\u002FReveal)\n2. **2-3 specific campaign ideas** (not just \"let's do something\")\n3. **Your audience metrics** (list size, traffic, engagement)\n4. **Examples of past partnerships** (shows you can execute)\n5. **Clear ask** (what you want from them, what you'll provide)\n\n---\n\n## Structuring the Partnership\n\n### Key Questions to Align On\n\n- **Lead ownership**: gated\u002Fsplit (one shared form, agreed split, written data\n  and consent terms) or each-keeps-own (no shared list: the default until data\n  terms are agreed). The format chosen from `references\u002Fcampaign-formats.md`\n  names which arrangement it assumes.\n- **Promotion commitments**: What will each party do to promote?\n- **Asset creation**: Who creates what? Who approves?\n- **Timeline**: When does each phase happen?\n- **Success metrics**: How will you measure success?\n- **Follow-up**: Will you do more together if it works?\n\n### Simple Co-Marketing Agreement Outline\n\n1. **Campaign description**: What you're doing together\n2. **Responsibilities**: Who does what\n3. **Timeline**: Key dates and deadlines\n4. **Lead handling**: How leads are captured, shared, followed up\n5. **Promotion**: Minimum commitments from each side\n6. **Branding**: Logo usage, approval process\n7. **Costs**: Who pays for what (if any)\n8. **Metrics sharing**: What data you'll share post-campaign\n\n---\n\n## Measuring Co-Marketing Success\n\n- Leads generated (total and per partner)\n- Lead quality (MQL\u002FSQL conversion rate)\n- Revenue attributed\n- Audience growth (new subscribers, followers)\n- Content engagement (views, downloads, shares)\n\nBaselines and targets come from the user's current analytics, not from a generic\nbenchmark. Report only metrics both sides agreed to share.\n\n---\n\n## Co-Marketing Checklist\n\n### Partner Identification\n- [ ] List tools your customers already use\n- [ ] Check Crossbeam\u002FReveal for account overlap\n- [ ] Score candidates on all six criteria and apply the pursue\u002Fdrop rule (cap 5)\n- [ ] Research their past co-marketing activities\n\n### Campaign Planning\n- [ ] Agree on campaign type and goals\n- [ ] Define lead sharing arrangement\n- [ ] Assign responsibilities and deadlines\n- [ ] Set success metrics\n\n### Execution\n- [ ] Create shared assets (landing page, content, etc.)\n- [ ] Coordinate promotion schedules\n- [ ] Brief both teams on talking points\n\n### Post-Campaign\n- [ ] Share metrics with partner\n- [ ] Debrief on what worked\u002Fdidn't\n- [ ] Discuss future collaboration opportunities\n\n---\n\n## Output Format\n\nThis skill returns one of two deliverables. Copy the matching skeleton verbatim\nfrom [references\u002Foutput-templates.md](references\u002Foutput-templates.md), open that\nfile before writing either one.\n\n**Scored partner shortlist** must contain:\n\n1. The ranked shortlist (max 5) with all six criterion scores per partner\n2. A scored-and-dropped list naming the failing criterion for each\n3. Open questions for any criterion scored `?`\n4. Candidates not pursued this round\n5. A recommended first move with a format named from `references\u002Fcampaign-formats.md`\n\n**Joint campaign plan** must contain:\n\n1. Campaign format (named from the formats reference), goal, and its one proving metric\n2. Value exchange on both sides\n3. Responsibilities and timeline with an owner and approver per phase\n4. Lead handling: gated\u002Fsplit or each-keeps-own, with the capture path\n5. Promotion commitments, branding approvals, and maximum approved cost\n6. Measurement plan with agreed shared metrics and a debrief date\n7. An approval-status line stating nothing has been sent, published, or committed\n\n---\n\n## Task-Specific Questions\n\n1. Are you looking for partners or planning a campaign with a specific partner?\n2. What type of co-marketing are you most interested in? (content, events, integrations, community)\n3. What's your audience size? (email list, social following, traffic)\n4. Do you have existing integration partners?\n5. Have you done co-marketing before? What worked\u002Fdidn't?\n6. What's your timeline and budget for co-marketing?\n\n---\n\n## Tool Integrations\n\nThis pack does not ship partner-platform connectors. Use an authorized product\nUI, current export, API, or installed connector and verify the provider's\ncurrent official documentation before reading or changing partner data.\n\nSelect capabilities against the campaign:\n\n- Privacy-safe aggregate account overlap, with minimum cohort thresholds\n- Partner records, owners, approvals, commitments, and deal registration\n- Shared asset review, version history, deadlines, and publication approval\n- Source-specific links or codes and agreed lead\u002Frevenue attribution\n- Export, deletion, access control, and audit-history requirements\n\n---\n\n## Boundaries\n\n- Do not claim a partnership, audience overlap, endorsement, reach, or committed deliverable without evidence from both sides.\n- Do not contact partners, share customer lists, sign terms, spend budget, or publish joint work without explicit authorization.\n- Do not decide ownership, licensing, attribution, lead-sharing, or revenue-sharing terms for the parties.\n- Do not expose private customer or partner data to prove overlap; use approved aggregate or privacy-safe methods.\n\n## Routing\n\n- Need referral or affiliate mechanics -> use `suede-referrals`.\n- Need launch sequencing and release assets -> use `suede-launch-packaging`.\n- Need co-created editorial planning -> use `suede-content-strategy`.\n- Need partner-facing collateral -> use `suede-sales-enablement`.\n- Need earned media for a joint launch announcement -> use `suede-public-relations`.\n- From those skills, route partner selection and joint-campaign design back to `suede-co-marketing`.\n",{"name":5,"metadata":55,"description":7},{"version":56,"display-name":57},"2.1.0","Suede AI Co-Marketing Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-co-marketing",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-co-marketing",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-co-marketing",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-co-marketing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-co-marketing\u002FSKILL.md",true,[82,88,92,96,100,104],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"agents\u002Fopenai.yaml","REFERENCE","参考文档",542,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-co-marketing\u002Fagents\u002Fopenai.yaml",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"CARD.md",4391,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-co-marketing\u002FCARD.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"evals\u002Fevals.json",6912,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-co-marketing\u002Fevals\u002Fevals.json",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fcampaign-formats.md",2744,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-co-marketing\u002Freferences\u002Fcampaign-formats.md",{"path":101,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Foutput-templates.md",2026,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-co-marketing\u002Freferences\u002Foutput-templates.md",{"path":105,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fworked-contract.md",1800,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-co-marketing\u002Freferences\u002Fworked-contract.md",[109,119,127,135,143,151],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":118},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":118},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":118},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":118},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":118},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":155,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":118},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]