polish-skills
9 editing & proofreading skills. Trigger: polishing drafts, academic tone, proofreading, translation. Design: style checkers and editing workflows for clear, concise academic English.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill polish --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.
# Editing & Proofreading — 9 Skills Select the skill matching the user's need, then `read` its SKILL.md. | Skill | Description | |-------|-------------| | [academic-tone-guide](./academic-tone-guide/SKILL.md) | Adjust writing tone and register for academic audiences and venues | | [academic-translation-guide](./academic-translation-guide/SKILL.md) | Academic translation, post-editing, and Chinglis
What does the polish-skills skill do?
9 editing & proofreading skills. Trigger: polishing drafts, academic tone, proofreading, translation. Design: style checkers and editing workflows for clear, concise academic English.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill polish --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.