Individual skill

nonprofit-board-pack

Builds the nonprofit board meeting pack that produces engagement instead of nodding - a one-page dashboard of finances, program KPIs, and fundraising pipeline up front, routine items batched into a consent agenda, one real decision per meeting, and an explicit ask naming what board members can do. Use when a nonprofit ED says "prepare the board packet", "our board meetings are just report-outs", "the board approves everything without discussion", "what should go in the board dashboard", or "how do I get the board to actually help". Do NOT use for general board governance strategy, recruitment, or managing board dynamics - use board-management instead - and do NOT use for the public annual report - use impact-report-builder instead.

skills/nonprofit-board-pack/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Nonprofit Board Pack

Most nonprofit board meetings are serial report-outs: the ED talks for fifty minutes, the board nods, and the organization's best-connected volunteers go home having decided nothing and been asked for nothing. The board pack determines the meeting - a pack built as reports produces nodding; a pack built around a dashboard, a decision, and an ask produces a working board. This skill builds that pack. For governance strategy beyond the meeting - recruitment, composition, officer roles, managing a difficult chair - route to board-management; this skill owns the packet and the meeting it shapes.

Work the example organization throughout: Bright Futures Tutoring, a youth-education nonprofit with a $420,000 annual budget, 3 staff, serving 250 students, with a $180,000 grant goal and a $75,000 Hearthstone Foundation ask in play.

## Operating procedure

Send the pack 5-7 days before the meeting - late enough to be current, early enough that "I didn't have time to read it" is a choice. Under 10 pages total; the dashboard does the compression.

### Step 1: Build the one-page dashboard (the dashboard-first rule)

Page one is always a single-page dashboard with three blocks - finances, program KPIs, fundraising pipeline - each showing actual vs plan and direction vs last meeting. The rule exists because board members are part-time: they will reliably read one page, and if that page holds the whole organization's vitals, every member arrives oriented even if they read nothing else.
Back to top