policy-brief
Skill3 starsChanged 40 days agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- baobab-tech/researcher-harnesstheir own version, first seen Sep 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- baobab-tech/researcher-harness★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- academic-essaySkill
- citation-trackerSkill
- fact-checkerSkill
- literature-reviewSkill
- systematic-reviewSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Compress the background: Only what is needed to understand the problem - typically one to two paragraphs.
- Distinctive: line 56
Do not bury the recommendation at the end.
- Distinctive: line 57
Do not present only supporting evidence.
- Distinctive: line 58
Do not mix evidence with values silently.
- Distinctive: line 59
Do not compare options on shifting criteria - praising one option's cost and another's speed hides the real trade-off.
- Distinctive: line 60
Do not exceed four pages or leave jargon and acronyms unexplained.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- 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.
- The decision deadline and any political, budget, or legal constraints that rule options in or out.
- The evidence available: studies, data, prior evaluations. Note what is missing; gaps shape how strongly the brief can recommend.
- The audience's technical depth. Default: intelligent non-specialist - define every acronym on first use.
- Length target. Default: one to four pages. Longer than four pages is a report, not a brief.
Label anything assumed rather than supplied.
Operating procedure
Order matters: options cannot be compared until criteria are fixed, and the executive summary is written last even though it appears first.
- Fix the decision and criteria. State the choice in one sentence. Choose 3-5 comparison criteria - effectiveness, cost, equity, feasibility, time-to-impact are the standard set - and hold them constant across every option.
- Draft the problem statement. What is wrong, who is affected, why now, and the cost of inaction. Quantify wherever possible; a problem without a number invites indefinite delay.
- Compress the background. Only what is needed to understand the problem - typically one to two paragraphs.
- Assemble the evidence. Cite credible primary sources; note the strength and limitation of each. Distinguish strong causal evidence (randomized or well-identified quasi-experimental) from correlation and from expert opinion, and say which is which. Present evidence on all sides, including findings inconvenient to the eventual recommendation.
- Build 2-4 realistic options, always including the status quo. For each: how it works, expected impact, cost, feasibility, key trade-offs - scored against the fixed criteria in a comparison table. Do not strawman the options you reject; state each option's best case fairly.
- Recommend and condition. Name the preferred option, the reasoning against the criteria, the assumptions it rests on, and the conditions under which the recommendation would change.
- Sketch implementation. Concrete first steps, owners, and timeline - a recommendation without a first step is a suggestion.
- Write the executive summary last. Problem plus recommendation in 3-4 sentences that stand alone. Many readers read nothing else.
Options table template
Criteria (weight) | Option A: [FILL] | Option B: [FILL] | Status quo
Effectiveness | [FILL] | [FILL] | [FILL]
Cost (annual) | $[FILL] | $[FILL] | $[FILL]
Equity impact | [FILL] | [FILL] | [FILL]
Feasibility | High/Med/Low | High/Med/Low | High/Med/Low
Time to impact | [FILL] months | [FILL] months | n/a
Key trade-off | [FILL] | [FILL] | cost of inaction: [FILL]Bad summary: "This brief examines several approaches to school absenteeism and discusses their relative merits." Good summary: "Chronic absenteeism has doubled to 28% of students since the baseline year. Of three options assessed, targeted mentoring is recommended: evaluations show a 4-6 percentage-point reduction at roughly $1,500 per student, versus weak evidence for automated messaging alone. Begin with a two-school pilot next term."
Deliverable
Produce a one-to-four-page brief containing: title and standalone executive summary; quantified problem statement; minimal background; evidence section with sources graded by strength; 2-4 options scored in a consistent comparison table; a conditioned recommendation; and implementation first steps with owners and timeline.
Do NOT
- Do not bury the recommendation at the end. Lead with the bottom line (BLUF); the structure of a brief is conclusion-first, evidence-after.
- Do not present only supporting evidence. Omitting the strongest counter-evidence is the fastest way to lose a skeptical reader - and decision-makers employ skeptical staff.
- Do not mix evidence with values silently. Separate what is (evidence) from what should be (normative choices) and label the normative ones.
- Do not compare options on shifting criteria - praising one option's cost and another's speed hides the real trade-off.
- Do not exceed four pages or leave jargon and acronyms unexplained.
Quality bar
Before shipping: the executive summary stands alone and states the recommendation; every factual claim has a findable citation; evidence strength is graded, not asserted; all options - including status quo - are scored on identical criteria; assumptions and change-conditions are explicit; a reader can identify the first implementation step and its owner.
Escalation
A brief informs a decision; it is not legal advice, and options touching statute, regulation, or liability need counsel review before adoption. For verifying a load-bearing statistic before it anchors the problem statement, use fact-checker. For deep sourcing on an unfamiliar topic before drafting, run deep-research first.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

