- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/Ootto-AI/claude-content-skills/tree/HEAD/skills/community-engagement-planFrom the publisher
Set a useful participation standard: where the team can add value, what it can truthfully say, and when it should not speak.
Ask which owned or external community is in scope, its rules, the team's legitimate role, the topic, and any moderator or brand constraints. Read supplied rules before proposing interaction. If the community does not welcome promotion or brand participation, do not design a workaround.
Use real questions, recurring friction, useful resources, corrections, and support needs as evidence. Classify participation as answer, clarification, acknowledgement, escalation, or observation. Give priority to helping people complete a task, not inserting the brand into every thread.
Define approved facts, prohibited claims, tone, disclosure, escalation owners, response windows, and cases that require silence or human review. Route product bugs, safety concerns, account-specific issues, legal questions, and hostile interactions to the appropriate owner rather than improvising publicly.
Set a small cadence to review unanswered questions, recurring themes, and useful contributions. Capture aggregate learning for social-listening. Measure quality through resolved questions, informed feedback, and community trust signals where available, not reply volume alone.
Use social-listening to identify recurring questions and comment-responder for a particular reply. Use campaign-brief only when a campaign has a legitimate community role. Feed patterns into audience-personas and positioning-audit; never treat a community plan as a mass-outreach mechanism.
Use when a team needs a deliberate, human-led plan for participating in comments, communities, or audience conversations around an approved topic. Trigger phrases include "plan community engagement",
---name: community-engagement-plandescription: Use when a team needs a deliberate, human-led plan for participating in comments, communities, or audience…---# skills/community-engagement-plan/SKILL.mdOverview
Use when a team needs a deliberate, human-led plan for participating in comments, communities, or audience conversations around an approved topic. Trigger phrases include "plan community engagement", "how should we join this conversation?", "what should we reply to?", "make an engagement playbook", and "how do we support this community?". Do not use this to automate unsolicited replies, manipulate conversations, impersonate people, or create comment copy at scale; use comment-responder for a specific approved reply and social-listening to analyse recurring themes.
FAQ
Download skills/community-engagement-plan/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/Ootto-AI/claude-content-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.