plugins/pm-social/skills/community-management-playbook/SKILL.md
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
npx skillsauth add mohitagw15856/pm-claude-skills community-management-playbookInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill produces a complete community management playbook covering response frameworks, tone guidelines, comment moderation rules, DM handling, crisis and escalation paths, response templates, and community health metrics. Output gives a community manager or social media team everything they need to manage public interactions consistently, professionally, and at speed.
Ask the user for these if not provided:
Version: 1.0 Platforms covered: [List] Team: [Names or roles] Last updated: [Date]
[2–3 sentences on what's at stake: brand reputation, customer loyalty, algorithm signals, trust-building. Frame community management as a business function, not just social admin.]
Our community management goals:
Use this decision tree for every comment or message:
Is it spam, phishing, or dangerous content?
→ YES: Delete immediately. Report if platform requires. Log in moderation tracker.
→ NO: Continue ↓
Is it a hate comment, harassment, or offensive content?
→ YES: Hide or delete. Consider account block. Escalate if ongoing. See Section 6.
→ NO: Continue ↓
Is it a customer complaint or support question?
→ YES: Respond within SLA. Acknowledge, empathise, resolve or redirect. See Section 4.
→ NO: Continue ↓
Is it positive — praise, testimonial, or user win?
→ YES: Like + reply with warm acknowledgement. Flag for social proof content if suitable.
→ NO: Continue ↓
Is it a question about the brand, product, or content?
→ YES: Answer clearly and helpfully. Include a CTA if relevant.
→ NO: Continue ↓
Is it a general conversation starter or neutral engagement?
→ YES: Engage authentically — like, reply briefly, or ask a follow-up question.
| Channel | Comment type | Target response time | Owner | |---|---|---|---| | [Instagram] | Customer complaint | [2 hours (business hours)] | [CM Lead] | | [Instagram] | General comment / question | [Same day] | [CM team] | | [Instagram] | DM | [4 hours (business hours)] | [CM Lead] | | [LinkedIn] | Professional comment / question | [4 hours (business hours)] | [CM / Marketing] | | [X / Twitter] | Public reply / mention | [2 hours (business hours)] | [CM Lead] | | [X / Twitter] | DM | [4 hours (business hours)] | [CM team] | | [Facebook] | Comment | [4 hours (business hours)] | [CM team] | | [TikTok] | Comment on promoted post | [8 hours] | [CM team] | | [YouTube] | Comment | [24 hours] | [CM team] |
Out-of-hours coverage:
These are starting-point templates — always personalise with the person's name and specific context.
Praise / testimonial:
"Thank you so much, [name]! 🙌 This genuinely made our day. So glad [product/service] is working for you. [Add specific personal note if possible]."
User-generated content / sharing their experience:
"Love seeing this, [name]! Thanks for sharing 🙌. [Relevant genuine comment on their specific post or experience]."
Review or recommendation:
"Thank you for taking the time to share this, [name] — really appreciate it. [Add genuine specific reaction]. If you ever want to [next step / share more / join community], we'd love to have you."
Feature question:
"Great question, [name]! [Answer clearly in 1–3 sentences]. If you'd like more detail, [link to docs / help centre / DM us]. Happy to help with anything else!"
Pricing / availability question:
"[Answer] — [link if relevant]. Feel free to DM us if you need anything specific. 😊"
"Is this available in [region/format]?" question:
"[Answer with current availability]. If that's changed, you'll always see it first at [link / newsletter sign-up / our channels]. 🙌"
Product issue — acknowledged, redirecting to support:
"Hi [name], really sorry to hear this — that's definitely not the experience we want for you. 😔 Could you DM us with [order number / account email / details]? We'll get this sorted as quickly as possible."
Shipping / fulfilment complaint:
"Hi [name], thank you for letting us know and I'm so sorry for this. We want to make it right. Please DM us with your order reference and we'll investigate right away."
General dissatisfaction:
"Hi [name], I'm sorry to hear you're not happy — your feedback genuinely matters to us. Could you DM us or email [support email] so we can understand what happened and fix it? We really do want to get this right."
Public complaint that needs urgent attention:
"Hi [name], I can see why that would be frustrating and I want to make sure we sort this out properly. I'm going to DM you now — please look out for a message from us."
Polite but persistent critic:
"Hi [name], thank you for the honest feedback — we do read and take this seriously. We can't always respond to every individual point publicly, but if you'd like to share more detail, [DM us / email us at X]. We're genuinely working on [relevant area] and appreciate you holding us accountable."
Misinformation or incorrect claim about the brand:
"Hi [name], just wanted to gently clarify — [correct the record factually in 1–2 sentences]. Happy to share more if useful! [Link to source / official page if relevant]."
Competitor attack or negative comparison:
[Do NOT engage publicly with competitive comparisons. Respond only if there's factual misinformation. Template: "Hi [name], happy to share what makes [brand] work for our customers — feel free to DM us if you'd like to know more."]
First DM response — complaint:
"Hi [name], thanks for reaching out. I'm [name] from the [brand] team. I've seen your [comment/message] and want to make sure we get this sorted for you properly. Could you share [details needed — order number, email, screenshots]? I'll personally make sure this is resolved."
First DM response — support question:
"Hi [name]! Thanks for getting in touch. Happy to help — [answer or next step]. If you need anything else, just reply here. 😊"
Issue resolved — closing DM:
"Glad we could sort that out, [name]! If you ever need anything else, we're here. Have a great [day/weekend]! 🙌"
Content that must be deleted immediately:
Content that should be hidden (not deleted) — review within 4 hours:
Content that should be left (even if negative) — respond and monitor:
Account-level actions:
| Action | When to use | |---|---| | Comment hide | First instance of borderline content | | Comment delete | Clear rule violation | | User block | Repeated harassment / spam after warning | | Report to platform | Content that may breach platform T&Cs or laws |
"Never delete to silence" rule: Never delete a genuine complaint or criticism just because it's uncomfortable. Deleting legitimate negative feedback damages trust more than the original complaint.
Tier 1 — CM handles directly:
Tier 2 — Escalate to [Marketing Lead / Brand Manager] within 2 hours:
Tier 3 — Escalate to [CMO / Founder / CEO] immediately:
Out-of-hours escalation contacts:
| Situation | Tone | Example phrase | Avoid | |---|---|---|---| | Complimenting content | Warm, genuine, specific | "This genuinely made our day 🙌" | Generic "Thank you!" | | Answering a product question | Helpful, clear, not jargony | "Great question — here's exactly how it works…" | "Per our FAQs…" | | Resolving a complaint | Empathetic, responsible, action-oriented | "Really sorry to hear this — let's sort it out." | "This is not our fault" | | Engaging with light content | Playful, natural, on-brand | [Match the energy of the post — don't be stiff] | Corporate speak | | Handling criticism | Measured, honest, not defensive | "We hear you and we're working on it." | "As per our T&Cs…" | | Addressing a crisis | Calm, clear, factual, empathetic | "We're aware of this and are treating it as an urgent priority." | Defensive or dismissive |
Emoji use: [Define brand's emoji policy — e.g. "Use emojis sparingly — 1 per response max, only on positive interactions. Never on complaints or sensitive topics."]
Track these weekly:
| Metric | What it measures | Target | Current | |---|---|---|---| | Average response time | Speed of community management | [≤ X hours] | [X hours] | | Response rate | % of comments/DMs replied to | [≥ X%] | [X%] | | Comment sentiment ratio | Positive : Neutral : Negative split | [≥ X% positive] | [X%] | | Escalation rate | % of interactions escalated | [≤ X%] | [X%] | | DM resolution time | Time to resolve a DM complaint | [≤ X hours] | [X hours] | | Content reports / removals | Volume of content moderated | [Track trend] | [X/week] |
Weekly CM review (15 min):
| Platform | Key nuance | Best practice | |---|---|---| | Instagram | Comments move fast on Reels; DMs high volume | Prioritise Reel comments; use saved replies for FAQ DMs | | LinkedIn | Professional audience; public replies visible to networks | Keep responses professional; avoid humour on complaints | | X / Twitter | Real-time; pile-ons escalate fast | Monitor with keyword alerts; act on Tier 2 triggers quickly | | TikTok | Comment culture is more casual; meme responses ok | Match platform tone but keep brand voice; don't try too hard | | YouTube | Older comments resurface regularly | Monitor new comments on older videos; set up notifications | | Facebook | Groups + page comments; older audience | More formal tone; monitor group dynamics separately | | Discord | Real-time community; requires moderators | Designate community moderators; publish community rules prominently |
development
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners.
development
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
development
Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.
development
Optimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.