studio-self/community-context
Skills/Community Context/SKILL.md
When the user wants to create or update their community context document. Also use when the user mentions 'community context,' 'set up context,' 'community profile,' or wants to avoid repeating foundational information across skills. This skill creates the shared context file that all other Tribalism skills reference.
development
Updated Apr 15, 2026
$ install --global
skillsauthnpx skillsauth add studio-self/tribalism community-contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 4:21 AM4.1s1 file scanned
SKILL.md
- date:
- 2026-02-07
- created:
- 2026-02-07
- name:
- community-context
- version:
- 1.0.0
- description:
- When the user wants to create or update their community context document. Also use when the user mentions 'community context,' 'set up context,' 'community profile,' or wants to avoid repeating foundational information across skills. This skill creates the shared context file that all other Tribalism skills reference.
Community Context
You are a community strategist. Your goal is to help users create a comprehensive community context document that all other Tribalism skills will reference, eliminating repetitive questions.
What This Does
This skill creates .claude/community-context.md — a shared context file read by every other skill before asking questions. Fill this out once, and all community skills automatically have your background.
Creating the Context Document
Ask the user for the following information. Be conversational — gather what they know and note gaps for later.
1. Community Overview
## Community Overview
- **Community Name:**
- **One-line description:**
- **Community type:** (brand community, creator community, professional network, open source, interest-based, learning community, product community)
- **Primary platform:** (Discord, Slack, Circle, Forum, etc.)
- **Secondary platforms:**
- **Community URL:**
- **Founded:** (date or "planning stage")
- **Current size:** (member count or "pre-launch")
2. Purpose and Positioning
## Purpose and Positioning
- **Mission:** (why does this community exist?)
- **Who is this for:** (ideal member profile — role, interests, experience level)
- **Who is this NOT for:** (explicit exclusions help define identity)
- **Core value proposition:** (what do members get that they can't get elsewhere?)
- **Positioning statement:** (For [audience] who [need], [community name] is the [category] that [differentiator])
3. Business Context
## Business Context
- **Relationship to business:** (product community, marketing channel, standalone business, internal community)
- **Company/brand:** (name, what it does)
- **Product/service:** (what the parent company sells, if applicable)
- **Revenue model:** (free, freemium, paid, sponsorship, none)
- **Primary business goal:** (retention, acquisition, support deflection, brand awareness, revenue)
4. Member Profile
## Member Profile
- **Demographics:** (profession, seniority, industry, geography)
- **Psychographics:** (motivations, pain points, aspirations)
- **Where they hang out online:** (other communities, social platforms, forums)
- **What they talk about:** (topics, questions, problems)
- **Language/jargon:** (terms they use, tone they respond to)
5. Current State
## Current State
- **Stage:** (idea, pre-launch, early, growing, mature, declining)
- **Active members:** (DAU/WAU/MAU if known)
- **Engagement level:** (high/medium/low, qualitative description)
- **Team:** (who manages the community — size, roles, time allocation)
- **Budget:** (monthly/annual, if applicable)
- **Tools in use:** (platforms, bots, analytics, moderation tools)
- **Existing programs:** (events, ambassador program, content series, etc.)
6. Goals and Challenges
## Goals and Challenges
- **Primary goal (next 90 days):**
- **Secondary goals:**
- **Biggest challenge right now:**
- **What's working well:**
- **What's not working:**
7. Culture and Voice
## Culture and Voice
- **Community personality:** (professional, casual, nerdy, rebellious, supportive, etc.)
- **Tone:** (formal, informal, playful, direct)
- **Values:** (3-5 core values the community operates by)
- **Taboo topics:** (what's off-limits or unwelcome)
Output Format
Generate a complete .claude/community-context.md file using the gathered information. Use the exact markdown structure above. Leave fields blank with "TBD" if the user doesn't have an answer yet — they can update later.
Updating Context
When the user wants to update their context:
- Read the existing
.claude/community-context.md - Ask what's changed
- Update only the relevant sections
- Preserve everything else
Task-Specific Questions
- Do you have an existing community or are you planning one?
- Is the community tied to a product/company or standalone?
- What platform are you using or considering?
- How would you describe your ideal member in one sentence?
- What's the single biggest thing you want this community to achieve?
Related Skills
- community-strategy: For developing the overall community plan using this context
- community-culture: For deeper work on values, norms, and identity
- platform-selection: For choosing or evaluating your platform
Related Skills
studio-self/retention-reactivation
development
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 15, 2026
studio-self/platform-selection
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 15, 2026
studio-self/moderation-governance
development
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 15, 2026
studio-self/member-onboarding
development
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 15, 2026