Agent Skillscbrock84/headcount › partnership-marketing

partnership-marketing

GitHub

指导开展合作营销,涵盖伙伴评估、协议结构化、社区运营及效果测量。用于寻找合作伙伴、策划联合活动或创作者交易,并评估合作价值与协调成本。

plugins/marketing/skills/partnership-marketing/SKILL.md cbrock84/headcount

Trigger Scenarios

寻找和评估潜在合作伙伴 制定联合营销活动或创作者交易方案 规划社区建设策略

Install

npx skills add cbrock84/headcount --skill partnership-marketing -g -y
More Options

Non-standard path

npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/partnership-marketing -g -y

Use without installing

npx skills use cbrock84/headcount@partnership-marketing

指定 Agent (Claude Code)

npx skills add cbrock84/headcount --skill partnership-marketing -a claude-code -g -y

安装 repo 全部 skill

npx skills add cbrock84/headcount --all -g -y

预览 repo 内 skill

npx skills add cbrock84/headcount --list

SKILL.md

Frontmatter
{
    "name": "partnership-marketing",
    "description": "Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, and community building. Use this to find and evaluate partners, structure a joint campaign or creator deal, plan a community strategy, or decide whether a partnership is worth the coordination cost."
}

Partnership marketing

Borrowing an audience is the cheapest reach available and the easiest to do badly.

Affiliates sit next to this rather than inside it: they are a paid channel with commercial terms, their own mechanics and their own fraud controls. revenue:referral-programs covers them.

Evaluating a partner

Fit matters more than size. The test is overlap of audience with non-overlap of offering: they serve the same people, and you do not compete for the same budget.

Check before committing:

  • Audience overlap — same buyer, or merely same industry? Same industry is not enough.
  • Engagement over follower count. A small responsive audience beats a large indifferent one, and follower counts are the easiest number to inflate.
  • Their audience's trust in them. You are borrowing that, and you can spend it.
  • What they get. A partnership that only serves you does not get executed, whatever was agreed.

Structuring

Write down, before anything ships: what each side produces, what each promotes and when, how leads or revenue are attributed, who owns the assets afterward, and what happens if one side does not deliver. Most partnerships fail on the last two, discovered late.

For creator deals specifically: pay for the work, not for promises about performance; require disclosure without exception; and give creative latitude — audiences detect a script and the whole value is that they trust the person's own voice.

Community

A community is a long commitment that pays late. Do not start one to hit a quarterly number.

It works when members get value from each other rather than only from you. That requires a reason to return that is not your product, visible norms, and consistent presence — a community that is quiet for a month does not recover easily. Seed it deliberately with people who will actually post; an empty room stays empty.

Measuring

Attribute honestly. Partnership traffic is often assisted rather than last-touch, so last-touch attribution will under-count it and you will kill something that was working. Agree the measurement method before launch, when neither side is defending a result.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Partner with someone whose audience you have not actually looked at.
  • Run a creator campaign without disclosure. The regulatory exposure is real and the reputational cost is worse.
  • Judge a community on member count.

Version History

  • 98d1c17 Current 2026-09-22 00:30

    扩展了来源目录至所有部门,将参考来源从50个增加至181个,覆盖技能数从36个增至144个,并更新了验证结果。

  • 9cbf340 2026-09-08 17:57

    修复了技能库中存在的多个问题:统一了 'Never' 规则块的标点风格以符合规范;修正了处理含空格或非ASCII字符文件路径时的检测逻辑;解决了悬空引用和冲突阈值问题;调整了部分描述以避免职责重叠。

  • d58a7ee 2026-09-02 21:07

Same Skill Collection

plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md
plugins/corporate-strategy/skills/market-entry/SKILL.md
plugins/corporate-strategy/skills/mergers-and-acquisitions/SKILL.md
plugins/corporate-strategy/skills/portfolio-strategy/SKILL.md
plugins/corporate-strategy/skills/scenario-planning/SKILL.md
plugins/corporate-strategy/skills/strategic-alliances/SKILL.md
plugins/customer-experience/skills/chief-customer-officer/SKILL.md
plugins/customer-experience/skills/customer-onboarding-and-implementation/SKILL.md
plugins/customer-experience/skills/customer-success-management/SKILL.md
plugins/customer-experience/skills/escalation-management/SKILL.md
plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md
plugins/customer-experience/skills/support-operations/SKILL.md
plugins/customer-experience/skills/voice-of-customer/SKILL.md
plugins/data-analytics/skills/ai-ml-governance/SKILL.md
plugins/data-analytics/skills/business-intelligence/SKILL.md
plugins/data-analytics/skills/chief-data-officer/SKILL.md
plugins/data-analytics/skills/data-engineering/SKILL.md
plugins/data-analytics/skills/data-governance/SKILL.md
plugins/data-analytics/skills/data-modeling/SKILL.md
plugins/demand-generation/skills/ai-search-optimization/SKILL.md
plugins/demand-generation/skills/app-store-optimization/SKILL.md
plugins/demand-generation/skills/experimentation/SKILL.md
plugins/demand-generation/skills/landing-page-cro-expert/SKILL.md
plugins/demand-generation/skills/lead-capture/SKILL.md
plugins/demand-generation/skills/lifecycle-messaging/SKILL.md
plugins/demand-generation/skills/listing-distribution/SKILL.md
plugins/demand-generation/skills/marketing-analytics/SKILL.md
plugins/demand-generation/skills/paid-advertising/SKILL.md
plugins/demand-generation/skills/programmatic-seo/SKILL.md
plugins/demand-generation/skills/seo-strategy/SKILL.md
plugins/executive/skills/ai-research-analyst/SKILL.md
plugins/executive/skills/business-growth-consultant/SKILL.md
plugins/executive/skills/chief-executive/SKILL.md
plugins/executive/skills/fundraising-and-investor-relations/SKILL.md
plugins/executive/skills/saas-idea-validator/SKILL.md
plugins/finance/skills/budgeting-and-forecasting/SKILL.md
plugins/finance/skills/capital-allocation/SKILL.md
plugins/finance/skills/capital-structure-and-covenants/SKILL.md
plugins/finance/skills/cost-accounting/SKILL.md
plugins/finance/skills/financial-modeling/SKILL.md
plugins/finance/skills/financial-reporting-and-close/SKILL.md
plugins/finance/skills/financial-statement-analysis/SKILL.md
plugins/finance/skills/internal-controls-and-audit/SKILL.md
plugins/finance/skills/revenue-recognition/SKILL.md
plugins/finance/skills/tax/SKILL.md
plugins/finance/skills/treasury-and-liquidity/SKILL.md
plugins/finance/skills/unit-economics/SKILL.md
plugins/it-operations/skills/backup-and-recovery/SKILL.md
plugins/it-operations/skills/chief-information-officer/SKILL.md
plugins/it-operations/skills/cloud-administration/SKILL.md

Metadata

Files
0
Version
98d1c17
Hash
937e1558
Indexed
2026-09-02 21:07

ホーム - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-09-23 02:11
浙ICP备14020137号-1