skills/documentation/policyengine-research-lookup-skill/SKILL.md
Find and reference PolicyEngine blog posts, research articles, and published analyses for evidence and proof points. Triggers: "find blog post", "PolicyEngine research", "published analysis", "proof point", "has PolicyEngine written about", "blog post about"
npx skillsauth add policyengine/policyengine-claude policyengine-research-lookupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to find existing PolicyEngine research, blog posts, and published analyses that can serve as evidence, proof points, or references.
PolicyEngine publishes research through:
Government adoption:
policyengine-10-downing-street.md)State coverage:
UK coverage:
Location in codebase:
~/policyengine-app-v2/app/src/data/posts/articles/
Search for topics:
# Find posts mentioning a topic
find ~/policyengine-app-v2/app/src/data/posts/articles/ -name "*.md" | \
xargs grep -l -i "topic" 2>/dev/null
# List all posts
ls ~/policyengine-app-v2/app/src/data/posts/articles/
Post metadata is in:
~/policyengine-app-v2/app/src/data/posts/posts.json
| Topic | File | Use Case |
|-------|------|----------|
| Government adoption | policyengine-10-downing-street.md | Credibility, state capacity |
| State tax models | state-tax-model-beta.md | US state coverage |
| Machine learning | Various | Accuracy, methodology |
| Budget analyses | autumn-budget-*.md | UK policy coverage |
| US tax proposals | *-tax-*.md, *-ctc-*.md | Federal policy coverage |
Each post is markdown with YAML frontmatter:
---
title: "Post Title"
date: "2025-01-15"
authors:
- name: Author Name
tags:
- us
- federal
---
"What's our strongest credibility proof point?" → 10 Downing Street blog post: CTO spent 6 months adapting PolicyEngine for UK government
"Do we cover [state] taxes?" → Search for state name in posts directory; also check policyengine-us-skill
"What did we write about [policy]?" → Search posts directory for policy name or related terms
"Where can I find our methodology for [X]?" → Search for technical posts; check also policyengine-core-skill
When PolicyEngine publishes significant new research:
~/policyengine-app-v2/app/src/data/posts/articles/~/policyengine-app-v2/app/src/data/posts/posts.jsondevelopment
ALWAYS LOAD THIS SKILL for PolicyEngine PR reviews, including when the user invokes $review-program or Codex /review on a PolicyEngine PR. Performs read-only code validation, source-reference checks, regulatory review, optional PDF audit, summary reporting, and optional GitHub comment posting.
development
Use when the user invokes $fix-pr or asks Codex to apply fixes to a PolicyEngine PR based on $review-program findings, GitHub review comments, CI failures, or local review reports.
development
Use when the user invokes $encode-policy-v2 or asks Codex to implement a new PolicyEngine-US state benefit program from official rules. Covers research, source collection, requirement extraction, scoped implementation, tests, validation, and draft PR preparation.
development
Deploying PolicyEngine frontend apps to Vercel - naming, scope, team settings