From grc-reporter
Audience-specific tone and format guidance for leadership communications. Use when drafting any /report:* output to tune length, framing, and technical depth to the reader (board, audit committee, CEO, weekly CISO, regulator).
How this skill is triggered — by the user, by Claude, or both
Slash command
/grc-reporter:exec-narrative-patternsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Different readers want different things. The same findings should not land the same way in a board deck, a CISO 1:1, and a regulator response.
Different readers want different things. The same findings should not land the same way in a board deck, a CISO 1:1, and a regulator response.
| Audience | Length budget | Opening line wants | Technical depth | What they skip |
|---|---|---|---|---|
| Full board | 1 page max | Strategic posture one-liner | Low. No control IDs in body. | Operational detail, acronyms, tables with >5 rows |
| Audit committee | 2 pages | Risk-and-assurance posture | Medium. Control families OK, not IDs. | Strategy monologue, vendor names unless load-bearing |
| Risk committee | 2 pages | Residual risk movement | Medium-high. Framework names, risk scoring. | Program branding, tool selection detail |
| CEO weekly | Half page | What changed, what's blocking, what's asked | Low. Translate everything. | Framework politics, tool comparisons |
| CISO weekly | 1 page | What moved, what's blocked, what's next | High. Control IDs, tool names, owner names fine. | Over-explained context |
| Regulator / auditor | As long as needed | Precise scope + evidence | Maximum. IDs, artifact paths, timestamps. | Narrative softening |
Board and audit committee
CEO weekly
CISO weekly
Regulator / auditor
YYYY-MM-DD. Periods are YYYY-Q# or YYYY-W##.If you cannot defend every sentence as "the audience needed this to make a decision," cut it.
If the document opens with context before the point, invert it.
If there are three open items and no ask, you are reporting, not communicating. Add the ask.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub abnejllc/grc --plugin grc-reporter