community-response
Skill3 starsChanged 5 months agoMITView on GitHub
Draft replies to comments and DMs - engagement, FAQs, objections, and light moderation - in the creator's voice. Use when managing community interaction or building reply templates.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analytics-reviewSkill
- caption-hashtagsSkill
- carousel-postSkill
- content-calendarSkill
- content-ideationSkill
- engagement-strategySkill
- facebook-postSkill
- feed-postSkill
- hook-writerSkill
- meta-discoverySkill
- reel-scriptSkill
- repurposeSkill
- sponsorship-pitchSkill
- story-sequenceSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Spam/trolls: don't feed; delete/hide/block per your boundaries.
- Very specific: line 25
Don't make promises or claims you can't back (truth-telling).
≈ “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-response
Replies build relationships and reach (early comment replies boost a post). Sound like a human, not a bot.
Process
- Categorize: genuine question, praise, objection/criticism, sales/collab inquiry, spam/troll.
- Reply in voice:
- Questions/FAQs: answer concisely + add value; reusable templates for repeats.
- Praise: warm, specific, not just "thanks!"; invite a follow/next step lightly.
- Objections/criticism: acknowledge, don't get defensive; correct misinformation calmly with facts.
- Inquiries: point to the media kit / DMs (
sponsorship-pitch). - Spam/trolls: don't feed; delete/hide/block per your boundaries.
- Reply fast on new posts - early engagement signals value to Meta.
Output
- Drafted replies per category + a few reusable templates, in the creator's tone.
Guardrails
- Authentic voice, not canned corporate replies (
authenticity-voice). - Don't make promises or claims you can't back (
truth-telling); don't argue publicly with bad-faith trolls.
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.

