A method for turning notes or longer analysis into a short executive memo that starts with the conclusion. BLUF means “bottom line up front.”

Use it to create a one-page memo, summarize a business case, or condense a narrative into a conclusion-first briefing.

It helps decision-makers understand the recommendation quickly while keeping the supporting reasons and uncertainties visible.

exec-memo — Skill for Claude Code by daddia/claude-for-strategy

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add daddia/claude-for-strategy --skill exec-memo

Clone the repo

git clone --depth 1 https://github.com/daddia/claude-for-strategy

Made for: Claude Code.

Or install consulting, the plugin that ships this one along with the rest of its 9 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/daddia/claude-for-strategy/exec-memo/github.svg)](https://agentmods.dev/skills/daddia/claude-for-strategy/exec-memo)

Your own site

<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/exec-memo"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/exec-memo/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/exec-memo"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/exec-memo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 711 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00049	$0.00711
Opus 5.5	$0.00020	$0.00284
Sonnet 5.5	$0.00010	$0.00142
Haiku 4.5	$0.00005	$0.00071

Measured 2mo ago against content hash e5d59310c7e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

exec-memo scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

consulting/skills/exec-memo/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Exec Memo

When to use

BLUF executive memo from narrative, notes, or narrative-builder output. Conclusion first per ../../references/bluf-conventions.md.

What this skill does not do

Does not bury the bottom line — BLUF is structural, not stylistic.
Does not exceed profile length by shrinking the bottom line — cut detail section.
Does not ship board-final without gate — confirm + reviewer note.

Preconditions

Input	If missing
Practice profile (length, audience)	Default one page; flag practice-setup
Source material or narrative	Ask for notes or run `narrative-builder`

Provisional mode

Raw notes only: compress inline; label structured first pass if MECE weak.

Trust spine

Per trust-conventions.md — sourcing, assumptions, numbers, confidence, gate before exec-final.

Analytical Rigor: Every WHY point traces to support; cut non-load-bearing detail.
Escalation: Ask missing → make impossible to miss; unverified claims → tag not smooth over.

Workflow

Read practice profile.
Use narrative-builder output if available; else compress notes inline.
Bottom line first (1–2 sentences, the answer).
WHY: 2–4 MECE points.
ASK: decision/resource/sign-off if any.
DETAIL: optional background last.
Check length vs profile.

Output format

[BOTTOM LINE]

WHY:
1. [point]
2. [point]

ASK: [or omit]

DETAIL: [...]

Worked example

Input: Notes on pricing failure. Bottom line: revert mid-tier increase.

Excerpt: BLUF states revert; WHY three MECE points (volume, elasticity, competitor); ASK: CFO sign-off by Friday.

Quality checks before delivering

Bottom line before context
MECE WHY section
ASK visible if needed
Length vs profile
Trust spine on figures

Propose profile update

When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/consulting/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /consulting:practice-setup auto-applies a full profile write.

Read the full file on GitHub · 92 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 92 lines · 49 tokens per session scan A e5d59310c7e3

Subscribe to this mod's changes

exec-memo is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 711 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Connectors Writing and docs agents claude cursor mcp skills

review

Run the full pre-merge panel: parallel audit and lens reviewers over a diff, consolidated into one severity-ranked verdict.

helderberto/agent-skills · 0 tokens

tdd

Test-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).

helderberto/agent-skills · 71 tokens

visual-review

Two visual modes — render a PR diff as an HTML page with each hunk annotated by principle, or check a UI change in a real browser (screenshots, console, network). Use for a visual/HTML diff report, "check the UI", or "screenshot before/after". Don't use for text-only feedback (/code-review), unit tests (/tdd), or full…

helderberto/agent-skills · 84 tokens

exec-memo