Install
openclaw skills install @mohitagw15856/board-pre-readWrite 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.
openclaw skills install @mohitagw15856/board-pre-readThe 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.
Ask for these only if they aren't already provided:
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 misses honestly — boards trust founders who surface bad news first.
| Metric | This period | vs. plan | Trend | Note |
|---|
3. What's working — the 2–3 things going well and why (so they can be doubled down on).
4. What's not — the 2–3 problems, what you're doing about them, and where you want the board's help. Candour here is the whole game.
5. Decisions & asks — explicit: "We're asking the board to approve X" / "We'd value input on Y" / "We need intros to Z." Tie each to the agenda.
6. Risks & watch-items — the top risks to the plan and runway, and the leading indicators you're watching.
Appendix — detail, financials, and supporting data (linked, not inline).
Board-management practice — pre-circulated reading, metrics-vs-plan transparency, and decision-focused agendas.