pm-claude-skills 28.1.0 → 28.2.0

package/README.md

@@ -4,7 +4,7 @@
   </a>
 </p>
 
-# 🧠 PM Skills — 205 Professional Agent Skills for Claude, ChatGPT, Gemini, Cursor, Codex & Hermes
+# 🧠 PM Skills — 206 Professional Agent Skills for Claude, ChatGPT, Gemini, Cursor, Codex & Hermes
 
 [![Stars](https://img.shields.io/github/stars/mohitagw15856/pm-claude-skills?style=social)](https://github.com/mohitagw15856/pm-claude-skills/stargazers)
 [![npm](https://img.shields.io/npm/v/pm-claude-skills?logo=npm&color=cb3837)](https://www.npmjs.com/package/pm-claude-skills)
@@ -14,12 +14,13 @@
 [![MCP](https://img.shields.io/badge/MCP-registry-0098FF?logo=modelcontextprotocol&logoColor=white)](https://github.com/mohitagw15856/pm-claude-skills#-use-it-anywhere--the-ai-ecosystem)
 [![Remote MCP](https://img.shields.io/badge/ChatGPT%20%C2%B7%20Claude.ai-connector-10A37F)](mcp-remote/)
 [![Smithery](https://smithery.ai/badge/mohit15856/pm-skills)](https://smithery.ai/servers/mohit15856/pm-skills)
-[![Skills](https://img.shields.io/badge/skills-205-blue)](https://github.com/mohitagw15856/pm-claude-skills)
+[![Skills](https://img.shields.io/badge/skills-206-blue)](https://github.com/mohitagw15856/pm-claude-skills)
 [![eval](https://img.shields.io/badge/eval--scored-196%20%C2%B7%20avg%204.8%2F5-brightgreen)](https://mohitagw15856.github.io/pm-claude-skills/leaderboard.html)
 [![Subagents](https://img.shields.io/badge/subagents-4-blueviolet)](agents/)
 [![Commands](https://img.shields.io/badge/slash%20commands-6-blueviolet)](commands/)
 [![Personas](https://img.shields.io/badge/personas-4-blueviolet)](output-styles/)
 [![Platforms](https://img.shields.io/badge/works%20with-Claude%20%7C%20ChatGPT%20%7C%20Gemini%20%7C%20Cursor%20%7C%20Codex%20%7C%20Hermes-8A2BE2)](#-works-with--cross-tool-compatibility)
+[![Integrations](https://img.shields.io/badge/integrates%20with-n8n%20%C2%B7%20Lovable%20%C2%B7%20Obsidian-0E9F6E)](connectors/)
 [![SkillCheck](https://img.shields.io/github/actions/workflow/status/mohitagw15856/pm-claude-skills/skillcheck.yml?branch=main&label=SkillCheck)](.github/workflows/skillcheck.yml)
 [![Security Audit](https://img.shields.io/github/actions/workflow/status/mohitagw15856/pm-claude-skills/skill-audit.yml?branch=main&label=security%20audit)](.github/workflows/skill-audit.yml)
 [![Version](https://img.shields.io/github/v/release/mohitagw15856/pm-claude-skills?label=version&color=brightgreen)](https://github.com/mohitagw15856/pm-claude-skills/releases)
@@ -29,20 +30,22 @@
 
 <p align="center">
   <a href="https://mohitagw15856.github.io/pm-claude-skills/">
-    <img src="https://readme-typing-svg.demolab.com?font=Inter&weight=600&size=24&pause=900&color=D97757&center=true&vCenter=true&width=720&lines=205+pro+AI+skills;PRDs%2C+roadmaps%2C+launches+%E2%80%94+done+right;Run+any+one+free+in+your+browser" alt="PM Skills" />
+    <img src="https://readme-typing-svg.demolab.com?font=Inter&weight=600&size=24&pause=900&color=D97757&center=true&vCenter=true&width=720&lines=206+pro+AI+skills;PRDs%2C+roadmaps%2C+launches+%E2%80%94+done+right;Run+any+one+free+in+your+browser" alt="PM Skills" />
   </a>
 </p>
 
 > **Generic AI gives you filler. These give you the structure a senior pro actually uses** — PRDs, exec updates, launch plans, postmortems — as open-source `SKILL.md` files. Across **21 professions**, not just product management. One source, every AI tool.
 
+> **🆕 Now plugs into your stack** — automate skills in **[n8n](connectors/n8n.md)**, build apps on **[Lovable](connectors/lovable.md)**, and run them in your **[Obsidian](connectors/obsidian.md)** vault, all via a read-only **[REST API](mcp-remote/#rest-api-for-n8n-lovable-make-any-http-tool)** on the hosted Worker.
+
 ### ⭐ If this saves you time, [star the repo](https://github.com/mohitagw15856/pm-claude-skills) — it's the #1 way to help others find it.
 
 > **PM stands for Professional, not just Product Management.**
-> 205 professional skills + 4 agent templates across 28 bundles covering 21 professions. Built for Claude Code — and now portable to ChatGPT, Gemini, and Hermes Agent. Built by a PM, used by everyone.
+> 206 professional skills + 4 agent templates across 28 bundles covering 21 professions. Built for Claude Code — and now portable to ChatGPT, Gemini, and Hermes Agent. Built by a PM, used by everyone.
 
 A community-built library of professional skills for every field — product management, engineering, customer success, marketing, social media, writers, design, legal, finance, HR, sales, operations, research, and more. Each skill is a structured `SKILL.md` file that teaches an AI assistant how to produce professional-grade outputs for your workflows. Skills run natively in **Claude Code** and **Hermes Agent** (same open `SKILL.md` standard), and ship as ready-to-paste exports for **ChatGPT** and **Gemini** — see [Works With](#-works-with--cross-tool-compatibility).
 
-**🆕 Latest release (v28.1.0 — Integrations):** PM Skills now plugs into **[n8n](connectors/n8n.md)**, powers **[Lovable](connectors/lovable.md)** apps, and lives in your **[Obsidian](connectors/obsidian.md)** vault — all backed by a read-only **REST API** (`/v1`) on the hosted Worker, auto-deployed via GitHub Actions. *Previously (v28.0.0 — live across the whole AI ecosystem):* every channel is now shipped & public — **[`pip install pm-skills`](https://pypi.org/project/pm-skills/)** (LangChain/CrewAI), the **hosted MCP connector** `https://pm-skills-mcp.pm-claude-skills.workers.dev/` (add to **ChatGPT/Claude.ai/Cursor** by URL), and the **[official MCP registry](https://github.com/mohitagw15856/pm-claude-skills/blob/main/server.json)** listing. See the new **[🌍 Use It Anywhere](#-use-it-anywhere--the-ai-ecosystem)** section. Also: **multi-model playground** (run any skill with your own **Claude / OpenAI / Gemini / Ollama** key — local models included), a **[remote MCP connector](mcp-remote/)** (add PM Skills to **ChatGPT, Claude.ai & Cursor** with one URL — no install), the MCP server now exposes skills as **prompts + resources**, **4 new IDE targets** (Cline, Continue, Zed, Roo — 9 platforms total), a **[Python package](python/)** (`pip install pm-skills` → LangChain/CrewAI tools), an **[`llms.txt`](https://mohitagw15856.github.io/pm-claude-skills/llms.txt)** for agent discovery, a reusable **[score-skills GitHub Action](.github/actions/score-skills/)**, and **MCP-registry manifests**. Plus the full library is now **eval-scored: 196 skills, avg 4.8/5**. **205 skills**. See the [changelog](#-changelog).
+**🆕 Latest release (v28.1.0 — Integrations):** PM Skills now plugs into **[n8n](connectors/n8n.md)**, powers **[Lovable](connectors/lovable.md)** apps, and lives in your **[Obsidian](connectors/obsidian.md)** vault — all backed by a read-only **REST API** (`/v1`) on the hosted Worker, auto-deployed via GitHub Actions. *Previously (v28.0.0 — live across the whole AI ecosystem):* every channel is now shipped & public — **[`pip install pm-skills`](https://pypi.org/project/pm-skills/)** (LangChain/CrewAI), the **hosted MCP connector** `https://pm-skills-mcp.pm-claude-skills.workers.dev/` (add to **ChatGPT/Claude.ai/Cursor** by URL), and the **[official MCP registry](https://github.com/mohitagw15856/pm-claude-skills/blob/main/server.json)** listing. See the new **[🌍 Use It Anywhere](#-use-it-anywhere--the-ai-ecosystem)** section. Also: **multi-model playground** (run any skill with your own **Claude / OpenAI / Gemini / Ollama** key — local models included), a **[remote MCP connector](mcp-remote/)** (add PM Skills to **ChatGPT, Claude.ai & Cursor** with one URL — no install), the MCP server now exposes skills as **prompts + resources**, **4 new IDE targets** (Cline, Continue, Zed, Roo — 9 platforms total), a **[Python package](python/)** (`pip install pm-skills` → LangChain/CrewAI tools), an **[`llms.txt`](https://mohitagw15856.github.io/pm-claude-skills/llms.txt)** for agent discovery, a reusable **[score-skills GitHub Action](.github/actions/score-skills/)**, and **MCP-registry manifests**. Plus the full library is now **eval-scored: 196 skills, avg 4.8/5**. **206 skills**. See the [changelog](#-changelog).
 
 ### ▶ See it in action — [try the live Skill Playground](https://mohitagw15856.github.io/pm-claude-skills/)
 
@@ -71,13 +74,13 @@ A community-built library of professional skills for every field — product man
 | 🔭 [Competitor Teardown](skills/competitor-teardown) | "what are rivals up to?" | a positioning map, feature gaps & strategy |
 | 📝 [Meeting Notes](skills/meeting-notes) | a raw transcript | decisions, owners & next steps |
 
-→ Want proof first? See [**real sample outputs**](https://mohitagw15856.github.io/pm-claude-skills/examples.html) from each skill. Like what you see? [**Install in 2 minutes**](#-quick-install-2-minutes) · [browse all 205 skills](#️-all-205-skills) · [**⭐ star the repo**](https://github.com/mohitagw15856/pm-claude-skills/stargazers) so others find it.
+→ Want proof first? See [**real sample outputs**](https://mohitagw15856.github.io/pm-claude-skills/examples.html) from each skill. Like what you see? [**Install in 2 minutes**](#-quick-install-2-minutes) · [browse all 206 skills](#️-all-206-skills) · [**⭐ star the repo**](https://github.com/mohitagw15856/pm-claude-skills/stargazers) so others find it.
 
 ---
 
 ## 🔄 One library, the whole professional workflow
 
-These 205 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:
+These 206 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:
 
 ```mermaid
 flowchart LR
@@ -96,7 +99,7 @@ flowchart LR
 | **📊 Measure** | Track outcomes & analyse | `metrics-framework` · `cohort-analysis` · `ab-test-planner` · `churn-analysis` |
 | **📣 Communicate** | Report up and out | `executive-update` · `board-deck-narrative` · `stakeholder-update` · `qbr-deck` |
 
-> New here? Start with the [**top-tier skills**](#️-skill-tiers--start-with-the-strongest), or jump straight to [**all 205 skills**](#️-all-205-skills) grouped by profession.
+> New here? Start with the [**top-tier skills**](#️-skill-tiers--start-with-the-strongest), or jump straight to [**all 206 skills**](#️-all-206-skills) grouped by profession.
 
 ---
 
@@ -192,7 +195,7 @@ Most skill repos are a folder of prompts. This one is a **system** — measured,
 
 | | **PM Skills** | Typical skill repo |
 |---|:---:|:---:|
-| Skills | **205**, across 21 professions | a handful → dozens, usually one domain |
+| Skills | **206**, across 21 professions | a handful → dozens, usually one domain |
 | Quality | **eval-scored** on a rubric + a public [benchmark](https://mohitagw15856.github.io/pm-claude-skills/benchmark.html) | trust the README |
 | Improves itself | ✅ eval → critique → rewrite (kept only if it scores higher) | ✗ |
 | Grounded in frameworks | ✅ each cites its source (RICE, JTBD, Pyramid Principle…) | rarely |
@@ -217,7 +220,7 @@ Most skill repos are a folder of prompts. This one is a **system** — measured,
 - [📦 Plugin Directory](#-plugin-directory)
 - [🤖 Building Blocks for Agent Templates](#-building-blocks-for-agent-templates)
 - [🏷️ Skill Tiers — start with the strongest](#️-skill-tiers--start-with-the-strongest)
-- [🗂️ All 205 Skills](#️-all-205-skills)
+- [🗂️ All 206 Skills](#️-all-206-skills)
 - [📋 Changelog](#-changelog)
 - [🤝 Contributing](#-contributing--add-your-skill)
 - [🔗 Related Projects](#-related-projects)
@@ -226,13 +229,13 @@ Most skill repos are a folder of prompts. This one is a **system** — measured,
 
 ## 🚀 Quick Install (2 minutes)
 
-**With the [`skills`](https://github.com/vercel-labs/skills) CLI** (the open agent-skills installer that works across Claude Code, Cursor, Codex, OpenCode & 60+ agents) — pick from all 205 interactively:
+**With the [`skills`](https://github.com/vercel-labs/skills) CLI** (the open agent-skills installer that works across Claude Code, Cursor, Codex, OpenCode & 60+ agents) — pick from all 206 interactively:
 
 ```bash
 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 205
+npx skills add mohitagw15856/pm-claude-skills --skill '*'            # install all 206
 ```
 
 **Or our own installer** — via the [`pm-claude-skills`](https://www.npmjs.com/package/pm-claude-skills) npm package (Windows/macOS/Linux, needs Node), which also installs subagents, slash commands & cross-tool exports:
@@ -241,7 +244,7 @@ npx skills add mohitagw15856/pm-claude-skills --skill '*'            # install a
 npx pm-claude-skills add --agent claude     # or: codex · cursor · hermes · openclaw
 ```
 
-**Or one-line MCP** — make all 205 skills + 5 workflow recipes available in *every* session of any MCP client (Claude Code, Claude Desktop, Cursor, Windsurf), no per-file install:
+**Or one-line MCP** — make all 206 skills + 5 workflow recipes available in *every* session of any MCP client (Claude Code, Claude Desktop, Cursor, Windsurf), no per-file install:
 
 ```bash
 claude mcp add pm-skills -- npx -y pm-claude-skills-mcp
@@ -298,7 +301,7 @@ ln -s ~/pm-claude-skills/skills/* ~/.claude/skills/
 
 ## 🌍 Use It Anywhere — the AI Ecosystem
 
-The same 205 skills reach you through every channel — pick whatever fits your stack:
+The same 206 skills reach you through every channel — pick whatever fits your stack:
 
 | Channel | Get it |
 |---|---|
@@ -312,7 +315,7 @@ The same 205 skills reach you through every channel — pick whatever fits your
 | 🖥️ **IDE rules** | Generated exports for **Cursor, Windsurf, Aider, Cline, Continue, Zed, Roo** — [`exports/`](exports/) |
 | 🤖 **Agents & answer engines** | [`llms.txt`](https://mohitagw15856.github.io/pm-claude-skills/llms.txt) makes the whole library discoverable & citable |
 
-> **196 of 205 skills are eval-scored, averaging 4.8/5** — see the [leaderboard](https://mohitagw15856.github.io/pm-claude-skills/leaderboard.html).
+> **196 of 206 skills are eval-scored, averaging 4.8/5** — see the [leaderboard](https://mohitagw15856.github.io/pm-claude-skills/leaderboard.html).
 
 ---
 
@@ -327,7 +330,7 @@ There are two kinds of support. **Native `SKILL.md` agents** read the file as-is
 auto-discover skills from the `description` frontmatter. **Other tools** take the markdown
 body as a system prompt — for those we ship ready-made [exports](#ready-to-use-exports).
 
-**In your editor (VS Code / Cursor):** the [**`vscode-extension/`**](vscode-extension/) brings all 205 skills into the Command Palette — search and *insert a skill as context* for Copilot/Cursor chat, copy it, or open it in the Playground.
+**In your editor (VS Code / Cursor):** the [**`vscode-extension/`**](vscode-extension/) brings all 206 skills into the Command Palette — search and *insert a skill as context* for Copilot/Cursor chat, copy it, or open it in the Playground.
 
 | Platform | How it works | Auto-trigger? |
 |---|---|---|
@@ -472,7 +475,7 @@ ANTHROPIC_API_KEY=sk-ant-… npx pm-claude-skills generate --from ./team-process
 
 **🏆 Skill Leaderboard — [evals](evals/).** An LLM-as-judge harness scores each skill across Claude models on structure, completeness, usefulness, and grounding. **[View the leaderboard →](https://mohitagw15856.github.io/pm-claude-skills/leaderboard.html)**
 
-> **Score the *whole* library, cheaply.** `npm run eval:gen-cases` writes a representative input for **all 205 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.
+> **Score the *whole* library, cheaply.** `npm run eval:gen-cases` writes a representative input for **all 206 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.
 
 ---
 
@@ -508,7 +511,7 @@ Not sure which plugin to install? Here's what each one covers:
 | **pm-advanced** | ai-ethics-review, ai-product-canvas, experiment-designer, design-handoff-brief, multi-source-signal-synthesiser | For PMs working on AI products or running sophisticated experiments. Covers ethical review of AI features, AI-native product canvases, and experiment design. |
 | **pm-analytics** | data-analysis-standard, product-health-analysis, retention-analysis | Turn raw data into PM-ready narratives. Use when you need to frame an analysis, explain health metrics to leadership, or diagnose retention drop-offs. |
 | **pm-business** | board-deck-narrative, investor-update, job-application | For PMs operating at the business layer — writing board narratives, investor updates, or crafting a standout job application. |
-| **pm-cross** | executive-summary, grant-proposal, last-30-days-research, notebooklm-connector, press-release, sycophancy-challenger, teaching-lesson-plan | Cross-profession utility skills that work outside a single domain — writing executive summaries, press releases, running research, and challenging sycophantic AI output. |
+| **pm-cross** | executive-summary, grant-proposal, last-30-days-research, notebooklm-connector, press-release, professional-brain, sycophancy-challenger, teaching-lesson-plan | Cross-profession utility skills that work outside a single domain — writing executive summaries, press releases, running research, and challenging sycophantic AI output, and giving the skills a durable memory with professional-brain. |
 | **pm-cs** | churn-analysis, cs-escalation-brief, cs-health-scorecard, customer-success-plan, qbr-deck, renewal-playbook | For PMs or CSMs responsible for retention. Covers churn diagnosis, escalation briefs, QBR decks, health scorecards, and renewal plays. |
 | **pm-data** | chart-data-extractor, cohort-analysis, dashboard-brief, data-pipeline-spec, metrics-framework, sql-query-explainer | Data-heavy work: extracting insights from charts, building metrics frameworks, explaining SQL queries, designing dashboards, and speccing data pipelines. |
 | **pm-delivery** | ab-test-planner, go-to-market-planner, pptx-slide-auditor, product-launch-checklist, retro-analysis, sprint-brief, sprint-planning, technical-spec-template, user-story-writer | Everything you need to ship: sprint planning, user stories, launch checklists, A/B test design, retros, and PowerPoint auditing. The most-used plugin for day-to-day delivery. |
@@ -548,7 +551,7 @@ Not sure which plugin to install? Here's what each one covers:
 
 On May 5, 2026, Anthropic [released their first agent templates](https://www.anthropic.com/news/finance-agents) — 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 205 skills here are the building blocks for agent templates outside of finance.**
+This library is the largest open-source collection of professional skills available — covering 20 professions beyond financial services. **The 206 skills here are the building blocks for agent templates outside of finance.**
 
 ### What is an agent template?
 
@@ -627,11 +630,11 @@ More templates will follow. If you want to contribute one, see the [template con
 
 ## 📋 Changelog
 
-**Latest: v28.1.0 — Integrations (n8n, Lovable, Obsidian) + a `/v1` REST API.** PM Skills now runs inside [n8n](connectors/n8n.md), powers [Lovable](connectors/lovable.md) apps, and lives in your [Obsidian](connectors/obsidian.md) vault — all backed by a read-only REST API on the hosted Worker (auto-deployed via a new GitHub Action). Builds on **v28.0.0 — live across the whole AI ecosystem.** Now public on every channel: **PyPI** (`pip install pm-skills`), a **hosted MCP connector** URL for ChatGPT/Claude.ai/Cursor, and the **official MCP registry** — plus a new **🌍 Use It Anywhere** section + PyPI/MCP header badges. Builds on the v27 ecosystem work: multi-model playground (Claude / OpenAI / Gemini / **Ollama**); a **remote MCP connector** ([`mcp-remote/`](mcp-remote/)) to add PM Skills to **ChatGPT, Claude.ai & Cursor** by URL; MCP server now serves skills as **prompts + resources**; **4 new IDE export targets** (Cline, Continue, Zed, Roo → 9 platforms); a **Python package** ([`python/`](python/), `pip install pm-skills` with LangChain/CrewAI adapters); an **`llms.txt`** for agent discovery; a reusable **[score-skills Action](.github/actions/score-skills/)**; and **MCP-registry manifests** (`server.json`, `smithery.yaml`). The full library is now eval-scored — **196 skills, avg 4.8/5**. Builds on **v26.0.0** (the Creator stack). **205 skills** across **28 bundles**, **21 professions**.
+**Latest: v28.1.0 — Integrations (n8n, Lovable, Obsidian) + a `/v1` REST API.** PM Skills now runs inside [n8n](connectors/n8n.md), powers [Lovable](connectors/lovable.md) apps, and lives in your [Obsidian](connectors/obsidian.md) vault — all backed by a read-only REST API on the hosted Worker (auto-deployed via a new GitHub Action). Builds on **v28.0.0 — live across the whole AI ecosystem.** Now public on every channel: **PyPI** (`pip install pm-skills`), a **hosted MCP connector** URL for ChatGPT/Claude.ai/Cursor, and the **official MCP registry** — plus a new **🌍 Use It Anywhere** section + PyPI/MCP header badges. Builds on the v27 ecosystem work: multi-model playground (Claude / OpenAI / Gemini / **Ollama**); a **remote MCP connector** ([`mcp-remote/`](mcp-remote/)) to add PM Skills to **ChatGPT, Claude.ai & Cursor** by URL; MCP server now serves skills as **prompts + resources**; **4 new IDE export targets** (Cline, Continue, Zed, Roo → 9 platforms); a **Python package** ([`python/`](python/), `pip install pm-skills` with LangChain/CrewAI adapters); an **`llms.txt`** for agent discovery; a reusable **[score-skills Action](.github/actions/score-skills/)**; and **MCP-registry manifests** (`server.json`, `smithery.yaml`). The full library is now eval-scored — **196 skills, avg 4.8/5**. Builds on **v26.0.0** (the Creator stack). **206 skills** across **28 bundles**, **21 professions**.
 
 Full [Keep a Changelog](https://keepachangelog.com/)-format history — every release back to the start — is in **[CHANGELOG.md](CHANGELOG.md)**.
 
-→ Earlier releases (v20 and before — the road from 6 to 205 skills) are in **[CHANGELOG.md](CHANGELOG.md)**.
+→ Earlier releases (v20 and before — the road from 6 to 206 skills) are in **[CHANGELOG.md](CHANGELOG.md)**.
 
 ---
 
@@ -667,7 +670,7 @@ This repo was built alongside a published 16-part article series on Medium.
 
 ## 🏷️ Skill Tiers — Start With the Strongest
 
-A 205-skill library doesn't have 205 equally-mature skills, and pretending otherwise
+A 206-skill library doesn't have 206 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.**
@@ -680,7 +683,7 @@ If you're new, install `pm-essentials` and try a couple of Production-Ready skil
 
 ---
 
-## 🗂️ All 205 Skills
+## 🗂️ All 206 Skills
 
 Every skill, grouped by profession. **[Browse the full per-skill catalog → SKILLS.md](SKILLS.md)** · **[searchable live catalog](https://mohitagw15856.github.io/pm-claude-skills/catalog.html)** · **[run any skill in the browser](https://mohitagw15856.github.io/pm-claude-skills/)**
 
@@ -703,7 +706,7 @@ Every skill, grouped by profession. **[Browse the full per-skill catalog → SKI
 | 🤝 Sales | `pm-sales` | 6 | `sales-battlecard` |
 | ⚙️ Operations | `pm-operations` | 10 | `sop-writer` |
 | 🏥 Research & Healthcare | `pm-research` | 4 | `literature-review` |
-| 🌐 Cross-Profession | `pm-cross` | 8 | `meeting-notes` · `red-team-review` |
+| 🌐 Cross-Profession | `pm-cross` | 9 | `meeting-notes` · `red-team-review` |
 | 🖼️ Figma | `pm-figma` | 10 | `figma-design-review` |
 | 📱 Social Media | `pm-social` | 5 | `social-media-strategy` |
 | ✍️ Writers & Content | `pm-writers` | 6 | `aeo-optimizer` |
@@ -714,7 +717,7 @@ Every skill, grouped by profession. **[Browse the full per-skill catalog → SKI
 
 ## ❤️ Sponsor This Work
 
-Building and maintaining 205 skills across 28 bundles takes real time — testing skills against new model releases, building new ones from community requests, writing the article series, and keeping documentation current.
+Building and maintaining 206 skills across 28 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 →](https://github.com/sponsors/mohitagw15856)** (or [☕ buy me a coffee](https://www.buymeacoffee.com/mohit15856)).
 

package/commands/brain.md

@@ -0,0 +1,13 @@
+---
+description: Set up or use your Professional Brain — init, ingest, recall, or review.
+argument-hint: [init | ingest <thing> | recall <query> | review]
+---
+
+Apply the **professional-brain** skill to: $ARGUMENTS
+
+- `init` — scaffold `brain/` (copy from `templates/brain/`) and migrate any existing `pm-context.md`.
+- `ingest <thing>` — save the original to `source/`, synthesise facts into the durable layer, tag each with provenance.
+- `recall <query>` — answer from memory using `scripts/brain_query.py`, citing each fact's file and tag; say so if memory is thin.
+- `review` — weekly sweep: flag stale hypotheses, decisions due to reopen, and contradictions.
+
+Default the brain location to `./brain/`. Never invent facts the brain doesn't hold, and never drop provenance tags.

package/connectors/lovable.md

@@ -73,7 +73,7 @@ just works.
 
 ```text
 KNOWLEDGE: PM Skills integration
-PM Skills is a free, read-only, CORS-open catalogue of 205 professional "skill"
+PM Skills is a free, read-only, CORS-open catalogue of 206 professional "skill"
 prompts (PRDs, exec updates, launch plans, etc.). Use it whenever the app needs to
 produce a structured professional document.
 

package/connectors/n8n.md

@@ -12,7 +12,7 @@ There are three ways in, from zero-build to native. Pick by how much you want to
 ## Tier 0 — MCP Client node (works today, no build)
 
 n8n's **AI Agent** node can use any external MCP server as a tool via the **MCP Client Tool**
-node. Point it at the hosted PM Skills connector and all 205 skills + 6 workflow recipes
+node. Point it at the hosted PM Skills connector and all 206 skills + 6 workflow recipes
 become tools the agent can call on demand.
 
 1. Add an **AI Agent** node (with your Anthropic/OpenAI credential).

package/exports/README.md

@@ -8,7 +8,7 @@ by hand; edit the source skill and run:
 node scripts/build-exports.mjs
 ```
 
-Currently exporting **205 skills** to:
+Currently exporting **206 skills** to:
 
 - **ChatGPT — Custom GPT instructions** → `exports/chatgpt/`
 - **Google Gemini — Gem instructions** → `exports/gemini/`

package/exports/aider/README.md

@@ -3,7 +3,7 @@
 > Auto-generated from `skills/*/SKILL.md` by `scripts/build-exports.mjs`.
 > **Do not edit these files by hand** — edit the source skill and regenerate.
 
-205 skills exported. Copy a `.mdc rule` into the tool to use it.
+206 skills exported. Copy a `.mdc rule` into the tool to use it.
 
 | Skill | Bundle | Path |
 |---|---|---|
@@ -149,6 +149,7 @@
 | Product Health Analysis | `pm-analytics` | `pm-analytics/product-health-analysis/product-health-analysis.md` |
 | Product Launch Checklist | `pm-delivery` | `pm-delivery/product-launch-checklist/product-launch-checklist.md` |
 | Product Positioning Doc | `pm-gtm` | `pm-gtm/product-positioning-doc/product-positioning-doc.md` |
+| Professional Brain | `pm-cross` | `pm-cross/professional-brain/professional-brain.md` |
 | Project Status Report | `pm-operations` | `pm-operations/project-status-report/project-status-report.md` |
 | Proposal Writer | `pm-sales` | `pm-sales/proposal-writer/proposal-writer.md` |
 | QBR Deck | `pm-cs` | `pm-cs/qbr-deck/qbr-deck.md` |

package/exports/aider/pm-cross/professional-brain/professional-brain.md

@@ -0,0 +1,162 @@
+# Professional Brain Skill
+
+Most skills start cold — you paste the same context every time, and decisions made six weeks
+ago lose the *why*. This skill gives the library a **memory**: a plain-markdown `brain/` folder
+on disk that skills read before they answer and write to after. No vector DB, no cloud — just
+grep-able files you (and Claude) can audit and edit.
+
+This is the **state layer** of an AI teammate. Pair it with the action layer (skills that file
+tickets / open PRs) and you get a loop: *recall → do the work → record the decision → review.*
+
+## What This Skill Produces
+
+- A scaffolded **`brain/` folder** with a fixed schema (see below).
+- **Provenance-tagged** knowledge — every claim says where it came from and how strong it is.
+- Four operations you can invoke: **init**, **ingest**, **recall**, **review**.
+- A standing contract other skills follow: *read the relevant brain files first; write durable
+  outcomes (decisions, new facts, stakeholder asks) back.*
+
+## Required Inputs
+
+Ask for these only if they aren't already on disk or in the request:
+
+- **Which operation** — `init`, `ingest`, `recall`, or `review` (default: infer from the ask).
+- For **ingest**: the artifact (a pasted note, a file path, a transcript) and what it's about.
+- For **recall**: the topic or question to answer from memory.
+- The **brain location** — default `./brain/` at the project root.
+
+## The Brain Schema
+
+```
+brain/
+  context.md      # who/what: product, ICP, metrics definitions, voice (supersedes pm-context.md)
+  knowledge/      # durable facts — strategy.md, market.md, users.md, org.md
+  decisions/      # one file per decision: what, why, alternatives rejected, reopen-when
+  hypotheses/     # assumptions: statement, evidence, status (open/validated/invalidated)
+  stakeholders/   # one file per person: asks, concerns, comms history
+  entities/       # typed objects: features, accounts, experiments — the artifact graph
+  source/         # immutable originals (audit trail) — never edited after capture
+```
+
+It is Obsidian-vault compatible: open `brain/` as a vault and the links become a graph.
+
+## Provenance Tags (the trust mechanism)
+
+Every fact carries a tag in square brackets so its strength is explicit. Skills must keep the
+tag when they reuse a fact, and **downgrade confidence for weak tags**.
+
+| Tag | Means | Strength |
+|---|---|---|
+| `[data]` | from analytics / a metric / a measured result | strong |
+| `[interview]` | from a documented user or customer interview | strong |
+| `[external]` | from third-party / market research | medium |
+| `[verbal]` | said in a meeting, not independently documented | weak |
+| `[hunch]` | informed intuition, no evidence yet | weakest |
+
+Example: `Mobile drives 65% of DAU [data]. Enterprise wants SSO before renewing [verbal].`
+
+## Operations
+
+**init** — Create the folder schema. Migrate an existing `pm-context.md` into `context.md`.
+Offer to ingest any artifacts the user already has (Notion export, Jira CSV, notes).
+
+**ingest `<thing>`** — Store the original verbatim in `source/`, then synthesise it into the
+right durable file(s) (`knowledge/`, `decisions/`, `hypotheses/`, `stakeholders/`), tagging each
+extracted claim with its provenance. Never discard the source.
+
+**recall `<query>`** — Answer from memory. Use the helper script to find matching facts across
+the brain, then synthesise an answer that **cites each fact's file and tag**. If memory is thin,
+say so rather than inventing.
+
+**record** — The write-back half of the loop (Phase 1). After a skill produces an artifact (or on
+demand), extract the **durable outcomes** worth remembering — decisions made, new facts learned,
+assumptions surfaced, stakeholder asks — and propose them as a numbered list, each with its
+**target section** and **provenance tag**. This is the action surface, so it is **approval-gated
+and dry-run by default**:
+
+1. **Propose** — show the records you'd write (section · tag · text). Preview with
+   `brain_write.py …` (no `--commit`), which prints exactly what would be appended.
+2. **Approve** — the user confirms, edits, or drops items. Never write without a yes.
+3. **Append** — write the approved records with `--commit`. Append-only: decisions become a new
+   numbered file; everything else appends to its named file. Nothing is overwritten.
+
+Downgrade weak evidence honestly — a conclusion from one call is `[interview]`, a gut call is
+`[hunch]`; don't launder it into `[data]`.
+
+**review** — Weekly sweep. Flag: stale hypotheses (open too long with no new evidence),
+decisions whose `reopen-when` condition now holds, contradictions between files, and facts that
+are only `[hunch]`/`[verbal]` but are being treated as settled. Draft the updates; don't apply
+silently.
+
+## Programmatic Helper
+
+`scripts/brain_query.py` (stdlib only) does deterministic recall — it greps the brain for a
+query and returns matches with their file and detected provenance tag, so retrieval is
+transparent (no embeddings, no guessing).
+
+```bash
+# Find what the brain knows about "activation", newest-first, as text
+python3 scripts/brain_query.py ./brain "activation"
+
+# JSON for chaining into another step
+python3 scripts/brain_query.py ./brain "enterprise SSO" --json
+```
+
+Use its output as the grounded evidence set, then synthesise the answer on top — never answer a
+recall from outside the brain without saying so.
+
+`scripts/brain_write.py` is the write-back counterpart — it **appends** a provenance-tagged record
+(append-only, never overwrites) and is **dry-run by default** so you can preview before committing:
+
+```bash
+# Preview what would be written (changes nothing):
+python3 scripts/brain_write.py ./brain decisions "Prioritise mobile" --tag data --body "68% of churn is mobile" --source "Q3 analytics"
+
+# Write it after approval:
+python3 scripts/brain_write.py ./brain decisions "Prioritise mobile" --tag data --body "…" --source "Q3 analytics" --commit
+```
+
+## The contract for other skills
+
+A brain-aware skill adds a short **"Reads from / Writes to the Brain"** section:
+
+- **Reads:** before producing, pull the relevant files (e.g. `prd-template` reads `context.md`,
+  `knowledge/strategy.md`, and any related `hypotheses/` + `entities/`).
+- **Writes:** after producing, append durable outcomes (e.g. `meeting-notes` writes each
+  decision to `decisions/`, new asks to the relevant `stakeholders/` file), each provenance-tagged.
+
+## Output Format
+
+For **ingest**, confirm what was captured:
+
+### Ingested: [artifact]
+- **Source saved:** `source/[file]`
+- **Knowledge updated:** `knowledge/[file]` — [facts added, each tagged]
+- **Decisions logged:** `decisions/[id]` — [if any]
+- **Hypotheses touched:** [statement → status]
+- **Open follow-ups:** [anything needing a human]
+
+For **recall**, answer then show your grounding:
+
+### Recall: [query]
+[Synthesised answer.]
+
+**Grounded in:**
+- `decisions/0003-...md` — "..." `[data]`
+- `stakeholders/sarah.md` — "..." `[verbal]`
+
+## Quality Checks
+
+- [ ] Every extracted claim carries a provenance tag
+- [ ] The verbatim original is saved in `source/` before synthesis
+- [ ] Recall answers cite the file + tag for each fact, and flag thin memory instead of inventing
+- [ ] Decisions record the rejected alternatives and a `reopen-when` condition
+- [ ] `[hunch]`/`[verbal]` facts are never presented with the confidence of `[data]`/`[interview]`
+
+## Anti-Patterns
+
+- [ ] Do not paraphrase a source into the durable layer without keeping the original in `source/` — the audit trail is the point
+- [ ] Do not drop provenance tags when reusing a fact — an untagged claim is an unfalsifiable one
+- [ ] Do not answer a recall from general knowledge and present it as something the brain "knows" — say when memory is empty
+- [ ] Do not overwrite a decision when it changes — append a new dated entry so the history survives
+- [ ] Do not build a vector database or hide memory behind embeddings — the brain stays plain, grep-able markdown a human can read and correct

package/exports/aider/pm-cs/churn-analysis/churn-analysis.md

@@ -2,6 +2,13 @@
 
 Produce a structured churn analysis that goes beyond the headline rate — identifying why customers leave, which segments are most at risk, and what interventions will have the highest impact on retention.
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know:
+
+- **Read first:** `context.md` (metric definitions — what "churn" means here), `knowledge/`, and related segment `entities/`. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "churn"` and carry each fact's provenance tag through.
+- **📥 Propose to the Brain:** after producing, propose recording the headline retention finding to `knowledge/` (`[data]`), any retention decision to `decisions/`, and at-risk drivers as `hypotheses/`. Show them, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default).
+
 ## Required Inputs
 
 Ask for these if not already provided:

package/exports/aider/pm-cs/cs-health-scorecard/cs-health-scorecard.md

@@ -2,6 +2,13 @@
 
 Produce a structured, data-driven health scorecard for a customer account — giving the CSM and leadership a clear view of renewal risk, expansion potential, and the actions needed to move the account in the right direction.
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know:
+
+- **Read first:** the account's `entities/` file, its `stakeholders/` (champion, economic buyer, detractors), and `knowledge/`. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<account name>"` and carry each fact's provenance tag through.
+- **📥 Propose to the Brain:** after producing, propose recording the health verdict + key risks to the account `entities/` file, and a renewal-risk entry to `decisions/` if a call is made, each provenance-tagged. Show them, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default).
+
 ## Required Inputs
 
 Ask for these if not already provided:

package/exports/aider/pm-delivery/sprint-planning/sprint-planning.md

@@ -2,6 +2,13 @@
 
 Transform raw backlog items into a structured, achievable sprint with clear goals, velocity-calibrated scope, and team-ready output.
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know:
+
+- **Read first:** priority `decisions/` (what the team agreed matters), feature `entities/`, and open `hypotheses/` the sprint might test. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<sprint goal>"` and carry each fact's provenance tag through.
+- **📥 Propose to the Brain:** after producing, propose logging the sprint commitment (goal + committed scope) as a `decisions/` record, provenance-tagged. Show it, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default).
+
 ## What This Skill Produces
 
 - **Sprint Goal** — single, outcome-focused sentence the whole team can rally around

package/exports/aider/pm-essentials/competitive-analysis/competitive-analysis.md

@@ -2,6 +2,13 @@
 
 Create structured competitive analyses for product decision-making.
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know:
+
+- **Read first:** `knowledge/` (market + positioning) and competitor `entities/`. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<competitor or market>"` and carry each fact's provenance tag through — a competitor claim from a press release is `[external]`, not `[data]`.
+- **📥 Propose to the Brain:** after producing, propose recording new competitor facts to `knowledge/` (`[external]`) and creating/updating competitor `entities/`. Show them, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default).
+
 ## Required Inputs
 
 Ask the user for these if not provided:

package/exports/aider/pm-essentials/meeting-notes/meeting-notes.md

@@ -10,6 +10,17 @@ Ask the user for these if not provided:
 - **Raw notes or transcript** (paste discussion notes, a transcript, or describe what was discussed)
 - **Meeting type** (1:1 / sprint planning / product review / stakeholder sync / other) — determines which template to use
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, this is where notes become durable memory:
+
+- **Read first:** the relevant `stakeholders/` files (so you arrive knowing each attendee's
+  open asks and concerns) and any `decisions/` the meeting revisits.
+- **Write after:** append each **decision** (with its rationale and a `reopen-when`) to
+  `decisions/`, add new **asks/concerns** to the right `stakeholders/` file, and flag any new
+  **assumption** into `hypotheses/`. Tag every captured fact with its provenance — most meeting
+  statements are `[verbal]` until independently confirmed. Save the raw notes to `source/`.
+
 ## Standard Meeting Notes Template
 
 ### Meeting Header

package/exports/aider/pm-essentials/prd-template/prd-template.md

@@ -12,6 +12,18 @@ Ask the user for these if not provided:
 - **Scope** (MVP vs full vision — what's in and out of scope)
 - **Key stakeholders** (who needs to review and approve)
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, use it instead of asking for context you already have:
+
+- **Read first:** `context.md` (product, metrics definitions, voice), `knowledge/strategy.md`
+  (where the product is going), any related `hypotheses/` and the matching `entities/` feature
+  file. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<feature>"` to pull
+  grounded facts, and carry their provenance tags into the PRD (don't present a `[hunch]` as a
+  settled requirement).
+- **Write after:** save the feature as/into `entities/<feature>.md`, log any scoping decision to
+  `decisions/`, and add new assumptions to `hypotheses/`. Tag each with its provenance.
+
 ## Template Structure
 
 Every PRD should include these sections in order:

package/exports/aider/pm-planning/okr-builder/okr-builder.md

@@ -2,6 +2,13 @@
 
 Write ambitious, measurable OKRs that connect product work to company strategy. Avoid vanity metrics, output-focused key results, and objectives that sound like task lists.
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know:
+
+- **Read first:** `context.md` (metric definitions), `knowledge/strategy.md` (where the product is going), and any open `hypotheses/`. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<objective theme>"` and carry each fact's provenance tag through — don't set a key result off a `[hunch]` as if it were `[data]`.
+- **📥 Propose to the Brain:** after producing, propose logging the chosen objectives + KR targets as a `decisions/` record (the period's bet) and any new metric definitions to `knowledge/`, each provenance-tagged. Show them, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default).
+
 ## Working from a brief
 
 You will often get a short brief without every detail (no baselines, no exact numbers). **Always deliver a complete, specific OKR set anyway** — do not stop to ask questions and do not leave bracketed placeholders like `[target]`. Where a baseline or number is missing, infer a realistic value from the brief and the domain, and mark it *(assumed — confirm)*. A clearly-labelled assumed baseline (e.g. "activation 40% *(assumed)* → 60%") is always better than a blank or an invented-as-fact figure.

package/exports/aider/pm-planning/rice-prioritisation/rice-prioritisation.md

@@ -2,6 +2,13 @@
 
 Apply consistent, criteria-based RICE scoring to a list of features or initiatives to produce an objective prioritisation ranking.
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know:
+
+- **Read first:** `knowledge/strategy.md` (so the ranking serves the direction), the items as `entities/`, and impact `hypotheses/`. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<initiative theme>"` and carry each fact's provenance tag through — an impact estimate is usually a `[hunch]`, not `[data]`.
+- **📥 Propose to the Brain:** after producing, propose recording the ranking decision to `decisions/` and the reach/impact estimates as `hypotheses/` tagged by evidence strength. Show them, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default).
+
 ## Required Inputs
 
 Ask the user for these if not provided:

package/exports/aider/pm-planning/roadmap-narrative/roadmap-narrative.md

@@ -2,6 +2,13 @@
 
 Convert a ranked list of product initiatives into a clear, strategic narrative that connects individual items to company goals and communicates a coherent product direction.
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know:
+
+- **Read first:** `knowledge/strategy.md` (the direction the narrative must ladder to), priority `decisions/`, and feature `entities/`. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<roadmap theme>"` and carry each fact's provenance tag through.
+- **📥 Propose to the Brain:** after producing, propose logging the sequencing/priority decisions to `decisions/` and updating the relevant feature `entities/`, each provenance-tagged. Show them, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default).
+
 ## Working from a brief
 
 You will often get a short brief (a few themes, an audience) without a full initiative list or OKRs. **Always deliver the complete narrative anyway** — do not stop to ask questions and do not leave bracketed placeholders like `[Theme Name]`. Where detail is missing, infer specific, realistic themes, initiatives, and metrics from the brief and the domain, and mark any inferred fact or number as *(assumed — confirm)*. Fill every section with concrete content, not template brackets.

package/exports/aider/pm-strategy/executive-update/executive-update.md

@@ -2,6 +2,13 @@
 
 Produce a stakeholder update that busy executives will actually read — structured around what they care about: decisions, risks, and numbers.
 
+## Reads from / Writes to the Brain
+
+If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know:
+
+- **Read first:** recent `decisions/`, `knowledge/` (the headline numbers + their definitions), and `context.md` (voice). Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<period or initiative>"` and carry provenance through — flag a metric that's only `[verbal]`.
+- **📥 Propose to the Brain:** the update mostly *reads* — but propose recording any **new** decision or commitment it surfaces to `decisions/`, provenance-tagged. Show it, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default).
+
 ## Required Inputs
 
 Ask the user for these if not provided: