Menu

Individual skill

policy-brief

0upvotes

Writes a concise, evidence-based policy brief - problem, options compared on consistent criteria, and a recommendation - that a decision-maker can act on in minutes. Use when someone asks "write a policy brief", "summarize the evidence and options for this decision", "brief the minister/board/council on X", or needs a one-to-four-page document that turns research into a recommended action. Do NOT use for persuasive opinion pieces - use op-ed-writer instead; for long-form marketing documents, use whitepapers; for condensing an existing long document, use executive-summary.

skills/policy-brief/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Policy Brief

A brief exists to inform one specific choice by one specific decision-maker - not to survey a literature. The costly failure is the brief that is read only as far as its summary and gives the reader nothing actionable there, or that strawmans the rejected options and loses credibility the moment a stakeholder notices. Write so that a busy reader who stops after the first half-page still knows the problem, the recommendation, and why.

## Inputs to collect

1. Who decides, and what decision they face - the single question the brief must answer. If the user cannot name the decision, help them narrow it before writing; "inform them about X" is not a decision.
2. The decision deadline and any political, budget, or legal constraints that rule options in or out.
3. The evidence available: studies, data, prior evaluations. Note what is missing; gaps shape how strongly the brief can recommend.
4. The audience's technical depth. Default: intelligent non-specialist - define every acronym on first use.
5. Length target. Default: one to four pages. Longer than four pages is a report, not a brief.

Label anything assumed rather than supplied.
Back to top