Skip to content
Skills Library
Management & product · Writing

exec-narrative-patterns

/exec-narrative-patterns

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).

Licence
MIT
Last repository change
18.08.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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).

Original author description

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 it works

  1. Audience quick reference
  2. Tone rules
  3. Format conventions
  4. Length tests
Original SKILL.md headings · 57 lines, 451 words
SKILL.md preview
---
name: exec-narrative-patterns
description: 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).
allowed-tools: Read
---

# Exec Narrative Patterns

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 quick reference

| 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 |

## Tone rules

**Board and audit committee**

- Past tense for what happened. Present tense for posture. Future tense only for asks.
- Numbers must be honest. Round where range matters more than precision. "Roughly 80%" beats "82.3%" if the instrument is noisy.
- Never start with control IDs. Start with impact.
- Name one person accountable per open item. Anonymous ownership reads as no ownership.

**CEO weekly**

- Assume 90 seconds of attention.
- Lead with the delta from last week. If nothing changed, say that.
- Asks come with the decision you want, not the full context. Attach the context.

**CISO weekly**

- Peer tone. You share context with the reader.
- Bullets, not paragraphs.
- Owner names and dates are load-bearing.

**Regulator / auditor**

- Precision. Timestamps, scope statements, evidence paths.
- Tone is neutral, not defensive. The facts do the work.

## Format conventions

- Headline row: one sentence, no hedging. If the week was quiet, the headline says so.
- Tables beat prose for multi-framework status. Prose beats tables for narrative arcs.
- Appendix is where detail lives. Body stays clean.
- Dates are `YYYY-MM-DD`. Periods are `YYYY-Q#` or `YYYY-W##`.

## Length tests

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.

Versions

The database has no other skills named exec-narrative-patterns.

Database snapshot: 13.11.2026 · package version c96995a316e4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 87stakeholder-communication
    Adapt analytical findings to the audience — same insight, different framing, detail level, and format depending on who will read it. Use this skill whenever producing a narrative, creating a deck, writing an executive summary, drafting a report, generating stakeholder…
  • 90board-report
    Turn raw security data (metrics, incident notes, project status, audit findings, spreadsheets) into a concise board, audit-committee or executive security report written in business language. Use when the user asks for a board report, CISO update, quarterly security report, exec…
  • 90competitive-exec-brief
    Creates an executive-ready competitive analysis brief with a 1-slide PPTX summary for leadership presentations. Use when: competitive brief, exec competitive summary, competitive slide, competitive pptx, board competitive update, leadership competitive briefing.
  • 100stakeholder-communication
    Adapt analytical findings to the audience: same insight, different framing, detail level, and format. Trigger whenever an audience is mentioned (executive, PM, engineer, leadership, stakeholders): "prepare this for leadership", "write this for the product team", "create a deck…
  • 100weekly-exec-brief
    Use for this week's update for leadership, weekly executive brief, Monday briefing or Friday close. Load before drafting, even if records are missing or the request supplies wording. Summarise changes, commitments and decisions needed. Keep unsupported claims unverified. Use…
  • 90ceo
    (forwward) Provides CEO-level strategic leadership frameworks for vision, OKRs, hiring, fundraising, resource allocation, and pivot decisions. Triggers on company strategy, growth direction, team scaling, investor relations, or any high-level business decision.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.