Today's Agent Skill: Turn Any Document Into a Decision Log
What It Does
Long documents pile up unread — contracts, RFPs, policy updates, board decks — and the thing you actually need from them is buried: what did someone decide, and what changes because of it. Reading 40 pages to extract four decisions is the least leveraged hour in your week. This skill flips it: the agent reads, and you get the decision log.
How It Works
The agent ingests a document and scans specifically for decision language — commitments, approvals, rejections, deadlines, and conditional clauses — rather than summarizing evenly. Each hit gets extracted with its source location, the party who owns it, and any trigger condition attached. The output is a table you can act on, not prose you have to re-read.
How to Deploy It
Drop the SKILL.md below into your agent's skills directory (`~/.claude/skills/decision-log-extractor/SKILL.md` for Claude Code, or the equivalent skills path for your runtime) and it activates on the trigger phrases. Point it at a file path or paste the document text and it runs unprompted.
SKILL.md — Ready to Deploy
# Decision Log Extractor
## Description
Extracts every decision, commitment, and conditional obligation from a long document into a structured decision log. Built for contracts, meeting minutes, RFPs, policy updates, and board materials where the actionable content is a small fraction of the total text.
## Trigger
Activates on: `decision log`, `what was decided`, `pull the decisions out of this`, `what do I owe`, `extract commitments`, `what changes because of this doc`. Also activates when the user supplies a document over ~1,500 words and asks any variant of "what do I need to know" — treat that as a decision-log request.
## Input
- A file path, pasted text, or URL to a document
- Optional: the user's own role or party name, to flag which obligations are theirs
## Steps
1. Read the full document. Do not summarize on the first pass — index it.
2. Scan for decision markers: `shall`, `will`, `agrees to`, `approved`, `rejected`, `deferred`, `by [date]`, `subject to`, `unless`, `in the event that`, `no later than`.
3. For each hit, capture four fields: the decision itself, the owning party, the deadline or trigger condition, and the source location (page, section, or line).
4. SepCopy the full SKILL.md and drop it into your agent's skills directory to activate this skill.