board-pre-read
Write a board pre-read that's sent before the meeting so the meeting is about decisions, not status. Use when asked to prepare a board pre-read, a board update/package, or pre-meeting materials for a board. Produces a board pre-read — a TL;DR, the metrics dashboard vs. plan, what's working / what's not, the decisions and asks for the board, and risks — designed to be read in advance.
npx skills add mohitagw15856/pm-claude-skills --skill board-pre-read --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Board Pre-Read Skill The best board meetings spend zero time on status because the board already read it. A pre-read sent 48+ hours ahead does that: it conveys the state of the business and, crucially, tells the board exactly what input and decisions are needed — so the meeting is discussion and decisions, not a slide-reading session. This skill structures that document. ## Required Inputs Ask for these only if they aren't already provided: - **The headline** — the one thing the board should take away this period (good or bad). - **Metrics vs. plan** — the key numbers against the plan/forecast (revenue, growth, burn, runway, the north-star). - **What changed** — major wins, misses, and shifts since last meeting. - **Decisions/asks** — what you actually need from the board (approval, input, introductions). ## Output Format ### Board Pre-Read — [company], [month/quarter] **Sent:** [date, ≥48h before the meeting] **1. TL;DR** — 3–5 bullets: the state of the business, the headline, runway, and the decisions you're bringing. A busy board member should get the gist from this alone. **2. Metrics dashboard** — the core numbers vs. plan, with the trend and a one-line "so what" each. Show
- Required Inputs
- Output Format
- Board Pre-Read — [company], [month/quarter]
- Quality Checks
- Anti-Patterns
- Based On
What does the board-pre-read skill do?
Write a board pre-read that's sent before the meeting so the meeting is about decisions, not status. Use when asked to prepare a board pre-read, a board update/package, or pre-meeting materials for a board. Produces a board pre-read — a TL;DR, the metrics dashboard vs. plan, what's working / what's not, the decisions and asks for the board, and risks — designed to be read in advance.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill board-pre-read --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.