Skills · Work
Turn a long document into the decision it's asking for
Paste the report, the deck, the forty-page proposal. Get the bit you have to decide.
--- name: decision-brief description: Reduces a long report, deck or proposal to the decisions it asks the reader to make, the evidence for each, and what it leaves out. Use when the user pastes a long document and asks what to do. --- # What this document is asking for Read the document as the person who has to decide, not as a summariser. ## Steps 1. Find the asks. Anything the document wants a reader to approve, fund, sign, choose or stop. Most documents bury one or two under a lot of context. 2. For each ask, write: **The decision.** In one line, as a question with real options, not "consider the strategy". **What the document says for it.** The specific evidence, with the section or page it came from. **What it doesn't say.** The number, risk or cost a reader would need and can't find here. 3. Then, and only then, a three-line summary of everything else in the document, for context. 4. If the document asks for nothing and is purely informational, say that in the first line. It's the most useful thing you can tell someone about a forty-page deck. ## Rules - Every claim you repeat gets a pointer back to where it came from. If you can't point at it, don't write it. - Never fill a gap from general knowledge. A missing number is a finding, not a hole to plug. - Don't take the document's word for its own conclusions. If the summary claims a 30% saving and the body shows 12%, say both. - Leave the recommendation to the reader unless they ask for one. ## Output One block per decision, in the order the reader has to make them. Context last, three lines. No executive-summary voice.
Where it goes
Claude Code: save the file as ~/.claude/skills/decision-brief/SKILL.md. The folder name has to match, and a new session picks it up.
claude.ai: turn on code execution in Settings → Capabilities, then go to Customize → Skills and upload the zip. The zip already has the folder at its root, which is what that upload wants.
When it fires
- Someone sent you a forty-page deck before a meeting
- You say "what does this actually want me to do"
- You have to approve something you haven't read
- A proposal arrives and a decision is due
Claude decides by reading one line, the description at the top of the file. This one says: Reduces a long report, deck or proposal to the decisions it asks the reader to make, the evidence for each, and what it leaves out. Use when the user pastes a long document and asks what to do.
The instruction that does the work
Pointing at the source for every claim. A summary that floats free of the document is impossible to check, and once one invented figure is in there the whole thing is worthless. Making every line carry its section reference means you can spot-check three of them in a minute.
Why "what it doesn't say" is its own section
The gap is usually the answer. A proposal with no cost line, or a report with no comparison to last year, has told you something. Summarisers smooth those gaps over because they're reading for what's there.
Install one of these next
Turn my meeting notes into a memo
Paste the mess you typed during the call. Get something you can send.
- You paste notes from a call
- You say "write this up"
- You drop in a transcript
Write my weekly update from the week's notes
Paste the week's scraps. Get the update your manager reads in ten seconds.
- You paste a week of notes
- You say "write my weekly update"
- It's Friday and the report is due
- Someone asks what you've been doing