community-engage
Skill1 starsChanged 7 months agoMITView on GitHub
Manages community presence and engagement strategy. Triggers ONLY when: user asks to find communities, plan community engagement, or draft community responses. Do NOT trigger when: creating content (use content-create) or distributing content (use content-distribute).
In this repository30 other files it gives its agents.
- claude.mdCLAUDE.md
- biz-thinkSkill
- biz-validateSkill
- brand-buildSkill
- content-createSkill
- content-distributeSkill
- copy-craftSkill
- data-decideSkill
- finance-opsSkill
- growth-trackSkill
- infra-opsSkill
- issue-createSkill
- legal-guardSkill
- post-mergeSkill
- pre-codeSkill
- pre-commitSkill
- pre-prSkill
- product-evalSkill
- project-initSkill
- retroSkill
- roadmap-steerSkill
- sales-closeSkill
- search-evalSkill
- self-reviewSkill
- sopSkill
- staging-verifySkill
- support-opsSkill
- test-gateSkill
- ux-auditSkill
- work-breakdownSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 24 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈24
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Search the web for communities where the target audience discusses their problems.
- Distinctive: line 16
Reddit: search for subreddits by topic keywords, check subscriber count and post frequency
- Distinctive: line 17
Discord: search Disboard, Discord.me, and Top.gg for relevant servers
- Distinctive: line 18
Slack: search Slofile, Standuply's Slack community list, and Google "[topic] slack community"
- Distinctive: line 22
LinkedIn Groups: search for active groups (most are dead — verify activity before joining)
- Distinctive: line 33
Read the last 50 posts/threads — are these actually your target users?
- Distinctive: line 34
Check activity level — are posts getting responses?
- Distinctive: line 35
Read the rules — is commercial activity tolerated, restricted, or banned?
- Distinctive: line 36
Look for competitors — are similar products mentioned positively, negatively, or not at all?
- Distinctive: line 66
Use your real name/identity — never create fake accounts
- Distinctive: line 70
Use Playwright MCP to monitor communities daily and draft responses.
- Distinctive: line 88
Only after meeting Phase 2 milestones.
- Distinctive: line 92
Always disclose that you're the creator/affiliated
- Distinctive: line 93
If the community has rules about self-promotion, follow them exactly
- Distinctive: line 94
Never force a mention — if your product isn't the best answer, recommend what is
- Distinctive: line 101
Check for new questions/discussions in your area
- Distinctive: line 116
Every month, evaluate each community:
- Distinctive: line 125
Drop: no engagement after 60 days of consistent effort
- Distinctive: line 142
Transparency: if asked, always disclose you're affiliated with the product
- Distinctive: line 143
Authenticity: never create multiple accounts, fake reviews, or astroturf
- Distinctive: line 144
Respect: follow every community's rules, even inconvenient ones
- Distinctive: line 145
The embarrassment test: if you would be embarrassed to admit the response was AI-assisted or strategically motivated, don't post it
- Distinctive: line 146
Reddit and HN: NEVER automate posting. Draft content only.
- Distinctive: line 148
Use Playwright MCP for:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Community Engagement SOP
Phase 1: Find Watering Holes
Reference: Etienne Garbugli, "Lean B2B" — go where your users already gather.
Step 1: Map Potential Communities
Search the web for communities where the target audience discusses their problems. Check:
- Reddit: search for subreddits by topic keywords, check subscriber count and post frequency
- Discord: search Disboard, Discord.me, and Top.gg for relevant servers
- Slack: search Slofile, Standuply's Slack community list, and Google "[topic] slack community"
- Forums: product-specific forums, Stack Overflow tags, specialized communities (e.g., Indie Hackers, Elixir Forum)
- Newsletters: Substack, Beehiiv newsletters in the niche — comment sections are communities too
- Twitter/X: identify key accounts and their reply communities
- LinkedIn Groups: search for active groups (most are dead — verify activity before joining)
Output a table:
| Community | Platform | Members | Posts/Week | Audience Match | Commercial Tolerance |
Step 2: Validate Each Community
For each candidate community, use Playwright MCP to browse and evaluate:
- Read the last 50 posts/threads — are these actually your target users?
- Check activity level — are posts getting responses? How old is the latest post?
- Read the rules — is commercial activity tolerated, restricted, or banned?
- Look for competitors — are similar products mentioned positively, negatively, or not at all?
- Assess tone — technical, casual, meme-heavy, professional? You must match it.
Score each community 1-5 on: audience fit, activity, commercial tolerance, effort required.
Step 3: Select 5-8 Communities
Pick based on:
- Audience fit score >= 4
- Activity level >= 3
- Commercial tolerance >= 2 (must allow SOME mention of tools/products)
- Manageable total time commitment (all communities combined <= 1 hour/day)
Quality over quantity. Being active in 5 communities beats being invisible in 20.
Phase 2: Value-First Engagement
Reference: Mary Thengvall, "The Business Value of Developer Relations."
Step 4: Weeks 1-4 — Pure Value, Zero Promotion
This phase is non-negotiable. For the first 2-4 weeks in each community:
- Answer questions — find unanswered questions in your area of expertise. Write genuinely helpful, thorough responses.
- Share useful resources — link to helpful articles, tools, tutorials (NOT your own product).
- Provide troubleshooting — help people debug problems, even if unrelated to your product.
- Engage in discussions — add thoughtful opinions, share relevant experiences.
Rules during this phase:
- ZERO product mentions. Not even subtle ones.
- Use your real name/identity — never create fake accounts
- Be genuinely helpful — if you're only helping to eventually promote, people will sense it
- Match the community's communication style (formal, casual, technical depth)
Use Playwright MCP to monitor communities daily and draft responses.
Step 5: Build Reputation
Track your reputation in each community:
- Reddit: karma in specific subreddits
- Discord: role level, reaction count on your messages
- Stack Overflow: reputation score in relevant tags
- Forums: post count, thank-you reactions, moderator recognition
- Twitter/X: follower growth from community interactions
Milestones before graduating to Phase 3:
- At least 10 helpful responses in the community
- Positive feedback (upvotes, thanks, follows) on at least 5 responses
- Recognized by at least 2 community members as a regular contributor
Step 6: Graduate to Mentioning Your Work
Only after meeting Phase 2 milestones. Rules:
- Mention your product ONLY when genuinely relevant to someone's specific question
- Frame it as "I built something that might help" — not "check out our product"
- Always disclose that you're the creator/affiliated
- If the community has rules about self-promotion, follow them exactly
- Never force a mention — if your product isn't the best answer, recommend what is
Phase 3: Ongoing Operations
Step 7: Daily Operations (20 min/day)
For the top 3 communities (highest engagement + conversion):
- Check for new questions/discussions in your area
- Respond to any replies to your previous comments
- Upvote/react to other helpful content (reciprocity builds goodwill)
- Draft responses — use Playwright MCP to browse, draft locally, post manually for Reddit/HN
Step 8: Weekly Operations
Every week:
- Identify high-intent threads — people actively asking for solutions you offer. Use web search and Playwright MCP to find phrases like "looking for", "any recommendations for", "alternative to [competitor]"
- Review engagement metrics — which communities are you getting the most positive responses in?
- Content ideas — note questions that keep coming up. These become content-create inputs.
- Respond to DMs/messages — people who reach out directly are highest-intent leads
Step 9: Monthly Review
Every month, evaluate each community:
| Community | Engagement Score | Referral Traffic | Signups | Conversion Rate | Time Invested |
Decision rules:
- Keep: positive engagement trend + measurable referral traffic
- Increase effort: high conversion rate but low volume
- Reduce effort: high time investment, low conversion
- Drop: no engagement after 60 days of consistent effort
Replace dropped communities with new candidates. Always be testing.
Step 10: Track in Auto Memory
Store in memory/communities.md for each community:
- Community name, platform, URL
- Join date
- Reputation/karma score (updated monthly)
- Number of posts/responses
- Referral traffic (from UTM or analytics)
- Conversions attributed
- Notes on tone, rules, best-performing content types
Ethical Guidelines
- Transparency: if asked, always disclose you're affiliated with the product
- Authenticity: never create multiple accounts, fake reviews, or astroturf
- Respect: follow every community's rules, even inconvenient ones
- The embarrassment test: if you would be embarrassed to admit the response was AI-assisted or strategically motivated, don't post it
- Reddit and HN: NEVER automate posting. Draft content only. User posts manually.
Use Playwright MCP for:
- Browsing communities to find relevant threads
- Reading community rules and recent posts
- Monitoring for new discussions matching target keywords
- Drafting responses (saved locally, not posted automatically on Reddit/HN)
Next Steps
Report to user: "Communities identified: [N]. Engagement status: [phase]. Key finding: [one line]"
Suggested next steps (user decides):
- Leads found → "Run sales-close"
- Questions surfaced → "Run content-create"
- Growing → "Run growth-track"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

