name

1pager

description

Condense any long document, folder/directory of files, chat, thread, meeting notes, PR description, or report into a strict one-page summary — bullet-first, least verbosity possible — then humanize it and export both a .md and a .docx (opens in Word and Google Docs). Use this whenever the user wants something shortened, tightened, or made into a "1-pager", "one pager", "tl;dr", "exec summary", "BLUF", or "brief", or says the content is too long/verbose/wordy, or asks to "condense", "summarize tightly", "cut this down", "make it fit on a page", or "boil this down". Prefer this skill over a plain summary whenever brevity and a shareable file (.md + .docx) matter.

1-Pager: condense to one page, least verbosity

Why this exists

LLM output trends long, and long output is a tax on every reader: they have to validate text the writer never trimmed. Sending a wall of text to make your own work easier just moves the cost onto someone else — it's rude, and brevity is a form of respect. This skill turns bloated source material into a page someone can read in under two minutes and act on. See README.md for the full problem statement.

The goal is not "a shorter version of everything." It's only what the reader needs to understand or decide, in the fewest words that stay accurate.

Input

The source can be a file path, a directory, pasted text, a link the user already shared, or the current conversation. If it's ambiguous what to condense, ask once; then go.

Directory / project: do not summarize file by file. First build a holistic understanding of what the directory is and what it's for — explore the structure, read the README/docs/configs and enough of the code to grasp the objective, the approach, dependencies, and current state. Then write the 1-pager about the substance (what it does, the option or approach, the decision or recommendation, what's proven vs. open), not an inventory of files. Skip binaries and vendored/build folders (node_modules, .git, dist, build, lockfiles). For a large project, scan breadth-first (entry points, top-level docs, configs) before going deep, and confirm scope once if it's sprawling or mixed. If the user instead wants a separate page per file, do that and export a .md + .docx pair for each.

Workflow

Strip to essentials. Read the source and keep only what a busy decision-maker needs: the point, the decision/ask, the few facts that support it, real risks, concrete next steps. Drop background, hedging, repetition, and anything "nice to know."
Draft the 1-pager in the format below. Bullets over prose. One page is the hard ceiling (see Constraints).
Humanize it. Pass the draft through the humanizer so it doesn't read like AI slop (em-dash overuse, rule-of-three, "delve/leverage/underscore", vague attributions, etc.).
- If the humanizer skill is available, invoke it (via the Skill tool) on the draft and use its result.
- Otherwise, apply the rules in references/humanizer.md yourself.
- Condense first, then humanize — humanizing before is wasted since condensing rewrites everything.
Export both files. Write the final humanized markdown to <name>-1pager.md, then generate the Word/Google-Docs version from that same file:
```
python3 scripts/md_to_docx.py <name>-1pager.md <name>-1pager.docx
```
(scripts/md_to_docx.py is pure standard-library Python — no install needed.) Pick a short <name> from the topic, write both into the user's working directory unless they say otherwise, and tell them where the files are.

Format

ALWAYS open with the bottom line so the reader gets the point before deciding to read on. Keep section headers to the few that fit the content — don't pad.

# <Topic> — 1-Pager

**Bottom line:** <the single most important takeaway, decision, or ask, in one sentence>

## <Section, e.g. Decision / Context / Findings>
- <one fact per bullet, shortest accurate phrasing>
- <sub-points indented two spaces when truly needed>
  - <sub-point>

## Risks / open questions
- <only the ones that change a decision>

## Next steps
- <action — owner — date, where known>

Use only the sections the material warrants. Meeting notes might need Decisions and Action items; a proposal might need Recommendation and Risks. Skip empty sections rather than filling them.

Constraints (this is the whole point)

One page, hard. Aim for ~350 words, ~35 lines max. If it doesn't fit, cut content — never shrink the value by padding, and never spill onto a second page.
Bullets beat paragraphs. Prose is allowed only for the one-sentence bottom line. Everything else is bullets.
No preamble, no filler. No "Here's a summary of…", no restating the title, no generic upbeat closer. Start at the bottom line.
One idea per bullet. If a bullet has a comma-spliced second idea, split or cut it.
Keep it accurate. Condensing must not distort. If something can't be said briefly without becoming wrong, keep it slightly longer rather than misleading.

A good test: could the reader act correctly having read only this page? If yes, you're done. If you're tempted to add "just one more thing," it probably belongs in the source, not the 1-pager.

1-Pager: condense to one page, least verbosity

Why this exists

The goal is not "a shorter version of everything." It's only what the reader needs to understand or decide, in the fewest words that stay accurate.

Input

The source can be a file path, a directory, pasted text, a link the user already shared, or the current conversation. If it's ambiguous what to condense, ask once; then go.

Workflow

Strip to essentials. Read the source and keep only what a busy decision-maker needs: the point, the decision/ask, the few facts that support it, real risks, concrete next steps. Drop background, hedging, repetition, and anything "nice to know."

Draft the 1-pager in the format below. Bullets over prose. One page is the hard ceiling (see Constraints).

Humanize it. Pass the draft through the humanizer so it doesn't read like AI slop (em-dash overuse, rule-of-three, "delve/leverage/underscore", vague attributions, etc.).

If the humanizer skill is available, invoke it (via the Skill tool) on the draft and use its result.
Otherwise, apply the rules in references/humanizer.md yourself.
Condense first, then humanize — humanizing before is wasted since condensing rewrites everything.

Export both files. Write the final humanized markdown to <name>-1pager.md, then generate the Word/Google-Docs version from that same file:

python3 scripts/md_to_docx.py <name>-1pager.md <name>-1pager.docx

(scripts/md_to_docx.py is pure standard-library Python — no install needed.) Pick a short <name> from the topic, write both into the user's working directory unless they say otherwise, and tell them where the files are.

Format

ALWAYS open with the bottom line so the reader gets the point before deciding to read on. Keep section headers to the few that fit the content — don't pad.

# <Topic> — 1-Pager **Bottom line:** <the single most important takeaway, decision, or ask, in one sentence> ## <Section, e.g. Decision / Context / Findings> - <one fact per bullet, shortest accurate phrasing> - <sub-points indented two spaces when truly needed> - <sub-point> ## Risks / open questions - <only the ones that change a decision> ## Next steps - <action — owner — date, where known>

Use only the sections the material warrants. Meeting notes might need Decisions and Action items; a proposal might need Recommendation and Risks. Skip empty sections rather than filling them.

Constraints (this is the whole point)

One page, hard. Aim for ~350 words, ~35 lines max. If it doesn't fit, cut content — never shrink the value by padding, and never spill onto a second page.

Bullets beat paragraphs. Prose is allowed only for the one-sentence bottom line. Everything else is bullets.

No preamble, no filler. No "Here's a summary of…", no restating the title, no generic upbeat closer. Start at the bottom line.

One idea per bullet. If a bullet has a comma-spliced second idea, split or cut it.

Keep it accurate. Condensing must not distort. If something can't be said briefly without becoming wrong, keep it slightly longer rather than misleading.

A good test: could the reader act correctly having read only this page? If yes, you're done. If you're tempted to add "just one more thing," it probably belongs in the source, not the 1-pager.