- name
SKILL.md
Beceri dosyası yayıncının deposunda kalır.
Kopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a cursor -yKopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a claude-code -yKopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a codex -yKopyalanan komutu bir terminale yapıştırın. Bu SKILL.md dosyasını ilgili ajana kurar.
npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a grok -yKopyalanan mesajı bir Grok Bot sohbetinde gönderin. Bot bu SKILL.md dosyasını GitHub'dan alır ve tüm Bot'larınızın paylaştığı becerilere ekler.
Install this skill: https://github.com/Ootto-AI/claude-content-skills/tree/HEAD/skills/community-engagement-planYayıncıdan
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.mdGenel bakış
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.
SSS
skills/community-engagement-plan/SKILL.md dosyasını yayıncıdan indirin veya yolu kopyalayıp depoyu açın. PlugMCP beceriyi listeler, dosyayı barındırmaz.
Yayıncı bunu şurada tutuyor: https://github.com/Ootto-AI/claude-content-skills.
Claude, Cursor, Codex ve Grok Build, yayıncının deposundan eklediğiniz bir SKILL.md dosyasını okuyabilir. Grok Bot, becerinin GitHub klasör bağlantısını bir sohbette gönderdiğinizde onu kurar.