policyengine-writing
PolicyEngine writing style for any public-facing prose — blog posts, research reports, documentation, PR descriptions, social copy, READMEs. Enforces active voice, quantitative precision, sentence-case headings, and the analytical neutrality a nonpartisan 501(c)(3) requires: no policy prescriptions dressed as findings, no speculative claims, no one-sided framing, and explained counterintuitive results. Triggers: "write a blog post", "PolicyEngine blog", "policy analysis writeup", "PR description", "research report", "documentation", "social post", "changelog prose", "sounds like advocacy", "is this neutral", "sentence case", "writing style", "make it quantitative".
PolicyEngine · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add PolicyEngine/policyengine-claude --skill policyengine-writing技能说明
name: policyengine-writing description: | PolicyEngine writing style for any public-facing prose — blog posts, research reports, documentation, PR descriptions, social copy, READMEs. Enforces active voice, quantitative precision, sentence-case headings, and the analytical neutrality a nonpartisan 501(c)(3) requires: no policy prescriptions dressed as findings, no speculative claims, no one-sided framing, and explained counterintuitive results. Triggers: "write a blog post", "PolicyEngine blog", "policy analysis writeup", "PR description", "research report", "documentation", "social post", "changelog prose", "sounds like advocacy", "is this neutral", "sentence case", "writing style", "make it quantitative". metadata: category: process
PolicyEngine Writing Skill
Use this skill when writing blog posts, documentation, PR descriptions, research reports, or any public-facing PolicyEngine content.
When to Use This Skill
- Writing blog posts about policy analysis
- Creating PR descriptions
- Drafting documentation
- Writing research reports
- Composing social media posts
- Creating newsletters
- Writing README files
Core Principles
PolicyEngine's writing emphasizes clarity, precision, and objectivity.
- Active voice - Use an actor and a real verb throughout
- Direct and quantitative - Use specific numbers, avoid vague adjectives/adverbs
- Sentence case - Use sentence case for headings, not title case
- Neutral tone - Describe what policies do, not whether they're good or bad
- Precise language - Choose exact verbs over vague modifiers
Sentences
These rules apply to every register: blog posts, docs, READMEs, PR descriptions, social copy, and reports back to the team.
- Name the actor and action. Put the person, program, or institution in the subject and a real verb in the predicate. Replace be-verb identities ("the chart is explorable") with actions ("filter the chart by state") wherever an actor can own the verb.
- Describe the action, not the scenario label. Test-case names and table headings are not prose. Write what someone does, what the program or model does next, and who experiences the result.
- No glosses and no argument pointers. Cut sentences whose subject is the text's own word ("X means…", "in other words") or the text's own reasoning ("this is why", "the point is"). Give a definition an agent and a condition where they help explain the subject. Keep formal definitions and equations. Remove narrated honesty, review credentials, and clauses about the writer's care; retain the facts those clauses manage.
- Introduce a name or role the first time it appears, then keep to it. Expand unfamiliar acronyms on first use. Introduce terms with the context the audience needs. Use consistent names for the roles the subject needs.
- Mechanism claims come from the source. Before writing what a program or model does, open the statute, parameter file, or code that does it, and write what you read.
- No "X, not Y" and no "instead of Y" unless Y is real information. State the fact. A real limit stays as its own plain sentence.
- Name it or cut it. A sentence that alludes to something the reader cannot see ("several programs interact here") carries nothing. Name the programs or delete the sentence.
- One thought per sentence, varied rhythm. Split any sentence a reader would read twice. Join clauses that share one thought. Vary sentence length within the paragraph; do not turn connected prose into a string of short declarations.
- Finished work introduces itself fresh. A published post, paper, or doc describes what the analysis shows now. It does not narrate drafts, review rounds, or fixed bugs. Keep substantive assumptions, limitations, sensitivity ranges, and uncertainty beside the claims they qualify. Preserve forecast-registration dates and evidence wherever readers need them to assess a forecast; keep full registration and review trails in supporting records. Corrections, changelogs, PR descriptions, and release notes take history as their subject: state what changed and the new numbers, and never hide a correction to a published claim.
- One flagged sentence means a full pass. When a reviewer strikes one instance of any of these, reread the whole document for the same pattern before replying.
Active Voice
Active voice makes writing clearer and more direct.
✅ Correct (Active):
Harris proposes expanding the Earned Income Tax Credit
The reform reduces poverty by 3.2%
PolicyEngine projects higher costs than other organizations
We estimate the ten-year costs
The bill lowers the state's top income tax rate
Montana raises the EITC from 10% to 20%
❌ Wrong (Passive):
The Earned Income Tax Credit is proposed to be expanded by Harris
Poverty is reduced by 3.2% by the reform
Higher costs are projected by PolicyEngine
The ten-year costs are estimated
The state's top income tax rate is lowered by the bill
The EITC is raised from 10% to 20% by Montana
Quantitative and Precise
Replace vague modifiers with specific numbers and measurements.
✅ Correct (Quantitative):
Costs the state $245 million
Benefits 77% of Montana residents
Lowers the Supplemental Poverty Measure by 0.8%
Raises net income by $252 in 2026
The reform affects 14.3 million households
Hours worked falls by 0.27%, or 411,000 full-time equivalent jobs
The top decile receives an average benefit of $1,033
PolicyEngine projects costs 40% higher than the Tax Foundation
❌ Wrong (Vague adjectives/adverbs):
Significantly costs the state
Benefits most Montana residents
Greatly lowers poverty
Substantially raises net income
The reform affects many households
Hours worked falls considerably
High earners receive large benefits
PolicyEngine projects much higher costs
Sentence Case for Headings
Use sentence case (capitalize only the first word and proper nouns) for all headings
阅读完整来源 ↗