pm-claude-skills

The whole library on one page — install, all 288 skills by profession, the Professional Brain, the REST API, integrations, and quality tooling. Great to print, share, or drop into a slide.

Markdown · PNG · PDF — regenerate the image/PDF with node web/docs-assets/shoot.mjs (PAGES=cheatsheet).

Want the full walkthrough? The Practical Guide is a 15-page, example-driven manual — install → your first skill → worked examples (PRD, exec update, RICE, postmortem) → chaining recipes → the Brain → running anywhere → tips. Download the PDF →

These 288 skills aren't a random catalog — they cover the full arc of professional work, end to end. Wherever you are in the loop, there's a skill for it:

flowchart LR
    A(["🔍 Discover"]) --> B(["🎯 Decide"]) --> C(["🔨 Build"]) --> D(["🚀 Ship"]) --> E(["📊 Measure"]) --> F(["📣 Communicate"])
    F -. "feeds the next discovery" .-> A
    classDef s fill:#1d288b,stroke:#d97757,color:#e7ebf0;
    class A,B,C,D,E,F s;

New here? Start with the top-tier skills, or jump straight to all 288 skills grouped by profession.

Individual skills are great. Chaining them is the superpower. A recipe runs several skills in sequence and passes each output forward as context — so a fuzzy idea comes out the other end as a finished, joined-up set of artifacts. No other skills library chains across professions like this.

/ship-a-feature  "a referral program for B2B users"

  ambiguity-resolver → prd-template → rice-prioritisation → roadmap-narrative → go-to-market
   frame the problem    spec it        prioritise it        place on roadmap     launch plan
        └──────────────── each stage's output feeds the next ────────────────┘

→ Full detail and how to add your own in WORKFLOWS.md. Recipes run as slash commands in Claude Code, or over MCP via the get_workflow tool.

Got a coding question? Just Ask — an error, a regex, a git mess, a dependency conflict, "what does this code do?" — and the right developer skill answers instantly (like StackOverflow, but the answer's already written), with a one-click path to the community Q&A for a human follow-up.

Or build your own visually. The Workflow Canvas lets you drag any skills into a custom chain and run it in the browser — each step's output feeds the next. Like n8n, but for professional thinking. Don't know which skills to use? The Auto-Agent takes a plain-English goal, plans which skills to chain, and runs them for you — each step feeding the next:

Generic output is the #1 complaint with AI. Skill Memory fixes it: tell the skills who you are once, and every skill and recipe produces output already tuned to your product, audience, and voice — no re-typing.

• In Claude Code: run /setup-context (or copy templates/pm-context.example.md → pm-context.md). Skills read it as standing context.
• In the Playground: fill the Your context box — it's saved in your browser and prepended to every run.

Without context:  "write an exec update" → generic, you rewrite it
With context:      "write an exec update" → your voice, your metrics,
                    your audience — shippable on the first try

This repo ships a Skill Bot: comment on any issue or PR and a skill runs and replies inline.

/skill executive-update
Audience: CEO. Period: Q2. Shipped onboarding redesign; activation up; hiring behind plan.

The bot runs the skill and posts the result as a reply. /skill list shows usage. It's gated to repo collaborators (so random commenters can't trigger paid API calls) and needs an ANTHROPIC_API_KEY secret. Copy the workflow into your own repo to give your whole team skill-powered ChatOps.

Grounded in canonical frameworks. These aren't invented prompts — each skill encodes a proven method and cites it: RICE (Intercom), Jobs-to-be-Done (Christensen), Continuous Discovery (Teresa Torres), Porter's Five Forces, the Pyramid Principle (Minto), Google SRE, WCAG, Obviously Awesome (April Dunford), and more. The source shows as a " Based on" line on every skill page and in the Playground.

And measured, not just claimed. An eval harness runs each skill against a held-out test case, then an LLM judge (Opus 4.8) rates the output on four dimensions — structure, completeness, usefulness, grounding — averaged across two models. 15 skills are eval-scored today (and climbing); the rest are reviewed against the authoring standard. A regression gate then blocks any PR that drops a skill's score, so quality can't quietly rot as models change.

The qualitative half — real time saved. Scores measure quality; case studies measure outcomes. See the kind of before → after a skill delivers (PRD: ~2 days → ~25 min), and add your own 2-minute ROI story — we'll feature it.

The loop actually catches bad skills. A recent run flagged three skills scoring ~2/5 because they asked for missing inputs instead of delivering. We added a "work from a brief" rule, re-ran, and they jumped to 4.75/5:

That's not luck — it's a self-improving pipeline (/improve) that critiques and rewrites a skill, keeping the change only if the score goes up. See the leaderboard for live scores; run it yourself with node evals/run-evals.mjs.

See the difference for yourself. The Playground's Compare toggle runs the same inputs with and without the skill, side by side — structured, shippable output on the left; generic mush on the right:

Already have a draft? Flip on Critique mode in the Playground — or use the standalone Grade your work tool — to paste an existing PRD/roadmap/update and get a rubric score, ranked gaps, and a redline graded against the skill's framework. Before you ship, run /red-team to stress-test the plan against a room of hostile expert personas.

This whole thing is an open, reproducible benchmark for AI professional work — and it's eval-gated: every contributed skill is auto-checked for structure and scored on the rubric. The easiest way to add one is Skill Studio — describe a skill in your browser, generate a compliant SKILL.md, and open a pull request in one click (or use the form →).

Most skill repos are a folder of prompts. This one is a system — measured, composable, and usable in the browser:

Not sure where to start? Pick by what you want:

• Just try it (0 install): open the live Playground and run any skill.
• Use it in Claude Code: npx pm-claude-skills add --agent claude (or the /plugin route below).
• Have it in every session: add the MCP server (one line, below).

You don't need npm install pm-claude-skills — it's a CLI, not a library, so there's nothing to import. Use npx pm-claude-skills … (it always runs the latest). npm install just downloads it and does nothing on its own.

With the skills CLI (the open agent-skills installer that works across Claude Code, Cursor, Codex, OpenCode & 60+ agents) — pick from all 288 interactively:

npx skills add mohitagw15856/pm-claude-skills            # browse & pick (auto-detects your agent)
npx skills add mohitagw15856/pm-claude-skills --list     # just preview the catalog
npx skills add mohitagw15856/pm-claude-skills --skill prd-template   # grab one
npx skills add mohitagw15856/pm-claude-skills --skill '*'            # install all 288

Or our own installer — via the pm-claude-skills npm package (Windows/macOS/Linux, needs Node), which also installs subagents, slash commands & cross-tool exports:

npx pm-claude-skills add --agent claude     # or: codex · cursor · hermes · openclaw

Or one-line MCP — make all 288 skills + 5 workflow recipes available in every session of any MCP client (Claude Code, Claude Desktop, Cursor, Windsurf), no per-file install:

claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Your assistant can then "search the skills for churn" or "run the ship-a-feature workflow" on demand. Details: mcp/README.md.

In Claude Cowork — open the plugin browser → Add from GitHub → enter mohitagw15856/pm-claude-skills, then add the bundles you want. No CLI needed.

In Claude Code — it's in the official Anthropic plugin directory, so you can browse to it in the /plugin marketplace, or add it directly:

/plugin marketplace add mohitagw15856/pm-claude-skills

Or install by profession:

claude plugin install pm-essentials@pm-claude-skills # Core PM + Word tracked changes

claude plugin install pm-delivery@pm-claude-skills # Delivery + PowerPoint auditor

claude plugin install pm-engineering@pm-claude-skills # Engineering (35 skills)

claude plugin install pm-cs@pm-claude-skills # Customer Success

claude plugin install pm-data@pm-claude-skills # Data + chart data extractor

claude plugin install pm-legal@pm-claude-skills # Legal

claude plugin install pm-finance@pm-claude-skills # Finance

claude plugin install pm-hr@pm-claude-skills # HR

claude plugin install pm-sales@pm-claude-skills # Sales

claude plugin install pm-operations@pm-claude-skills # Operations

claude plugin install pm-research@pm-claude-skills # Research & Healthcare

claude plugin install pm-cross@pm-claude-skills # Cross-profession

claude plugin install pm-figma@pm-claude-skills # Figma

claude plugin install pm-social@pm-claude-skills # Social Media

claude plugin install pm-writers@pm-claude-skills # Writers & Content Creators

Or clone and symlink for auto-updates:

git clone https://github.com/mohitagw15856/pm-claude-skills.git ~/pm-claude-skills mkdir -p ~/.claude/skills ln -s ~/pm-claude-skills/skills/* ~/.claude/skills/

The same 288 skills reach you through every channel — pick whatever fits your stack:

196 of 288 skills are eval-scored, averaging 4.8/5 — see the leaderboard.

Give your skills memory: the Professional Brain is a local markdown folder skills read, write back to, and act on. It's a folder + one file to start — 5-minute Quickstart.

These skills were built for Claude Code, but they aren't locked to it. Each SKILL.md is two portable parts: a small frontmatter block (name + description) and a markdown body that is just a well-structured set of instructions and output templates. The body is plain English — so it works anywhere a capable model reads instructions.

There are two kinds of support. Native SKILL.md agents read the file as-is and auto-discover skills from the description frontmatter. Other tools take the markdown body as a system prompt — for those we ship ready-made exports.

In your editor (VS Code / Cursor): the vscode-extension/ brings all 288 skills into the Command Palette — search and insert a skill as context for Copilot/Cursor chat, copy it, or open it in the Playground.

What's verified vs. what varies: the skill bodies — the frameworks, rubrics, and output templates that do the actual work — are model-agnostic and have been used across Claude and other chat LLMs. Native SKILL.md agents (Claude Code, Hermes) also get the convenience layer: automatic skill discovery from the description. On chat LLMs you paste the body in manually and lose only the auto-triggering, not the substance.

Ready-to-use exports

You don't have to strip frontmatter by hand. Every skill is exported to platform-ready files under exports/, generated from the same source so nothing is maintained twice:

• ChatGPT — copy any exports/chatgpt/<bundle>/<skill>/SYSTEM_PROMPT.md straight into a Custom GPT's instructions.
• Google Gemini — copy any exports/gemini/<bundle>/<skill>/GEM_INSTRUCTIONS.md into a Gem's instructions.
• Cursor (.mdc) · Windsurf (.md) · Aider (.md) — generated rule/conventions files in exports/cursor/, exports/windsurf/, exports/aider/ (or use the installers below).

One-command install for coding agents

Cross-platform (Windows, macOS, Linux) — recommended. One Node command installs every skill where your agent discovers them. No git, no bash:

npx pm-claude-skills add --agent claude     # skills + subagents + commands → ~/.claude/
npx pm-claude-skills add --agent codex      # OpenAI Codex (or: hermes · openclaw)
npx pm-claude-skills add --agent cursor     # .mdc rules → ./.cursor/rules
npx pm-claude-skills add --agent windsurf   # .md rules → ./.windsurf/rules
npx pm-claude-skills add --agent aider      # conventions → load with: aider --read
npx pm-claude-skills list                   # all supported agents + default paths

Add --link (symlink), --target <path>, or --dry-run to any add.

Shell one-liners (macOS / Linux / Git Bash / WSL — not PowerShell):

bash <(curl -fsSL https://raw.githubusercontent.com/mohitagw15856/pm-claude-skills/main/scripts/codex-install.sh)
bash <(curl -fsSL https://raw.githubusercontent.com/mohitagw15856/pm-claude-skills/main/scripts/openclaw-install.sh)
bash <(curl -fsSL https://raw.githubusercontent.com/mohitagw15856/pm-claude-skills/main/scripts/cursor-install.sh)

Windows / PowerShell: use the npx command above (the bash <(curl …) form is a Unix idiom and won't run in PowerShell).

Already cloned? ./scripts/install.sh --agent <name> (or python3 scripts/sync-hermes-skills.py for Hermes) does the same from your checkout.

The skill body in skills/<name>/SKILL.md is the single source of truth. Regenerate the chat-LLM / Cursor exports (or add a new platform — it's a few lines in the PLATFORMS registry) with:

node scripts/build-exports.mjs            # regenerate all platform exports
node scripts/build-exports.mjs --check    # CI: fail if exports are stale

Prefer a hand-curated ChatGPT collection? There's also a companion Custom GPT library built from the same frameworks.

It's not just skills. The library also ships Claude Code subagents and slash commands built on top of the strongest skills, so common workflows are one delegation or one command away.

Subagents (agents/) — focused personas Claude delegates to automatically by description:

Slash commands (commands/) — run a skill on whatever you pass:

/prd · /rice · /sprint-plan · /health-scorecard · /retro · /exec-summary

Personas (output-styles/) — Claude Code output styles that change the assistant's whole voice and default skill loadout. Switch with /output-style:

Startup CTO · Growth Marketer · Solo Founder · Product Leader

Install everything for Claude Code in one go (skills + subagents + commands + personas):

npx pm-claude-skills add --agent claude   # ~/.claude/{skills,agents,commands,output-styles}

Commands whose skill ships a Python helper (RICE, sprint capacity, customer health) run it to compute results, not estimate them. To string these together, see the orchestration patterns (skill chains & multi-agent handoffs).

For MCP clients (Claude Desktop, Cline, …), there's a zero-dependency MCP server so your assistant searches and pulls skills on demand instead of installing 172 files. It exposes three tools — list_skills, search_skills, get_skill — over stdio (no network, nothing leaves your machine).

{
  "mcpServers": {
    "pm-claude-skills": { "command": "npx", "args": ["-y", "pm-claude-skills-mcp"] }
  }
}

Then ask: "search the skills for customer churn, then apply the best one to my account." Full setup in mcp/README.md.

Skills that act on your data. Run pm-skills alongside a data server (filesystem, GitHub, Postgres, Drive…) and a skill works on your real sources: "draft the PRD from GitHub issue #123," "run churn-analysis on exports/q2.csv," "open an issue per product-launch-checklist item." Copy-paste configs + worked recipes in connectors/.

pm-skills needs no auth. To connect GitHub, Slack, Notion, etc., you add that provider's MCP server with its own token/OAuth once in your client — then every skill can use it. (filesystem = a folder you grant; GitHub = a PAT; Slack/Notion = OAuth.)

Three ways to put the library to work beyond installing files:

Run a skill in your CI — GitHub Action. Auto-write PR descriptions, changelogs, release notes, or run a code-review checklist on every PR:

- uses: mohitagw15856/pm-claude-skills/action@main
  with:
    skill: pr-description-writer
    input: ${{ steps.diff.outputs.text }}
    api_key: ${{ secrets.ANTHROPIC_API_KEY }}

Turn your docs into a skill — generate. Point it at a URL or file and it writes a SKILL.md that follows the authoring standard:

ANTHROPIC_API_KEY=sk-ant-… npx pm-claude-skills generate --from ./team-process.md

Skill Leaderboard — evals. An LLM-as-judge harness scores each skill across Claude models on structure, completeness, usefulness, and grounding. View the leaderboard →

Score the whole library, cheaply. npm run eval:gen-cases writes a representative input for all 288 skills (curated cases kept verbatim; the rest auto-generated), then npm run eval:all runs the full pass on Haiku for ~$2 total. The weakest scorers can then be auto-rewritten with npm run improve -- <skill> (/improve), which keeps a change only if the score goes up.

Live: mohitagw15856.github.io/pm-claude-skills · Browse the full skill catalog

Don't want to install anything yet? Run any of these skills from a zero-backend web app using your own Claude, OpenAI, or Gemini key. Pick a provider, pick a skill, fill in the auto-generated form, and the result streams back live. Your key is stored only in your browser (localStorage) and sent directly to the provider you chose — nothing touches a server we own.

Run it locally:

git clone https://github.com/mohitagw15856/pm-claude-skills.git
cd pm-claude-skills
node web/build-skills.mjs               # generate the skill index (skills.json)
cd web && python3 -m http.server 8000   # serve over HTTP (not file://)
# open http://localhost:8000 and paste a key from console.anthropic.com

It's fully static — deploy the web/ folder to GitHub Pages, Netlify, or Vercel with no environment variables. Full details in web/README.md.

Not sure which plugin to install? Here's what each one covers:

Debugging Log Analyser — paste a stack trace or error log, get a structured root cause diagnosis with probable cause, affected code path, a specific fix, and next debugging steps.

PR Description Writer — share your diff or commit list, get a reviewer-friendly PR description with summary, changes made, testing steps, and reviewer notes.

Sprint Planning Skill — paste your sprint goals and backlog items, get a complete structured sprint plan with capacity, commitments, risks, and a day-one kickoff agenda.

Drop a demo in Discussions and we'll feature it here.

On May 5, 2026, Anthropic released their first agent templates — pre-packaged Claude agents that combine skills, connectors, and subagents into ready-to-run workflows for financial services.

This library is the largest open-source collection of professional skills available — covering 20 professions beyond financial services. The 288 skills here are the building blocks for agent templates outside of finance.

What is an agent template?

An agent template packages three things into one runnable workflow:

A skill alone gives Claude a structured output format. An agent template gives Claude a complete workflow — pulling data, running specialised analysis, producing the output, and routing it where it needs to go.

How to use this library to build your own agent template

Pick a recurring workflow on your team. Identify which existing skills cover the structured outputs that workflow needs. Add the connectors that let Claude reach the data. Add subagents for the analytical sub-tasks. That's the template.

Examples of agent templates this library supports:

Available agent templates

The pm-claude-skills library now includes four working agent templates, each built from existing skills in this library combined with subagents and connectors. All four follow the architecture Anthropic introduced for financial services agent templates on May 5, 2026.

Each template includes:

• Working orchestration script
• Two or more focused subagents
• Connector configurations with documented setup
• Working examples (input + output)
• Smoke test for verifying installations

How to install a template

All templates are part of the main library — installing the marketplace gives you all four.

/plugin marketplace add mohitagw15856/pm-claude-skills

Then navigate to the template you want and follow its README:

cd templates/pm-sprint-agent # or pm-discovery-agent, etc. cat README.md # full setup instructions

Building your own template

If you want to build a template for a workflow not covered above — Legal Contract Review, Sales Pursuit, Finance Board Pack, HR Onboarding, Marketing Campaign — see the template contribution guide.

The pattern is consistent: pick a multi-step workflow, identify which existing skills cover the structured outputs, add connectors for data access, and define subagents for specialised analysis. The four templates above are reference implementations.

It combines four skills, two connectors, and two subagents into a single workflow that handles end-to-end sprint planning.

Documentation, working orchestration script, and example outputs are included in the template folder.

More templates will follow. If you want to contribute one, see the template contribution guide.

Latest: v29.1.0 — AI/ML + Growth skill packs, composable recipes, a deeper Brain. 288 skills across 41 bundles, 23 professions. Every tagged release has complete notes on the Releases page.

Full Keep a Changelog-format history — every release back to the start — is in CHANGELOG.md.

This repo was built alongside a published 16-part article series on Medium.

A 288-skill library doesn't have 288 equally-mature skills, and pretending otherwise wastes your time. Skills are tiered honestly so you can start with the best work:

• Production-Ready (50) — battle-tested, stable output, used in real work. Includes the three skills with computed Python helpers (sprint planning, RICE, customer health). Start here.
• Stable — solid, reliable, well-structured; the default for most of the library.
• Experimental — newer or dependent on an external tool/API/scrape (Gemini, Gmail, browser automation, social scraping). Useful, but more setup and more moving parts.

Full breakdown: TIERS.md — every Production-Ready and Experimental skill listed by name.

If you're new, install pm-essentials and try a couple of Production-Ready skills before going wide.

Every skill, grouped by profession. Browse the full per-skill catalog → SKILLS.md · searchable live catalog · run any skill in the browser

Full per-skill detail (folder paths, descriptions, "" markers) lives in SKILLS.md.

Building and maintaining 288 skills across 41 bundles takes real time — testing skills against new model releases, building new ones from community requests, writing the article series, and keeping documentation current.

If these skills save you time at work — or you're a company that wants your logo in front of the PMs, engineers, and operators who use them daily — become a sponsor → (or buy me a coffee).