Agent skill · Code Review & Quality

proofread

Run the proofreading protocol on academic writing — papers or manuscripts. Checks grammar, typos, layout issues, consistency, and academic writing quality. Produces a report without editing files. Make sure to use this skill whenever the user wants surface-level writing errors found — not substantive academic critique. Triggers include: "proofread", "check for typos", "grammar check", "look for errors in my draft", "proofread all", "polish this", "check my writing", "are there any mistakes", "proofread before I send this", or when the user wants a clean-up pass rather than feedback on argum

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codecan modify filesNOASSERTION
Install
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill proofread --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Allowed tools: ReadGrepGlobWriteTaskAskUserQuestion
Path: skills/15-Felpix-Studios-social-science-research/skills/proofread/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 3,244
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Proofread Academic Writing Run the mandatory proofreading protocol on papers or manuscripts. Produces a report of all issues WITHOUT editing any source files. ## Steps 1. **Identify files to review:** - If `$ARGUMENTS` is a specific filename: review that file only - If `$ARGUMENTS` is `all`: review all files in `manuscripts/` and `Quarto/` (if it exists) - If `$ARGUMENTS` is a file in `manuscrip

More from Auto-Empirical-Research-Skills
All skills →
About this skill
What does the proofread skill do?

Run the proofreading protocol on academic writing — papers or manuscripts. Checks grammar, typos, layout issues, consistency, and academic writing quality. Produces a report without editing files. Make sure to use this skill whenever the user wants surface-level writing errors found — not substantive academic critique. Triggers include: "proofread", "check for typos", "grammar check", "look for errors in my draft", "proofread all", "polish this", "check my writing", "are there any mistakes", "proofread before I send this", or when the user wants a clean-up pass rather than feedback on argum

How do I install it?

Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill proofread --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.

Keep going