top-down-memo

top-down-memo is a skill for Claude Code, Codex from sruthir28/enterprise-ai-skills. It costs 93 tokens per session (2,274 once invoked), scanned A, original, MIT.

A writing framework that puts the conclusion first, followed by a small set of supporting reasons and the evidence behind them.

In plain words
What is it for?
Use it for recommendations, findings, assessments, memos, emails, briefings, and other writing where the decision or message should be clear at the start.
Why use it?
It lets readers understand the main answer quickly instead of making them follow the order in which the writer discovered the information.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for recommendations, findings, assessments, memos, emails, briefings, and other writing where the decision or message should be clear at the start.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sruthir28/enterprise-ai-skills/top-down-memo
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 sruthir28/enterprise-ai-skills --skill top-down-memo
Clone the repo
git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills

Made for: Claude Code, Codex.

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.

agentmods badge for top-down-memo

README.md
[![agentmods](https://agentmods.dev/badge/skills/sruthir28/enterprise-ai-skills/top-down-memo/github.svg)](https://agentmods.dev/skills/sruthir28/enterprise-ai-skills/top-down-memo)
Your own site
<a href="https://agentmods.dev/skills/sruthir28/enterprise-ai-skills/top-down-memo"><img src="https://agentmods.dev/badge/skills/sruthir28/enterprise-ai-skills/top-down-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.

agentmods 80×15 button for top-down-memo

Your own site · 80×15
<a href="https://agentmods.dev/skills/sruthir28/enterprise-ai-skills/top-down-memo"><img src="https://agentmods.dev/badge/skills/sruthir28/enterprise-ai-skills/top-down-memo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,274 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.02274
Opus 5 $0.00046 $0.01137
Sonnet 5 $0.00019 $0.00455
Haiku 4.5 $0.00009 $0.00227

Measured 11d ago against content hash c133e4cae4a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

top-down-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 11d 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.

top-down-memo/SKILL.md · 193 lines

How it starts

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

Top-Down Memo

The McKinsey writing rule: lead with the answer. Chronological narratives ("first we did X, then Y, then Z, and concluded W") are how thinking happens, not how communication should land. Top-down inverts the order — conclusion first, then the structure that supports it, then the evidence.

This is also called BLUF (Bottom Line Up Front) in military writing and Minto Pyramid in consulting. Same idea. Different name.

The test: can the reader stop after the first paragraph and still know what you think and what you want? If yes, top-down. If they need to read to the end to find the answer, you wrote a story.


Why people don't do this naturally

The way you thought about something is the opposite of how the reader needs to hear it.

You (writer) Reader
Gathered data → found patterns → drew conclusion Wants the conclusion → then patterns → then data only if they push back

Chronological narrative is easier to write because it matches your discovery path. It's harder to read because the reader doesn't know where you're going. Reversing the order is unnatural but obviously correct.


Design choices

  • Lead is the answer, not the setup. The first sentence states what you think. The reader can stop here.
  • 2–4 supporting arguments. Rule of 3 is best. >4 means you haven't synthesized; <2 means it's a one-liner, not a memo.
  • MECE at the argument level. The supports should not overlap and should jointly defend the lead.
  • Evidence under each argument, not in a separate section. Reader skims to the argument they doubt, then drops down for proof.
  • Background last (if at all). Most "background" sections exist because the writer felt anxious about jumping to the answer. Cut.
  • One memo, one answer. If you have two recommendations, write two memos.

The pyramid structure

                    [LEAD]
                  The answer.
                One sentence.
                      │
       ┌──────────────┼──────────────┐
       │              │              │
   [ARG 1]        [ARG 2]        [ARG 3]
   Because…       Because…       Because…
       │              │              │
   • evidence      • evidence      • evidence
   • evidence      • evidence      • evidence
   • evidence      • evidence      • evidence

Read the full file on GitHub · 193 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.

  1. 11d ago First seen · 193 lines · 93 tokens per session scan A c133e4cae4a0

Subscribe to this mod's changes

top-down-memo is a skill published in the GitHub repository sruthir28/enterprise-ai-skills (139 stars, last pushed 10d ago), licensed MIT. It adds 93 tokens to every session and 2,274 once invoked, about $0.0005 per session on Opus 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-30.