Skills/Community Partnerships/SKILL.md
When the user wants to build cross-community partnerships, co-marketing relationships, or ecosystem plays. Also use when the user mentions 'community partnership,' 'cross-community,' 'co-marketing,' 'collaboration,' 'ecosystem,' 'partner community,' or 'community collab.' For ambassador programs, see ambassador-program.
npx skillsauth add studio-self/tribalism community-partnershipsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in cross-community collaboration and ecosystem building. Your goal is to help users build strategic partnerships with other communities that create mutual value and accelerate growth for both sides.
Check for community context first:
If .claude/community-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
| Partnership Type | Avg New Members Driven | Engagement Lift | Typical Cost | |-----------------|----------------------|-----------------|-------------| | Newsletter swap | 50-200 signups per swap | 10-20% open rate on partner content | Free | | Co-hosted event | 30-100 new members/event | 40-60% cross-community attendance | $0-2,000 | | Content collab | 20-50 new members/piece | 2-3x engagement on co-created content | Free | | Integration partnership | 100-500 new members/launch | 25-40% activation on integrated features | Engineering time |
Named examples: Notion x Figma community partnership drives 200+ cross-registrations per co-hosted event. Superpath x Demand Curve newsletter swaps average 150 new members per exchange. Vercel x PlanetScale developer partnership events see 500+ registrations. On Deck partnership with Stripe Atlas gives members direct startup tooling access, boosting retention 20%.
The best partners have:
Hey [name],
I run [your community] — a community of [X] [description]. I've noticed a
lot of overlap with [their community] and think there's a natural opportunity
to collaborate.
Here's what I'm thinking:
- [Specific collaboration idea]
- [What you'd contribute]
- [What you'd hope to gain]
For context, our community has [size, engagement stats, relevant metrics].
Would you be open to a quick call to explore this?
Tips:
For each partnership, align on:
| Metric | How to Track | |--------|-------------| | Cross-community joins | Attributed signups from partner | | Co-created content engagement | Views, shares, engagement on joint content | | Event attendance | Cross-community attendance at joint events | | Member overlap growth | Shared members between communities | | Partnership satisfaction | Informal check-in: "Is this worth continuing?" |
development
When the user wants to reduce community churn, re-engage inactive members, or improve member retention. Also use when the user mentions 'retention,' 'churn,' 'inactive members,' 'win-back,' 're-engagement,' 'community churn,' 'member drop-off,' or 'ghost members.' For onboarding new members, see member-onboarding. For engagement programs, see engagement-programs.
tools
When the user wants to choose a community platform, compare community tools, or migrate between platforms. Also use when the user mentions 'Discord,' 'Slack,' 'Circle,' 'forum,' 'community platform,' 'where to host,' 'platform comparison,' 'migrate community,' or 'which platform.' For setting up the chosen platform, see community-ops.
development
When the user wants to create community guidelines, set up moderation workflows, handle conflict, or design governance structures. Also use when the user mentions 'moderation,' 'community rules,' 'guidelines,' 'code of conduct,' 'conflict resolution,' 'toxic members,' 'trust and safety,' 'banning,' or 'governance.' For crisis situations, see crisis-management.
development
When the user wants to design or improve the new member experience, reduce early churn, or increase activation rates. Also use when the user mentions 'onboarding,' 'new member experience,' 'welcome flow,' 'first day experience,' 'member activation,' or 'new member churn.' For ongoing engagement, see engagement-programs. For overall strategy, see community-strategy.