PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/board-deck-narrative)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/board-deck-narrative"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/board-deck-narrative/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/board-deck-narrative"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/board-deck-narrative.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.01714 |
| Opus 5 | $0.00026 | $0.00857 |
| Sonnet 5 | $0.00011 | $0.00343 |
| Haiku 4.5 | $0.00005 | $0.00171 |
Grade A, and why
board-deck-narrative scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Board Deck Narrative Skill
This skill builds the complete narrative and slide structure for a board presentation — from opening framing to closing asks. It produces slide-by-slide content guidance, not just a list of topics.
Required Inputs
Ask the user for these if not provided:
- Company stage and context (Seed / Series A / Growth — and where you are in the year)
- Board meeting type (Regular quarterly / Annual / Special / Fundraise-related)
- Key themes for this meeting (e.g. strong growth quarter / pivoting strategy / hiring challenge / fundraise update)
- Key metrics to feature
- Decisions needed from the board (if any)
- Time available (e.g. 60 min / 90 min)
- Audience (investors only / investors + independent directors / mixed)
Output Structure
Board Deck Narrative: [Company] — [Quarter/Period]
Meeting type: [Regular quarterly / Special] Time: [X minutes] Narrative theme: [The one-sentence story of this quarter — e.g. "We hit our revenue target, but activation is the problem we need to solve together."]
Opening Frame (Slide 1–2)
Slide 1: Title
- Company name, quarter, date
- One-sentence framing of the meeting's narrative arc
Slide 2: Agenda
- List of sections + time allocation
- Flag which sections need board input vs. are informational
Presenter note: Board members are busy. Tell them in the first 2 minutes what you need from them today. It changes how they listen.
Business Performance (Slides 3–6, ~15 min)
Slide 3: Scorecard / KPI Dashboard
- Content: Key metrics vs. targets for the quarter. No more than 6 metrics.
- Format: Traffic-light table (Green / Amber / Red against plan)
- Narrative: [1–2 sentences — the headline story of the quarter in numbers]
- Don't hide reds. Boards lose trust when they discover hidden problems later.
Slide 4: Revenue / Growth Deep Dive
- Content: Revenue breakdown by segment, cohort retention, growth drivers
- Key message: [What the data shows about the health of growth]
- Call out: [Any trend that needs board context or discussion]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 171 lines · 53 tokens per session scan A 591739b88b14
board-deck-narrative is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,714 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.