SkillAtlasSkill 详情

community-management-playbook

In the official Anthropic plugin directory

审核状态:已审核Quality 72Security 60

复制安装命令

用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。

复制前请先查看来源、License 和安全提示。

项目 README

来源文件:README.md

抓取于 2026年8月17日

🧠 PM Skills — 1099 Professional Agent Skills for Claude, ChatGPT, Gemini, Cursor, Codex & Hermes

PM Skills — 1099 professional skills your AI assistant can read. Plain markdown, works with Claude, ChatGPT, Gemini, Cursor, and Codex. MIT licensed.

In the official Anthropic plugin directory Stars npm PyPI Skills SkillCheck SkillSpec Security Audit Version License Sponsor Listed in Awesome Claude Skills Skill of the day Free runs served Website & newsletter

What is PM Skills?

PM Skills is an open-source library of 1099 Agent Skills — plain-markdown SKILL.md files that teach an AI assistant to do one professional task to a senior professional's standard, from writing a PRD to decoding a lease or running a blameless postmortem. Each skill bundles the framework, an output template, quality checks, and anti-patterns. It is MIT-licensed and works with Claude, ChatGPT, Gemini, Cursor, and Codex.

Decode a lease before you sign it. Write a PRD your team can execute. Simulate the promotion committee before the real one meets. Check the weather with zero API keys. Generic AI gives you filler; these give you the structure a senior professional actually uses.

Works natively in Claude Code and Hermes Agent, with ready-to-paste exports for ChatGPT, Gemini, Cursor, Codex and 8 more tools. (PM stands for Professional, not just Product Management.)

Claude Code — native ChatGPT exports Gemini exports Cursor, Codex, Windsurf — one command MCP — any client
Telegram bot Slack app Raycast launcher Obsidian plugin n8n connector
Python — pip install pm-skills Hugging Face dataset Docker image on ghcr GitHub Actions

🐣 New here? Pick a door — each takes about 30 seconds

  1. Just looking → open the ▶ Playground and run a skill in your browser. Nothing to install, nothing to sign up for.
  2. You use Claude Code → type /plugin, search pm-skills, install. Done — ask "decode this lease" and watch.
  3. You use anything else → npx pm-claude-skills add and pick your tool from the menu (Cursor, Codex, Windsurf, ChatGPT, Gemini…).
  4. Want the guided tour → browse the searchable catalogue site and subscribe to get an email whenever new skills launch.

Nothing here can scare your setup. A skill is a markdown file your AI reads — no runtime, no telemetry, no accounts. Installing copies text files; uninstalling is deleting them. Skeptical? Good instinct: read one first — it's designed to be read by humans too.

Don't know what to look for? Describe your task in plain words at 🔎 find — "my landlord kept my deposit", "board meeting on Thursday" — and it names the skill.

Subscribe to the PM Skills newsletter

Never miss a new skill. New ones drop regularly — subscribe to the newsletter and get a short email with a real example whenever they launch. No spam, unsubscribe anytime. Prefer no email? Follow via RSS or browse the newsletter archive.


🧠 Not just what to do — how to think

Most skills here answer "do this task." A new family answers "think differently about my life."

LLMs have one big weakness: they're too correct. On open-ended questions they give the safe, average, textbook answer — technically right and completely forgettable. Two new bundles fight that head-on (inspired by parallel-divergent-ideation research):

💭 pm-thinking — think better

Escape the generic answer and stress-test your own decisions:

🎯 pm-focus — get unstuck

ADHD-friendly executive function (useful for everyone):

✨ See it in action

It's not just a folder of files — the whole library is explorable, runnable, and a little bit magic. All of this runs in your browser, free, nothing to install:

The Skill Playground: pick the Executive Update skill, fill in a few notes, hit run, and watch a structured executive briefing stream out — all in the browser
▶ Pick a skill → fill a short form → run it → a senior-grade artifact streams out. No install, your key stays in your browser (or run free with no key).

Galaxy 3D — fly through all 1099 skills as a glowing constellation you orbit and click into
🌌 Galaxy 3D — fly through all 1099 skills as a living constellation. The ones you've run burn brighter.
PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story
🎁 Wrapped — your practice, as a shareable story. 100% local — nothing leaves your browser.

▶ Open the Playground to run any of the 1099 skills with your own key — or just browse them all.

💬 What can I ask it to do?

Anything below is a real ask that activates a real skill — say it in your own words, the description does the routing:

🏠 "decode this lease before I sign" → lease-decoder📋 "write the PRD for our referral feature" → prd-template🚨 "blameless postmortem for Friday's outage" → incident-postmortem
💰 "practice my salary negotiation" → salary-negotiation📉 "why is churn up this quarter?" → churn-analysis⚖️ "rank the backlog with RICE" → rice-prioritisation
🛂 "prep me for the visa interview" → the-visa-interview🔨 "is this contractor quote fair?" → home-contractor-quote-decoder🏡 "should we rent or buy?" → rent-vs-buy
📝 "draft my self-review honestly" → performance-review🚀 "are we ready to launch?" → product-launch-checklist📬 "my inbox is 4,000 deep" → email-triage-system

…all 1099 asks live in the catalog.

⚡ Quick start

You want to…Do this
Browse the skillsSKILLS.md — the full catalog · or the searchable web catalog
Install in Claude Code/plugin → search pm-skills (it's in the official Anthropic directory) — or npx pm-claude-skills add --agent claude
Install in Cursor / Codex / Windsurf / Cline…npx pm-claude-skills add --agent cursor (or codex, windsurf, aider, cline, zed…)
Use one skill in ChatGPT / GeminiCopy it from exports/chatgpt/ or exports/gemini/ and paste as instructions
Skills over MCP, in any sessionclaude mcp add pm-skills -- npx -y pm-claude-skills-mcp

No npm install needed — npx pm-claude-skills … always runs the latest. npx pm-claude-skills list shows everything in your terminal. Full per-tool instructions: docs/installation.md.

📚 The skills

Every skill follows the same discipline: what it produces, the inputs it needs, a real framework (severity scales, decision rules — not vibes), a concrete output template, quality checks, and anti-patterns. All 1099 pass the SkillSpec L3 gate and a security audit in CI.

Decoders bundle crestSimulators bundle crestCalculators bundle crestLive data bundle crestCowork bundle crestTokens bundle crestSeatbelt bundle crestEssentials bundle crest
DecodersSimulatorsCalculatorsLive dataCoworkTokensSeatbeltEssentials

Browse all 1,099 → · try one in your browser →

Every category, with examples

For everyone — life's paperwork and decisions

FamilyWhat it doesExamples (of many)
🔍 Decoders (25+)Read the document before you sign it — plain language, 🔴🟡🟢 severity, the money mathlease · medical bill · job offer · severance · insurance policy · contractor quote · timeshare
🎭 SimulatorsFace the adversary early — the real meeting, then an out-of-character debriefsalary negotiation · promotion committee · thesis defense · visa interview · due-diligence call
🧮 CalculatorsDeterministic Python scripts + honest models — assumptions labeled, no false precisionrent vs buy · FIRE number · debt payoff · raise vs jump · daycare vs stay-home
📡 Live data (17)Real-time answers with zero API keys — weather, rates, flights, scores, all over plain curlweather · currency · crypto · flights · earthquakes · is-it-down
🏠 Life adminThe unglamorous logistics, done in orderrelocation · new parent · caregiving · doctor visits · records requests
💼 Career momentsThe weeks that decide yearslayoff kit · resignation kit · PIP response · first 90 days as manager · interview gauntlet
🏛 Dead mentors (5) 🆕History's sharpest operators, resurrected — the real methods from public-domain classics, applied to modern workMachiavelli on office politics · Sun Tzu on picking your fights · Franklin's decision algebra · Marcus Aurelius on bad days · Bennett's 1908 time audit
🏛 Life systems (20) 🆕Navigating the bureaucracies and emergencies people face alone — civic, disability, immigration, disastervoting-navigator · disability-benefit-appeal · arrival-setup · credential-recognition · go-bag-builder · after-the-disaster
🧠 Human edges (20) 🆕The parts of life nobody built tools for — neurodivergence, invisible illness, grief, identity, the hard conversationsmasking-budget · spoon-planner · diagnosis-limbo-kit · coming-out-rehearsal · grief-admin · rabbit-hole-rescue
⚡ New-gen (10) 🆕How the next generation lives and earns — creator deals, clips, D&D, ranked, resale, the attention warcreator-deal-decoder · clip-factory · ttrpg-session-forge · the-vibe-check · ranked-climb-coach · attention-reset
🔮 2027 (10) 🆕Problems you don't have yet, but will — the agent era's operational skillsagent-severance · deepfake-drill · agent-hiring-panel · context-bankruptcy · clone-brief · api-for-yourself · the-org-simulator
🎲 Tabletop (5) 🆕Game night, upgraded — teach, judge, plan, design, and practice the tradesteach-the-game · rules-lawyer · game-night-planner · board-game-designer · tabletop-negotiator
🧾 Freelance & renters & parentsSmall bundles for specific livespricing your services · late invoices · deposit recovery · IEP meetings · students
🎲 Hobbies (12) 🆕Life outside work — the genuinely fun stuffwine pairing · houseplant care · board-game night · D&D campaign · stargazing · chess openings
💪 Wellbeing (12) 🆕Body and mind, sustainably — not another app streakhome workout · sleep reset · habit builder · posture reset · screen-time detox
🔐 Digital self-defense (12) 🆕When your digital life is under attackidentity-theft recovery · phishing triage · account recovery · data-broker removal · doxxing response
👪 Family & relationships (12) 🆕The people who matternew-baby logistics · wedding vows · co-parenting messages · condolences · in-law boundaries
💭 Thinking modes (24) 🆕Change how your AI reasons — escape the generic answer, stress-test decisionsthe-third-answer · five-minds · decision-panel · red-team-my-plan · devils-advocate · poke-holes-in-this
🎯 Focus & executive function (26) 🆕Get unstuck and run your own brain — ADHD-friendly, for everyonewhere-do-i-start · task-to-first-step · overwhelm-triage · the-one-thing · build-my-memory-file · weekly-unstuck
📖 Learning & mastery (10) 🆕Learn anything faster and make it sticklearn-anything-roadmap · feynman-explainer · spaced-repetition-setup · skill-plateau-breaker · deliberate-practice-plan
💰 Wealth-building (10) 🆕Build wealth on purpose — educational, not financial adviceinvesting-for-beginners · index-fund-starter · ask-for-a-raise · first-100k-plan · financial-independence-roadmap
🤝 Social & relationships (10) 🆕The hard conversations and the human onesmake-friends-as-an-adult · networking-for-introverts · boundary-setting-scripts · give-hard-feedback-kindly · repair-after-a-fight
🩺 Caregiving & aging (10) 🆕Care for aging parents and navigate the system — not medical/legal advicemedical-appointment-advocate · care-team-coordinator · caregiver-burnout-check · long-term-care-options · end-of-life-wishes-conversation
🤖 AI-native life (10) 🆕Use AI itself well — the meta-skills that make every tool betterprompt-library-builder · delegate-to-ai · ai-context-primer · spot-ai-mistakes · get-more-from-ai
🤝 Cowork (100)The office knowledge work an AI coworker actually does — the frameworks — the whole bundleemail triage · spreadsheet audit · meeting cost meter · deck outline first · saying no kindly · delegation brief
⚡ Cowork · Live (12)The same jobs, done — Claude Cowork acts on your real data via connectors + sandbox and returns an artifact — the whole bundleinbox triage (live) · meeting prep (live) · spreadsheet audit (live) · deck from doc · thread → decision · PR description (live)

For professionals — 35 fields

Product Management Engineering Marketing & GTM
Customer Success Data & Analytics Leadership & People
Design & UX Legal Finance
Founders Security Government

…plus HR, sales, operations, research, healthcare, educators, writers, social media, and more — the full profession index, or by bundle in plugins/ (121 bundles). Install any bundle: /plugin install pm-decoders@pm-skills.

Meta

Before installing anyone's skills (including these): skill-vetting — a security read for SKILL.md files. The library's own standard lives in SKILLSPEC.md; every skill's level is enforced in CI.

🔍 What does a skill look like?

A skill is a single markdown file with a name, a description that tells the assistant when to activate it, and a body containing the working framework: required inputs, decision rules or severity scales, a concrete output template, quality checks, and anti-patterns. The assistant reads it and gains the judgment; humans can read, audit, and edit the same file. No runtime, no lock-in.

---
name: lease-decoder
description: "Decode a residential lease into plain English and rank the
  clauses that can hurt you. Use when someone asks 'what am I signing'…"
---
## Framework: Severity Scale
- 🔴 Can cost you real money — auto-renewal into a full new term, break
  penalties beyond re-rental costs, deposit conditions written to fail…

That's the whole trick: it's markdown. Your agent reads it and gains the judgment; you can read it too, audit it, edit it, or write your own. No lock-in, no runtime, no telemetry.

💸 What it costs you, and how to prove it

Cut your token bill

The pm-tokens bundle optimizes every stage of your agent's token journey — no API keys, stdlib Python, nothing leaves your machine. Five habits, typically 30–60% off a session's token flow:

# 1. Map the repo instead of reading it (~3% of the cost of reading everything)
python3 skills/repo-map/scripts/repo_map.py .

# 2. Crush bulk before it enters context (98% smaller on uniform JSON; errors always survive)
python3 skills/context-crusher/scripts/context_crush.py --mode json --file response.json

# 3. Measure what anything costs — at YOUR prices, times YOUR call volume
python3 skills/token-cost/scripts/token_cost.py --file CLAUDE.md --price-in 3 --calls 200

Plus the judgment skills: token-diet (output costs 3–5× input — diet it where safe), context-budget (cache-aware layout: stable first, volatile last), and session-handoff (resume at ~5% of transcript size). See your own breakdown in the 🪙 Token Dashboard — paste what rides in your context, get computed per-piece savings, all in-browser. The full how-to: docs/SAVE-TOKENS.md.

🤝 Make the most of the cowork skills

The pm-cowork bundle is 100 skills for the office work an AI coworker actually does. Install it (/plugin install pm-cowork@pm-skills), then — the whole trick — describe your mess, don't name the skill: say "my inbox is 4,000 deep", "nobody reads my status updates", "this spreadsheet came from someone who left" — the right skill activates on the ask.

Start where it hurts:

Your painSay thisThe skill that answers
Drowning in email"triage my inbox and cut the volume at the source"email-triage-system → inbox-unsubscribe-purge
Calendar is all meetings"audit my recurring meetings and price them"standing-meeting-audit + meeting-cost-meter
Inherited a scary spreadsheet"audit this sheet before we trust it"spreadsheet-audit → formula-detangler
Docs get rewritten in review"outline first, get sign-off, then draft"outline-before-prose
Weeks just happen to you"set up my weekly review"weekly-review-ritual — the hub the others plug into

Three habits that compound: (1) The weekly review is the keystone — it feeds task-triage-matrix, deep-work-blocking, and personal-wip-limits automatically. (2) The skills chain on purpose — email-to-tasks feeds the task triage; the meeting audit feeds async-instead; delegation-brief hands off what the triage says to shed — follow the links inside each skill. (3) Teams adopt one norm at a time — start with agenda-or-cancel or working-agreements, let it stick, then add the next; the ten-norms-on-Monday rollout is how none of them survive.

Prove a skill works, and stop paying MCP rent

Two CLI tools for the trust-and-cost problems the ecosystem keeps hand-waving — both keyless-to-inspect, both one command:

# Does your skill actually work? Prove it. Paired A/B — skill on vs off, same tasks,
# REAL token counts from the API's usage fields, optional blind judge, sha-pinned receipt.
npx pm-claude-skills prove --skill ./my-skill --tasks tasks.txt --runs 2 --judge
npx pm-claude-skills prove --skill ./my-skill --tasks tasks.txt --dry-run   # plan + call count, spends nothing

# Your MCP servers are charging you rent. Measure it: per-server token cost,
# unused-in-N-days flags, "disconnect these three, save X tokens per message".
npx pm-claude-skills mcp-audit --connect

prove exists because the ecosystem is full of "65% better!" claims and almost none are measured — it's the honest-broker harness (the JetBrains "advertised 65%, measured 8.5%" story is exactly why). mcp-audit reads your Claude configs, speaks real MCP to each server to count its schema tokens, and scans your session logs for what you actually use. See also the 📊 AI Spend page — every agent's cost (Claude Code, Codex, Copilot) in one meter, all in-browser.

Agent safety: the pm-seatbelt bundle is the pre-flight checklist before an agent touches email, the browser, or files — least-privilege reviews, prompt-injection spotting, and the blast-radius drill for going autonomous. And RFC 0002 — HANDOFF.md is a dead-simple session-handoff convention (your agent, but it remembers Monday) — a file, not a server, with reference hooks.

Quality, not just quantity

  • Every skill passes the SkillSpec L3 gate — structure, framework, quality checks, anti-patterns — enforced in CI on every commit
  • Eval-scored — 208 scored outputs, avg 4.8/5, judged blind
  • Security-audited — a dedicated CI workflow sweeps every skill and script; calculators are stdlib-only and deterministic with byte-exact output tests
  • Honest by design — decoders end with a not-legal-advice line, calculators name what they don't model, simulators debrief out of character, and skills that shouldn't ghostwrite (student statements) coach instead

🎁 Beyond the skills (the bonus material)

The library grew an ecosystem — all optional, all linked from the full showcase:

📄 The one-page cheatsheet — the whole library on one printable poster · ▶ Skill Playground — try any skill in your browser, no install · 📸 the Gallery — the creative side, in screenshots · Anti-Pattern Museum — 2,900+ shareable rules · The Handbook (also a real printed book) · Workflow recipes · Subagents & slash commands · MCP server + REST API · n8n / Slack / Obsidian integrations · The Boardroom · SkillBench · Org Edition · 🇪🇸 🇫🇷 🇨🇳 🇯🇵 translations

Lint your own skills in CI

The validator that keeps these 1,099 honest, as a GitHub Action:

- uses: mohitagw15856/pm-claude-skills@v76
  with:
    path: .claude/skills   # optional — it finds them otherwise

It checks frontmatter, the Use when … trigger clause a model actually matches on, leftover template text, and structure — and annotates each finding inline on the pull request diff, because a finding on the line beats a finding in a log nobody opens. Also available as npx pm-claude-skills skillcheck.

Zero dependencies, no Docker image, no model call.

Companion tools — for the bits a skill shouldn't guess

A skill can tell a model to check the contrast. Only arithmetic can actually check it. Where a question has a right answer rather than a good one, the skill calls out to a tool instead of estimating — both are MIT, zero-dependency, and neither makes a model call, so they cost nothing to run and return the same answer every time.

notugly — design systems that are provably not ugly. #777777 on white is 4.478 and fails AA; #767676 is 4.542 and passes, and no amount of looking at a screenshot separates those. accessibility-audit, design-system-audit, design-handoff-brief, brand-guidelines and the Figma reviews now fill their contrast rows from npx notugly; the MCP server exposes check_contrast directly; and design-system-generate wraps it for the case where there is no design system and something ships on Thursday.

rulebook — 37 games, 203 rulings, and how commonly each house rule is actually played. board-game-night-planner uses it for teach times and for settling the argument, because a rules disagreement is usually two groups who learned it differently and are both partly right.

🆕 Latest

v76.2.1 — SkillCheck as a GitHub Action, and the design skills now compute their contrast numbers instead of estimating them.

Everything else is in the changelog and the releases — a README should say what this is, not what it was.

❓ First-timer questions, straight answers

Is it actually free? Yes — MIT, all 1099 skills, forever. The skills are markdown; there is nothing to gate. Sponsors fund the playground's free model runs, not access.
Do I need an API key? Not to browse, read, install, or use skills inside a tool you already have (Claude Code, ChatGPT, Cursor…). The playground even serves a few sponsor-funded free runs a day. A key only enters the picture for optional extras like running skills from CI.
I'm not a product manager. Is this for me? PM stands for Professional here. Most of the library is decoders for leases and medical bills, salary-negotiation practice, career-moment kits, life admin, and 35 professions from teaching to veterinary. The product-management corner is just where it started.
Will this mess with my existing setup? No. Skills are inert text files in a folder; your assistant reads them when relevant. Remove the folder and it's like they were never there. The CLI never touches anything outside the skills directory it tells you about.
How do I know these are any good? Every skill passes a structural gate (SkillSpec L3) and a security scan in CI; 208 outputs are eval-scored in the open (avg 4.8/5), and the benchmark report publishes the negative findings too. When something's machine-translated or unscored, it's labelled.

🤝 Contributing

The library grows a skill at a time — plant one of your own. One markdown file, one PR.

Add a skill via PR (the standard, CONTRIBUTING), request one via issue, or publish your own repo to the community index and earn the badge. Translations follow the pattern in skills-i18n/.

❤️ Support

If a skill saved you real money or a real mistake, star the repo — it's how others find it. Sponsors fund the playground's free runs and get naming rights, not influence: become a sponsor.

📄 License

MIT — use them, fork them, ship them at work. Skills are judgment, and judgment wants to be free.


Built by Mohit with Claude. 1099 skills · 121 bundles · 35 professions · every commit gated. The long version of this README — every feature, wave, and frontier bet — lives in the Showcase.

其他

高风险

  • 来源需自行核对维护者身份。
  • 未检测到明显脚本安装指令。
  • 可能需要外部 token、网络权限或第三方服务。
  • 存在潜在风险命令,请谨慎安装。
  • 扫描发现:2 条。

Codex — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/mohitagw15856/pm-claude-skills.git
  3. 将 "skills/community-management-playbook" 文件夹复制到 Codex 的 skills 目录中。
  4. 重启 Codex 让新的 skill 生效。

Codex — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Codex 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Codex 让新的 skill 生效。

Claude Code — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/mohitagw15856/pm-claude-skills.git
  3. 将 "skills/community-management-playbook" 文件夹复制到 Claude Code 的 skills 目录中。
  4. 重启 Claude Code 让新的 skill 生效。

Claude Code — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Claude Code 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Claude Code 让新的 skill 生效。

Cursor — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/mohitagw15856/pm-claude-skills.git
  3. 将 "skills/community-management-playbook" 文件夹复制到 Cursor 的 skills 目录中。
  4. 重启 Cursor 让新的 skill 生效。

Cursor — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Cursor 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Cursor 让新的 skill 生效。

GitHub Copilot — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/mohitagw15856/pm-claude-skills.git
  3. 将 "skills/community-management-playbook" 文件夹复制到 GitHub Copilot 的 skills 目录中。
  4. 重启 GitHub Copilot 让新的 skill 生效。

GitHub Copilot — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 GitHub Copilot 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 GitHub Copilot 让新的 skill 生效。

Windsurf — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/mohitagw15856/pm-claude-skills.git
  3. 将 "skills/community-management-playbook" 文件夹复制到 Windsurf 的 skills 目录中。
  4. 重启 Windsurf 让新的 skill 生效。

Windsurf — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Windsurf 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Windsurf 让新的 skill 生效。
查看 SKILL.md 原文
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

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

发现问题?提交给管理员复核

评分:

评论 (0)

暂无评论,成为第一个评论者吧!