User-Facing Text Cleanup
guillaumemeyer/watermarks-remover
Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.
Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis.
Install Proofreading
$ npx skills add seb1n/awesome-ai-agent-skills --skill proofreading -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills proofreading --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/writing-and-content/proofreading .claude/skills/proofreading && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "proofreading" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/proofreading into .claude/skills/proofreading/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "proofreading", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/proofreadingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add seb1n/awesome-ai-agent-skills --skill proofreading -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills proofreading --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/writing-and-content/proofreading .agents/skills/proofreading && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "proofreading" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/proofreading into .agents/skills/proofreading/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "proofreading", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seb1n/awesome-ai-agent-skills --skill proofreading -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills proofreading --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/writing-and-content/proofreading .cursor/skills/proofreading && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "proofreading" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/proofreading into .cursor/skills/proofreading/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "proofreading", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/seb1n/awesome-ai-agent-skills.git --path writing-and-content/proofreading--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add seb1n/awesome-ai-agent-skills --skill proofreading -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills proofreading --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/writing-and-content/proofreading .gemini/skills/proofreading && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "proofreading" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/proofreading into .gemini/skills/proofreading/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "proofreading", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install seb1n/awesome-ai-agent-skills proofreadingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add seb1n/awesome-ai-agent-skills --skill proofreading -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/writing-and-content/proofreading .github/skills/proofreading && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "proofreading" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/proofreading into .github/skills/proofreading/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "proofreading", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seb1n/awesome-ai-agent-skills --skill proofreading -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills proofreading --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/writing-and-content/proofreading .opencode/skills/proofreading && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "proofreading" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/writing-and-content/proofreading into .opencode/skills/proofreading/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "proofreading", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
proofreading- GitHub stars
- 206
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,183 words
- Files
- 1
- Skills in repo
- 92
- Repo updated
- First seen
- Licence
- MIT
At a glance
Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis.
- Works in 6 steps: Grammar Check → Spelling and Word Choice → Punctuation and Mechanics → …
- The user requests proofreading
- SKILL.md covers Workflow, Usage, Examples and Best Practices, plus 1 more section
- Calls npm
What it does
Proofreading is an agent skill from seb1n/awesome-ai-agent-skills. Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis. Use when the user requests proofreading or provides relevant inputs for this workflow.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Copy editing and proofreading. The repository describes itself as: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.
When your agent uses it
- The user requests proofreading
- Provides relevant inputs for this workflow
Example prompts
- “/proofreading”
Requirements
- Node.js
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Grammar Check
- Spelling and Word Choice
- Punctuation and Mechanics
- Style and Consistency
- Clarity and Readability
- Tone Analysis and Final Review
What it can do on your machine
Read from SKILL.md and the folder at commit 75865a5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Proofreading loads about 2.4k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 1,183 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 1,183 words, ~2,358 tokens.
Download SKILL.mdSave it as
.claude/skills/proofreading/SKILL.md (or your agent's skills folder).- name
- proofreading
- description
- Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis. Use when the user requests proofreading or provides relevant inputs for this workflow.
- license
- MIT
- metadata.author
- awesome-ai-agent-skills
- metadata.version
- 1.0.0
Proofreading
This skill enables an AI agent to systematically proofread text, catching errors in grammar, spelling, punctuation, style, and consistency. The agent applies a structured multi-pass review process, supports standard style guides (AP, Chicago, APA, or custom house styles), and provides readability scoring alongside tone analysis. Output includes both the corrected text and an annotated summary of every change made.
Workflow
Grammar Check Scan the text for grammatical errors including subject-verb agreement, incorrect tense usage, dangling modifiers, sentence fragments, run-on sentences, and misplaced clauses. Fix each error and record the original phrasing alongside the correction. Pay special attention to complex sentences where multiple clauses may introduce ambiguity.
Spelling and Word Choice Identify misspelled words, commonly confused homophones (e.g., "affect" vs. "effect," "their" vs. "there"), and incorrect word forms. Verify proper nouns and domain-specific terminology against the provided context or glossary. Flag any words that are spelled correctly but likely used in the wrong context.
Punctuation and Mechanics Review comma usage, semicolons, colons, em dashes, en dashes, hyphens, quotation marks, and apostrophes. Apply the rules of the specified style guide — for example, the Oxford comma for Chicago style but not for AP style. Correct misuse of ellipses, parentheses, and bracket nesting.
Style and Consistency Enforce consistent formatting throughout the document: heading capitalization (title case vs. sentence case), number formatting (numerals vs. spelled-out), abbreviation usage (define on first use), and list punctuation. Check for passive voice overuse and recommend active alternatives where the meaning would be clearer. Ensure consistent use of terminology — if "user interface" appears in one place and "UI" elsewhere, unify them.
Clarity and Readability Evaluate sentence length, paragraph structure, and overall readability. Flag sentences longer than 30 words for possible splitting. Identify jargon or overly complex vocabulary that could be simplified without losing precision. Calculate a readability score (Flesch-Kincaid or equivalent) and report it. Suggest structural improvements such as adding transition sentences or breaking up dense paragraphs.
Tone Analysis and Final Review Assess the overall tone (formal, conversational, academic, persuasive) and verify it matches the user's stated intent. Flag any jarring tonal shifts — for instance, a casual phrase in an otherwise formal report. Perform a final read-through to ensure all corrections integrate smoothly and no new errors were introduced during editing.
Usage
Provide the text to proofread along with any relevant context. Optionally specify:
- Style guide — AP, Chicago, APA, MLA, or a custom style reference
- Audience — academic, professional, general public, technical
- Tone — formal, informal, conversational, neutral
- Focus areas — grammar only, style only, full proofread
- Output format — corrected text only, corrected text with tracked changes, or annotated list of changes
Example prompt: "Proofread the following research abstract for APA style. Flag any passive voice usage and provide a readability score."
Examples
Example 1: Proofreading an Academic Paragraph
Input:
The study's participants was selected from a pool of undergraduate students, who where enrolled in a introductory psychology course. Data was collected over a 6 week period and analysed using a mix-methods approach. The researchers founded that participants that recieved the intervention showed signficant improvement, however those in the control group did not.
Corrected Output:
The study's participants were selected from a pool of undergraduate students who were enrolled in an introductory psychology course. Data were collected over a six-week period and analyzed using a mixed-methods approach. The researchers found that participants who received the intervention showed significant improvement; however, those in the control group did not.
Changes Made:
| # | Original | Correction | Reason |
|---|---|---|---|
| 1 | "participants was" | "participants were" | Subject-verb agreement |
| 2 | "who where" | "who were" | Homophone error |
| 3 | "a introductory" | "an introductory" | Article agreement (vowel sound) |
| 4 | "Data was" | "Data were" | "Data" is plural in academic writing (APA) |
| 5 | "6 week" | "six-week" | Spell out numbers under 10; hyphenate compound modifier |
| 6 | "analysed" | "analyzed" | American English spelling (APA default) |
| 7 | "mix-methods" | "mixed-methods" | Incorrect adjective form |
| 8 | "founded" | "found" | Wrong verb form |
| 9 | "participants that" | "participants who" | Use "who" for people |
| 10 | "recieved" | "received" | Spelling error |
| 11 | "signficant" | "significant" | Spelling error |
| 12 | "improvement, however" | "improvement; however," | Semicolon before conjunctive adverb |
Readability: Flesch-Kincaid Grade Level 14.2 (appropriate for academic audience).
Show full SKILL.md (503 more words)Show less
Example 2: Proofreading Technical Documentation
Input:
Configration
To setup the SDK, first install the dependancies using npm. Run
npm install @acme/sdkin your terminal. After installing you need to initialise the client by callingAcmeClient()constructor and passing you're API key. Make sure the api key is stored securly and is not hard-coded in your source code, we reccommend using environment variables.
Corrected Output:
Configuration
To set up the SDK, first install the dependencies using npm. Run
npm install @acme/sdkin your terminal. After installing, you need to initialize the client by calling theAcmeClient()constructor and passing your API key. Make sure the API key is stored securely and is not hard-coded in your source code. We recommend using environment variables.
Changes Made:
| # | Original | Correction | Reason |
|---|---|---|---|
| 1 | "Configration" | "Configuration" | Spelling error in heading |
| 2 | "To setup" | "To set up" | "Set up" is a verb phrase; "setup" is a noun/adjective |
| 3 | "dependancies" | "dependencies" | Spelling error |
| 4 | "After installing you" | "After installing, you" | Missing comma after introductory phrase |
| 5 | "initialise" | "initialize" | American English spelling for consistency |
| 6 | "calling AcmeClient()" | "calling the AcmeClient()" | Missing article |
| 7 | "you're" | "your" | Homophone error ("you're" = "you are") |
| 8 | "api key" | "API key" | Acronym should be capitalized |
| 9 | "securly" | "securely" | Spelling error |
| 10 | "source code, we" | "source code. We" | Comma splice — use a period to separate independent clauses |
| 11 | "reccommend" | "recommend" | Spelling error |
Best Practices
- Use a multi-pass approach. Never try to catch all error types in a single read. Separate passes for grammar, spelling, punctuation, and style yield more thorough results.
- Preserve the author's voice. Correct errors without rewriting the text in a different style. The goal is to polish, not to replace the author's expression.
- Show your work. Always provide an annotated list of changes so the author can review, learn from corrections, and accept or reject individual edits.
- Apply the correct style guide consistently. AP and Chicago have different rules for commas, numbers, and capitalization. Confirm which guide applies before starting.
- Flag subjective suggestions separately. Distinguish between objective errors (misspellings, grammar mistakes) and subjective suggestions (word choice, sentence restructuring) so the author can prioritize.
- Consider the audience. A technical document for developers can tolerate jargon that would be inappropriate in a public-facing blog post. Calibrate simplification suggestions accordingly.
Edge Cases
- Intentional style deviations: Creative writing, dialogue, and marketing copy may intentionally break grammar rules for effect. Ask for clarification before "correcting" sentence fragments or colloquialisms that appear purposeful.
- Mixed languages: Documents containing code snippets, foreign phrases, or brand names in another language should have those sections excluded from spelling checks.
- Regional English variants: Distinguish between American, British, Australian, and other English variants. "Colour" is not a misspelling in British English; "analyze" is not a misspelling in American English.
- Highly technical or domain-specific text: Medical, legal, and scientific texts contain specialized terminology that may trigger false positives. Cross-reference flagged terms against domain glossaries before marking them as errors.
- Very short text: For single sentences or headlines, readability scoring may not be meaningful. Focus on correctness and clarity instead.
© seb1n, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in writing-and-content/proofreading of seb1n/awesome-ai-agent-skills.
Open the folder on GitHubat commit 75865a5
Compare with similar skills
Proofreading next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Proofreading this skillseb1n/awesome-ai-agent-skills | 206 | — | ~2.4k | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 23k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode | 7.3k | 3 repos | ~3k | Automated safety check: Pass | MIT | |
| Chinese Text Humanizerop7418/Humanizer-zh | 19k | — | ~2k | Automated safety check: Pass | MIT | |
| Baoyu TranslateJimLiu/baoyu-skills | 26k | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Story Multi-Perspective Review
zenstory-ai/oh-story-claudecode
Reviews Chinese web-novel text with several reviewer agents in parallel, falling back to a single-agent pass, and reports structure, character, prose and setting problems with fixes.
Chinese Text Humanizer
op7418/Humanizer-zh
Edits Chinese articles, comments and documents to remove filler, repetition and template phrasing while keeping the facts, the level of certainty and the author's voice.
Baoyu Translate
JimLiu/baoyu-skills
Translates articles and files in quick, normal or refined mode, with a custom glossary, saved preferences and a review-and-polish workflow for publication quality.
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
Defensive Writing Editor
lennney/stop-that-shit
Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.
More from seb1n/awesome-ai-agent-skills
All 92 skills in this repoAgent Red Teaming
seb1n/awesome-ai-agent-skills
Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.
Eu AI Act Readiness
seb1n/awesome-ai-agent-skills
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…
Human In The Loop
seb1n/awesome-ai-agent-skills
Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.
MCP Server Building
seb1n/awesome-ai-agent-skills
Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.
PDF Processing
seb1n/awesome-ai-agent-skills
Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.
Skill Supply Chain Audit
seb1n/awesome-ai-agent-skills
Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.
Related
Categories
Questions about Proofreading
What does Proofreading do?
Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis. Proofreading is an agent skill from seb1n/awesome-ai-agent-skills. Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis.
When should I use Proofreading?
Proofreading fits situations like: the user requests proofreading; provides relevant inputs for this workflow.
How do I install Proofreading in Claude Code?
Run `npx skills add seb1n/awesome-ai-agent-skills --skill proofreading -a claude-code`. Or copy the skill folder (writing-and-content/proofreading in seb1n/awesome-ai-agent-skills) into .claude/skills/proofreading in your project. Claude Code loads it when a task matches its description.
How do I install Proofreading in Codex?
Run `npx skills add seb1n/awesome-ai-agent-skills --skill proofreading -a codex`. Or copy the skill folder (writing-and-content/proofreading in seb1n/awesome-ai-agent-skills) into .agents/skills/proofreading in your project. Codex loads it when a task matches its description.
Can I use Proofreading in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seb1n/awesome-ai-agent-skills --skill proofreading -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/proofreading, .gemini/skills/proofreading, .github/skills/proofreading and .opencode/skills/proofreading in your project.
What does Proofreading need to run?
Going by SKILL.md and its folder, Proofreading needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Proofreading access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Proofreading safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Proofreading use?
Proofreading is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Proofreading use?
About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Proofreading?
Skills that share tags, products or a category with Proofreading: User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 23k stars), Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.3k stars), Chinese Text Humanizer (op7418/Humanizer-zh, 19k stars) and Baoyu Translate (JimLiu/baoyu-skills, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Proofreading?
seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 92 skills in this directory. The repository was last updated on August 9, 2026.
Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.