proofread
Skill8 starsChanged 4 months agoMITView on GitHub
Proofread papers and manuscripts. Checks grammar, typos, layout, consistency, writing quality. Produces report without editing files. Use when finding surface-level errors, not substantive academic critique.
26 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- NilsHellwig/acl-paper-skillstheir own version, first seen Nov 8, 2026
- pedrohcgs/claude-code-my-workflowedited, first seen Nov 7, 2026
- flonat/flonat-researchtheir own version, first seen Nov 3, 2026
- obviousbread/docs-skillstheir own version, first seen Nov 1, 2026
- shuymn/skillstheir own version, first seen Nov 1, 2026
- dewil/claude-toolkittheir own version, first seen Nov 1, 2026
Used with
Projects with it also use humanize, deploy and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
eherrerosjSkillhumanize
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive 'Signs of AI writing' guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Triggers on: 'humanize', 'make this sound human', 'remove AI writing', 'de-AI', 'sound more natural', 'less robotic', 'too AI-sounding', or when reviewing text that reads like AI output.
Also in 3 projects that use this
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
Microsoft AzureSkillverify
End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- pedrohcgs/claude-code-my-workflow★ 1.7k35% same
- maxwell2732/paper-replicate-agent-demo★ 13444% same
- maxwell2732/my-submission-formatting-agent★ 10631% same
- clearsmog/claude-skills★ 235% same
Wrote their own version · 22
- flonat/flonat-research★ 150same name
- sonilo-ai/skills★ 117same name
- tance-mang/chinese-webnovel-skills★ 97same name
- JakobThumm/proofreading★ 38same name
- christopherkenny/skills★ 26same name
- AlessandroCaforio/Academic-Writing★ 17same name
- amondnet/yoonmoon★ 17same name
- dewil/ai-toolkit★ 9same name
- dewil/claude-toolkit★ 9same name
- flowing-abyss/obsidian-vault-skills★ 9same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- data-analysisSkill
- data-finderSkill
- lit-reviewSkill
- new-projectSkill
- quality-gateSkill
- research-setupSkill
- review-paperSkill
- review-rSkill
- revise-paperSkill
- session-logSkill
- validate-bibSkill
- write-paperSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Run the mandatory proofreading protocol on papers or manuscripts.
- Very specific: line 16
If $ARGUMENTS is a specific filename: review that file only
- Very specific: line 17
If $ARGUMENTS is all: review all files in manuscripts/ and Quarto/ (if it exists)
- Very specific: line 18
If $ARGUMENTS is a file in manuscripts/: treat as manuscript (not slides)
- Very specific: line 19
If $ARGUMENTS is empty or ambiguous and multiple files exist, use AskUserQuestion:
- Very specific: line 39
Read ${CLAUDE_PLUGIN_ROOT}/skills/proofread/references/proofreading-protocol.md.
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Proofread Academic Writing
Run the mandatory proofreading protocol on papers or manuscripts. Produces a report of all issues WITHOUT editing any source files.
Steps
- Identify files to review:
- If
$ARGUMENTSis a specific filename: review that file only - If
$ARGUMENTSisall: review all files inmanuscripts/andQuarto/(if it exists) - If
$ARGUMENTSis a file inmanuscripts/: treat as manuscript (not slides) - If
$ARGUMENTSis empty or ambiguous and multiple files exist, use AskUserQuestion:- header: "Files"
- question: "Which files should I proofread?"
- multiSelect: true
- options: list up to 4 found files (label: filename, description: directory and file type). User can select multiple or choose "Other" to specify a path.
- If
- For each file, launch the
proofreaderagent (via Task). It checks grammar, typos, layout issues, consistency, and academic quality — the agent definition owns the full category specifications, so do not restate them here. - Produce a detailed report for each file listing every finding with:
- Location (line number or section heading)
- Current text (what's wrong)
- Proposed fix (what it should be)
- Category and severity
- Save each report to
quality_reports/:- For
.texslide files:quality_reports/FILENAME_report.md - For
.qmdslide files:quality_reports/FILENAME_qmd_report.md - For manuscript files:
quality_reports/FILENAME_proofread.md
- For
- IMPORTANT: Do NOT edit any source files.
Read
${CLAUDE_PLUGIN_ROOT}/skills/proofread/references/proofreading-protocol.md. Only produce the report. Fixes are applied separately after user review. - Present summary to the user:
- Total issues found per file
- Breakdown by category
- Most critical issues highlighted
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.