1285 professional Agent Skills + workflow recipes — searchable & fetchable over MCP.
io.github.mohitagw15856/pm-claude-skills MCP Server
This MCP server exposes “1117 professional Agent Skills + workflow recipes” that are “searchable & fetchable over MCP.” It is focused on product-management and productivity skills for AI assistants, spanning tools such as Claude, ChatGPT, Gemini, Cursor, Codex & Hermes.
🛠️ Key Features
Provides professional Agent Skills and workflow recipes
Supports search and fetch via MCP
🚀 Use Cases
Retrieve product-management and productivity skills for AI agents
Use across Claude, ChatGPT, Gemini, Cursor, Codex, and Hermes
⚡ Developer Benefits
Contents are available as plain markdown
MIT licensed
⚠️ Limitations
Server description provided does not specify authentication, endpoints, or tool count
Your landlord kept your deposit. Your mom got a medical bill that makes no sense. You got laid off on a Tuesday. Someone you love died, and no one handed you the checklist.
Generic AI is a very confident intern. PM Skills is the senior colleague's notes — 1176 of them, one markdown file each, for the moments at work and in life where "it depends" is not an answer. (PM stands for Professional, not just Product Management. Yes, we get asked.)
PM Skills is an open-source library of 1176 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.
You get the finished document, not advice about it
The challenge to each deduction, the demand letter, and the point at which small claims is worth it
🚪 Pick a door — 30 seconds each
You…
Do this
▶
just want to see it
open the Playground and run a skill in your browser. No install, no signup, no "enter your email to continue"
🧠
use Claude Code
/plugin → search pm-skills → install. Ask "decode this lease" and watch
🛠
use anything else
npx pm-claude-skills add and pick your tool (Cursor, Codex, Windsurf, ChatGPT, Gemini…)
🔎
don't know what to ask for
type it at find — "my landlord kept my deposit" — and it names the skill
🎒
are in the middle of something
start from your moment, not the catalogue → Skill Packs · 🍼 new parent · 💼 laid off · 🌍 new country · 👵 caring for a parent · 🕊️ losing someone · 💸 money in crisis
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 written for humans too.
The MCP install command fixed, a check that every release installs and runs, announcements in doctor and the playground, and frozen versions of the flagship skills that a team can pin
A five-stage UI pipeline (direction, system, motion, critique, verification) that stops generic AI-looking interfaces, with pointers to five specialist design skills
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcp
Route a prompt to a skill
npm run route -- "board meeting on Thursday"
No npm install needed — npx pm-claude-skills … always runs the latest. 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 1176 pass the SkillSpec L3 gate and a security audit in CI.
…plus HR, sales, operations, research, healthcare, educators, writers, social media, and more — the full profession index, or by bundle in plugins/ (134 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.
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.
markdown
---
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 audit it, edit it, or write your own.
✅ Quality, not just quantity
Structure
every skill passes the SkillSpec L3 gate — framework, quality checks, anti-patterns — on every commit
decoders end with a not-advice line, calculators name what they don't model, simulators debrief out of character, and skills that shouldn't ghostwrite (your kid's college essay) coach instead
pm-tokens — 30–60% off a session's token flow, stdlib Python, nothing leaves your machine (how-to, 🪙 dashboard) · npx pm-claude-skills mcp-audit — what your MCP servers charge you in rent
Prove
npx pm-claude-skills prove --skill ./my-skill --tasks tasks.txt — paired A/B with real token counts and a sha-pinned receipt, because "65% better!" is not a measurement · SkillBench · route-bench
-uses:mohitagw15856/pm-claude-skills@v79with:path:.claude/skills# optional — it finds them otherwise
Checks frontmatter, the Use when … trigger clause a model actually matches on, leftover template text, and structure — and annotates each finding inline on the PR diff. Also npx pm-claude-skills skillcheck. Zero dependencies, no model call.
Companion tools for the bits a skill shouldn't guess — both MIT, zero-dependency, no model call: notugly (contrast and design-system checks the design skills call instead of estimating) and rulebook (37 games, 203 rulings, for the board-game skills).
🚫 What PM Skills is not
Not an agent framework.
Skills are instructions your existing assistant reads. There is no runtime to host.
Not a prompt pack.
Every skill has required inputs, an output format, quality checks and anti-patterns, and is gated in CI.
Not only for product managers.
PM stands for Professional. Most of the library is life admin and 35 professions.
Not a substitute for a professional.
The legal, medical and financial skills prepare you for that conversation. They do not replace it.
Not tied to one vendor.
The same skill exports to 12 platforms and is served over MCP.
Not a hosted service.
The playground and the MCP endpoint are optional. Everything works from files on your machine.
❓ Straight answers
Is it actually free?
Yes — MIT, all 1176 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. The playground serves a few sponsor-funded free runs a day. A key only matters for optional extras: running skills from CI, or the typed decision layer (which falls back to keyword routing without one).
The catalog says 1176 but the folder has more. Which is it?
Both. There are 1188 directories under skills/; 12 of them are deprecated (marked in their frontmatter, each pointing at the skill that replaced it). They stay on disk so an old install command or a bookmarked name never breaks, and they are hidden from the catalog, the playground and the headline count. 1176 is what a person can browse; 1178 is what an installer can resolve.
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.
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 is machine-translated or unscored, it's labelled.
🗺️ Roadmap
✅ Exports to 12 platforms and one install command
✅ MCP server, subagents and slash commands
✅ Quality gates in CI: structure, security, duplicates, drift
✅ The decision layer and the promote loop
✅ The design taste pipeline
⚪ Published eval scores for more skills
⚪ A promotion round for the Production-Ready tier
⚪ Merging the near-duplicate skills still marked as pending
⚪ Translated skill descriptions, done at scale or retired
Direction, not a contract. Details and good first issues: ROADMAP.md.
🔒 Privacy and telemetry
Off by default. A skill is a text file and sends nothing.
What
Default
Detail
Skills, CLI, exports
Nothing is sent
Plain files on your machine
Usage counter
Off
Opt in with PM_SKILLS_TELEMETRY=1. It sends the skill name and nothing else
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. Organisations: a clearly-disclosed logo and link only, never product integration — email me.
📄 License
MIT — use them, fork them, ship them at work. Skills are judgment, and judgment wants to be free.
Built by Mohit with Claude. 1176 skills · 134 bundles · 35 professions · every commit gated. The long version — every feature, wave, and frontier bet — lives in the Showcase.
