Agent skill

Community Management Playbook

by mohitagw15856 in mohitagw15856/pm-claude-skills

Build a community management playbook for a brand's social media channels.

MITAuto-check passedMarketing & SEO

Install Community Management Playbook

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill community-management-playbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills community-management-playbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/community-management-playbook .claude/skills/community-management-playbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
community-management-playbook
GitHub stars
1.4k
Token cost
~4k tokens
SKILL.md length
1,972 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Build a community management playbook for a brand's social media channels.

  • Works in 9 steps: Why Community Management Matters → Response Framework → Response Time SLAs → …
  • Asked to create guidelines for managing comments
  • SKILL.md covers Required Inputs, Output Structure, 1. Why Community Management… and 2. Response Framework, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Community Management Playbook is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering Social media marketing. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to create guidelines for managing comments
  • Community interactions
  • Define a moderation policy
  • Build response frameworks for social media community managers

Example prompts

  • “/community-management-playbook”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Why Community Management Matters
  2. Response Framework
  3. Response Time SLAs
  4. Response Templates
  5. Moderation Rules
  6. Escalation & Crisis Protocol
  7. Tone of Voice in Practice
  8. Community Health Metrics
  9. Platform-Specific Notes

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Community Management Playbook loads about 4k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 1,972 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~100
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,972 words, ~3,986 tokens.

Download SKILL.mdSave it as .claude/skills/community-management-playbook/SKILL.md (or your agent's skills folder).
name
community-management-playbook
description
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.

Community Management Playbook Skill

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.

Required Inputs

Ask the user for these if not provided:

  • Brand / product name
  • Active platforms — which channels need community management (Instagram, LinkedIn, X/Twitter, Facebook, TikTok, YouTube, Discord, Reddit, etc.)
  • Team structure — who manages community? (solo, small team, agency, rotating)
  • Brand tone of voice — how the brand sounds (e.g. warm and friendly / professional / witty / technical)
  • Primary community type — customers, fans, professional network, creators, users of a product
  • Common comment types — what kinds of interactions do you get? (support questions, complaints, praise, spam, trolls)
  • Response time SLA — how fast must the team respond? (e.g. within 2 hours on weekdays)

Output Structure


Community Management Playbook: [Brand Name]

Version: 1.0 Platforms covered: [List] Team: [Names or roles] Last updated: [Date]


1. Why Community Management Matters

[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:

  1. [Goal 1: e.g. Respond to every comment and DM within our SLA — no question goes unanswered]
  2. [Goal 2: e.g. Turn complaints into loyalty moments — every resolved issue is a trust win]
  3. [Goal 3: e.g. Amplify positive sentiment — surface customer stories and user wins]
  4. [Goal 4: e.g. Protect brand reputation — remove harmful content quickly and consistently]

2. Response Framework

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.

3. Response Time SLAs

ChannelComment typeTarget response timeOwner
[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:

  • [Define weekend / evening coverage — e.g. "On-call CM checks mentions at 9am, 1pm, and 6pm on weekends"]
  • Crisis escalation is always on — see Section 6 for out-of-hours escalation contacts

4. Response Templates

These are starting-point templates — always personalise with the person's name and specific context.

Positive comments

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."


Questions about the product or brand

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]. 🙌"


Complaints

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."


Difficult interactions

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."]


DM templates

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]! 🙌"


5. Moderation Rules

Content that must be deleted immediately:

  • Spam (repeated posts, fake giveaways, phishing links)
  • Explicit or NSFW content
  • Personal attacks on other community members
  • Doxxing (sharing personal information about another person)
  • Content that violates platform terms of service
  • Illegal content or illegal product promotion

Content that should be hidden (not deleted) — review within 4 hours:

  • Unverified complaints that may require investigation before action
  • Offensive language that isn't targeting a specific person
  • Posts that may be legitimate but contain sensitive information

Content that should be left (even if negative) — respond and monitor:

  • Genuine product criticism or negative reviews
  • Complaints that are being actively resolved
  • Controversial opinions that are within the rules of civil debate
  • Negative comparisons to competitors (only respond if misinformation)

Account-level actions:

ActionWhen to use
Comment hideFirst instance of borderline content
Comment deleteClear rule violation
User blockRepeated harassment / spam after warning
Report to platformContent 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.


6. Escalation & Crisis Protocol

Show full SKILL.md (824 more words)Show less
Escalation tiers

Tier 1 — CM handles directly:

  • Routine complaints, questions, thank-yous
  • Single negative comment, isolated incident
  • Standard off-topic or mildly unhappy comment

Tier 2 — Escalate to [Marketing Lead / Brand Manager] within 2 hours:

  • Customer with significant public platform (journalist, influencer, known figure)
  • Complaint gaining traction (10+ likes on a negative comment)
  • Legal or compliance mention ("I'm going to sue", "trading standards", "data breach")
  • Media interest — journalist asking questions publicly

Tier 3 — Escalate to [CMO / Founder / CEO] immediately:

  • Viral negative content (100+ shares / views growing rapidly)
  • Allegation of safety issue, injury, or product harm
  • Coordinated negative campaign or pile-on
  • Any media coverage of a complaint
  • Potential crisis — brand reputation at risk
Crisis response protocol
  1. Stop scheduled posting — pause all queued content immediately
  2. Assess — what is the scope? How fast is it spreading? What's the allegation?
  3. Brief leadership — share screenshot, link, and initial assessment within 30 minutes
  4. Hold public response — do not post publicly until leadership approves messaging
  5. Draft response options — prepare 2–3 response options (acknowledge / deny / defer)
  6. Respond or don't respond? — sometimes silence + private resolution beats a public statement
  7. Monitor — track mentions every 30 minutes during a crisis
  8. Post-crisis review — within 48 hours, document what happened and what to do differently

Out-of-hours escalation contacts:

  • CM Lead: [Name, mobile]
  • Marketing Lead: [Name, mobile]
  • [Senior escalation]: [Name, mobile]

7. Tone of Voice in Practice

SituationToneExample phraseAvoid
Complimenting contentWarm, genuine, specific"This genuinely made our day 🙌"Generic "Thank you!"
Answering a product questionHelpful, clear, not jargony"Great question — here's exactly how it works…""Per our FAQs…"
Resolving a complaintEmpathetic, responsible, action-oriented"Really sorry to hear this — let's sort it out.""This is not our fault"
Engaging with light contentPlayful, natural, on-brand[Match the energy of the post — don't be stiff]Corporate speak
Handling criticismMeasured, honest, not defensive"We hear you and we're working on it.""As per our T&Cs…"
Addressing a crisisCalm, 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."]


8. Community Health Metrics

Track these weekly:

MetricWhat it measuresTargetCurrent
Average response timeSpeed of community management[≤ X hours][X hours]
Response rate% of comments/DMs replied to[≥ X%][X%]
Comment sentiment ratioPositive : Neutral : Negative split[≥ X% positive][X%]
Escalation rate% of interactions escalated[≤ X%][X%]
DM resolution timeTime to resolve a DM complaint[≤ X hours][X hours]
Content reports / removalsVolume of content moderated[Track trend][X/week]

Weekly CM review (15 min):

  • Review last week's metrics vs target
  • Flag any recurring complaint themes (product signals for the team)
  • Identify any standout positive interactions worth amplifying
  • Note any escalations and how they were handled

9. Platform-Specific Notes

PlatformKey nuanceBest practice
InstagramComments move fast on Reels; DMs high volumePrioritise Reel comments; use saved replies for FAQ DMs
LinkedInProfessional audience; public replies visible to networksKeep responses professional; avoid humour on complaints
X / TwitterReal-time; pile-ons escalate fastMonitor with keyword alerts; act on Tier 2 triggers quickly
TikTokComment culture is more casual; meme responses okMatch platform tone but keep brand voice; don't try too hard
YouTubeOlder comments resurface regularlyMonitor new comments on older videos; set up notifications
FacebookGroups + page comments; older audienceMore formal tone; monitor group dynamics separately
DiscordReal-time community; requires moderatorsDesignate community moderators; publish community rules prominently

Quality Checks

  • Response templates cover all common scenarios (positive, neutral, complaint, crisis)
  • SLAs are realistic for available team resource
  • Moderation rules clearly distinguish between delete, hide, and leave
  • Escalation tiers are specific — each tier has a named contact and timeframe
  • Tone of voice guidance is concrete enough to write from (examples included)
  • Community health metrics have targets, not just labels
  • Platform-specific nuances are covered for every active channel

Anti-Patterns

  • Do not delete genuine customer complaints to silence negative feedback — deletion damages trust more than the original complaint and can escalate a minor issue to a viral one
  • Do not respond to competitor comparison comments publicly — engaging publicly with competitive comparisons amplifies them; redirect to DMs or ignore
  • Do not use the same template response for every complaint — copy-paste responses on visible complaints are noticed by other users and undermine brand authenticity
  • Do not leave a crisis without pausing scheduled content — queued posts published during an active brand crisis appear tone-deaf and make the situation worse
  • Do not set response time SLAs that cannot be met with the available team size — an SLA that is consistently missed is worse than no SLA

Example Trigger Phrases

  • "Build a community management playbook for [brand]"
  • "Create social media response guidelines for our team"
  • "What should our moderation policy be for [platform]?"
  • "Write community management templates and escalation procedures"
  • "How should we handle negative comments on social media?"

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/community-management-playbook of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Community Management Playbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Community Management Playbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Community Management Playbook this skillmohitagw15856/pm-claude-skills1.4k—~4kAutomated safety check: PassMIT
Instagram Marketingsergebulaev/instagram-skills347—~1.9kAutomated safety check: NotesMIT
Getxapi ConnectLeoYeAI/openclaw-marketing-skills1k1 repos~715Automated safety check: PassCustom licence
Competitor Social ResearchScrapeCreators/social-media-research-skills3.4k—~1.1kAutomated safety check: NotesMIT
Business Contact and Social Links Finderbrowser-act/skills6.1k1 repos~1.6kAutomated safety check: PassMIT
LinkedIn Ads Managementivangfalco/ads-skills279—~1.7kAutomated safety check: PassCustom licence

Similar skills

  • Instagram Marketing

    sergebulaev/instagram-skills

    Plan, draft, audit, and publish content for Instagram. An agent skill from sergebulaev/instagram-skills.

    347 GitHub stars~1.9k tokensUpdated 4 days ago
    Marketing & SEOAuto-check: notes
  • Getxapi Connect

    LeoYeAI/openclaw-marketing-skills

    Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.

    1k GitHub starsUsed in 1 repo~715 tokens
    Marketing & SEOAuto-check passed
  • Competitor Social Research

    ScrapeCreators/social-media-research-skills

    A skill your agent uses when the user wants to research competitors' social media strategy, compare brands or creators, find what content is working in a niche, identify content gaps, or produce a…

    3.4k GitHub stars~1.1k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check: notes
  • Finds a company's official website and social profiles from its name, or collects social links from a website URL, using BrowserAct templates run by a Python script.

    6.1k GitHub starsUsed in 1 repo~1.6k tokens
    Marketing & SEOAuto-check passed
  • LinkedIn Ads Management

    ivangfalco/ads-skills

    Routes LinkedIn Ads work for B2B SaaS to the right playbook: campaign planning, performance analysis, account audits, creative, scaling and account-based campaigns.

    279 GitHub stars~1.7k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed
  • Buying Signal Monitor

    unifapi-agent/agents

    When a seller or SDR wants to catch public buying intent on X/Twitter and LinkedIn — someone asking for a tool they sell, complaining about or switching off a competitor, or hiring for a role that…

    589 GitHub stars~2.4k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Community Management Playbook

What does Community Management Playbook do?

Build a community management playbook for a brand's social media channels. Community Management Playbook is an agent skill from mohitagw15856/pm-claude-skills. Build a community management playbook for a brand's social media channels.

When should I use Community Management Playbook?

Community Management Playbook fits situations like: asked to create guidelines for managing comments; community interactions; define a moderation policy; build response frameworks for social media community managers.

How do I install Community Management Playbook in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill community-management-playbook -a claude-code`. Or copy the skill folder (skills/community-management-playbook in mohitagw15856/pm-claude-skills) into .claude/skills/community-management-playbook in your project. Claude Code loads it when a task matches its description.

How do I install Community Management Playbook in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill community-management-playbook -a codex`. Or copy the skill folder (skills/community-management-playbook in mohitagw15856/pm-claude-skills) into .agents/skills/community-management-playbook in your project. Codex loads it when a task matches its description.

Can I use Community Management Playbook in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill community-management-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/community-management-playbook, .gemini/skills/community-management-playbook, .github/skills/community-management-playbook and .opencode/skills/community-management-playbook in your project.

What does Community Management Playbook need to run?

SKILL.md names no scripts, command-line tools or credentials: Community Management Playbook is instructions for the agent only.

Does Community Management Playbook access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Community Management Playbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Community Management Playbook use?

Community Management Playbook is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Community Management Playbook use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Community Management Playbook?

Skills that share tags, products or a category with Community Management Playbook: Instagram Marketing (sergebulaev/instagram-skills, 347 stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars), Competitor Social Research (ScrapeCreators/social-media-research-skills, 3.4k stars) and Business Contact and Social Links Finder (browser-act/skills, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Community Management Playbook?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.