Mohit
54f76456ab
Signature features that turn breadth (174 skills) into a differentiated product: - Workflow recipes: 5 cross-profession chains (workflows.json) that pass each output forward — slash commands (/ship-a-feature etc.), WORKFLOWS.md generated by scripts/build-workflows.mjs, README + MCP (list_workflows/get_workflow) wired - Eval-backed quality: real per-skill scores from evals/results.json surfaced as badges in the playground and an honest README section (6 scored skills) - One-click MCP: 'claude mcp add' install + workflow tools, works in any MCP client - Playground: 'which skill?' recommender, with/without compare toggle, shareable ?skill= deep-links with prefilled inputs - Sample-output gallery: hand-written examples for the hero five + generator (scripts/build-samples.mjs) + web/examples.html - Skill-of-the-week: scheduled workflow + script that composes X/LinkedIn posts and posts to an optional webhook Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
58 lines
2.1 KiB
Markdown
58 lines
2.1 KiB
Markdown
# MCP Server
|
|
|
|
A zero-dependency [Model Context Protocol](https://modelcontextprotocol.io) server that exposes this skill library to **any MCP client** (Claude Code, Claude Desktop, Cursor, Windsurf, Cline…). Instead of installing 174 files, your assistant can **search and pull skills — and run workflow recipes — on demand**.
|
|
|
|
## One-line install (Claude Code)
|
|
|
|
```bash
|
|
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp
|
|
```
|
|
|
|
That's it — all 174 skills and 5 workflow recipes are now available in every Claude Code session, on any project.
|
|
|
|
## Tools
|
|
|
|
| Tool | What it does |
|
|
|---|---|
|
|
| `list_skills` | List every skill (name, tier, one-line description). Optional `tier` filter. |
|
|
| `search_skills` | Keyword search across name, description, and body — returns the best matches. |
|
|
| `get_skill` | Return the full instructions for one skill by name, ready to apply. |
|
|
| `list_workflows` | List workflow recipes — named chains of skills (e.g. ship-a-feature). |
|
|
| `get_workflow` | Return one recipe: the ordered skills to run and what each produces. |
|
|
|
|
## Configure it
|
|
|
|
**Claude Desktop** — add to `claude_desktop_config.json`:
|
|
|
|
```json
|
|
{
|
|
"mcpServers": {
|
|
"pm-claude-skills": {
|
|
"command": "npx",
|
|
"args": ["-y", "pm-claude-skills-mcp"]
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
**Cursor / Windsurf / Cline** — add the same `mcpServers` block to the client's MCP config (`~/.cursor/mcp.json`, Windsurf settings, etc.).
|
|
|
|
**From a local clone** (no npm install):
|
|
|
|
```json
|
|
{
|
|
"mcpServers": {
|
|
"pm-claude-skills": {
|
|
"command": "node",
|
|
"args": ["/absolute/path/to/pm-claude-skills/mcp/server.mjs"]
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
Restart the client. Then ask it to *"search the skills for customer churn"*, *"get the rice-prioritisation skill and apply it to my backlog"*, or *"run the ship-a-feature workflow for a referral program"* — it calls the tools automatically.
|
|
|
|
## How it works
|
|
|
|
Pure Node standard library, MCP stdio transport (newline-delimited JSON-RPC 2.0). It reads the bundled `skills/` at startup and serves them in-memory; all logging goes to stderr so it never corrupts the protocol stream. No network, no data leaves your machine.
|