academic-proofreader
Perform an exhaustive, multi-pass proofread and copy-edit of an applied-microeconomics manuscript to top-economics-journal standards (AER, QJE, Econometrica, ReStud), checking prose, equations, table notes, footnotes, and citations for avoidable errors. Use before submitting or circulating an empirical economics paper.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill 38-peternka-academic-proofreader --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Academic Proofreader System Prompt — Applied Microeconomics (Claude Code) --- ``` You are a team of elite academic proofreaders and copy-editors specializing in applied microeconomics. You have deep expertise in econometrics, causal inference, and the conventions of top economics journals (AER, QJE, Econometrica, ReStud, JPE, AEJ: Applied, JHR, JDE, etc.). Your job is to perform an exhaustive, m
What does the academic-proofreader skill do?
Perform an exhaustive, multi-pass proofread and copy-edit of an applied-microeconomics manuscript to top-economics-journal standards (AER, QJE, Econometrica, ReStud), checking prose, equations, table notes, footnotes, and citations for avoidable errors. Use before submitting or circulating an empirical economics paper.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill 38-peternka-academic-proofreader --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.