proofread

Detect AI writing tropes and report concrete rewrite suggestions.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/shuymn/skills --skill proofread-shuymn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proofread
Source: https://github.com/shuymn/skills/tree/main/skills/proofread
Command: npx skills add https://github.com/shuymn/skills --skill proofread-shuymn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you spot writing that sounds mechanical, generic, or overly AI-generated, then turns those observations into practical rewrite guidance. It is especially useful when prose needs to feel natural and credible in docs, READMEs, blog posts, commit messages, PR descriptions, or other public-facing text.

Core Features & Use Cases

  • Trope Detection: Scans for recurring AI-writing patterns such as filler phrasing, overused structures, and inflated tone.
  • Context-Aware Judgment: Weighs the purpose and length of the text so it can ignore harmless style choices and focus on real problems.
  • Concrete Suggestions: Reports specific findings with short quotes, line references when available, and rewrite ideas that preserve meaning.
  • Use Case: A team can run this Skill on a draft README before release to catch phrases that sound polished but not human.

Quick Start

Paste the text you want reviewed or point the Skill at a file and ask it to check for AI writing tropes and suggest more natural alternatives.

Frequently Asked Questions about proofread

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect AI writing tropes in my documentation?

AI writing tropes are detected by scanning text for filler phrasing, overused structures, and inflated tone. Context-aware judgment filters out harmless style choices, focusing on mechanical prose patterns and reporting concrete rewrite suggestions with quoted passages and line references.

What is the best way to make README prose sound naturally human?

The best way to make README prose sound naturally human is to scan for AI-generated tropes and apply context-aware judgment based on text length and purpose. This identifies mechanical prose patterns and provides line-aware rewrites with quoted passages to preserve meaning.

Can I check commit messages and PR descriptions for mechanical prose patterns?

Yes, you can check commit messages and PR descriptions for mechanical prose patterns. The scanning process applies context-sensitive judgment to these formats, identifying AI writing tropes and providing concise findings with quoted passages and line-aware rewrites.

Does proofreading for AI writing tropes ignore harmless style choices?

Yes, proofreading for AI writing tropes ignores harmless style choices by applying context-aware judgment. It weighs the text's purpose and length to filter acceptable variations, focusing only on detecting filler phrasing, overused structures, and inflated tone that sound mechanical.

How do I get concrete rewrite suggestions for overly polished blog posts?

You get concrete rewrite suggestions for overly polished blog posts by scanning for AI writing tropes. The process reports specific findings with short quotes, line references when available, and rewrite ideas that preserve meaning while restoring a natural tone.

When should I not use an AI writing trope detector?

You should not use an AI writing trope detector when your text contains purely structural data or does not need to read as human-written. The mechanism targets prose like documentation, READMEs, and PR descriptions where natural tone and credibility are required.