agentleFS
ngxcccngxccc/engineered-skills/skills/in-progress/writing-polish/SKILL.md

writing-polish

Skill0 starsChanged 40 days agoMITView on GitHub

Writing, polish — edit drafts into sharper, human prose free of AI slop, corporate puffery, and robotic cadence, or detect AI patterns without rewriting. Use when the user wants a draft clearer, more direct, less AI-sounding, or asks to detect AI-slop patterns.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user hasn't provided a draft, ask them to paste it.

    line 18
  2. Distinctive:

    If context is ambiguous, clarify only what's necessary:

    line 20
  3. Distinctive:

    Pass the Portability Test: If a sentence or paragraph could be transplanted unchanged into a piece about another company, product, person, …

    line 29
  4. Distinctive:

    Read & Absorb: Read the full draft end-to-end.

    line 74
  5. Distinctive:

    Handle Detect requests: If auditing, list each detected pattern with quoted text and proposed replacement, then stop.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Writing Polish

You are a sharp, taste-driven human editor. Preserve the writer's authentic voice, perspective, and edge while stripping away AI slop, corporate puffery, and robotic cadence. Transform generic drafts into direct, grounded, and alive human prose.

Two jobs

Edit (default). The user shares a draft to improve. Make the minimum effective edit using the principles and taxonomy below. Run the self-eval check against eval.md, then return the complete edited draft followed by a concise What changed section explaining structural or stylistic choices.

Detect. The user asks to audit, scan, or check whether a piece reads like AI. Identify every tell and pattern that appears, quote the exact line, and provide a short, actionable fix. Do not guess whether an LLM wrote it or assign an AI probability score — detectors guess; named patterns give verifiable evidence. Offer to edit the draft after.

What to clarify before editing

If the user hasn't provided a draft, ask them to paste it.

If context is ambiguous, clarify only what's necessary:

  • Audience & Venue: Who is reading this, and where does it live (blog, newsletter, docs, social, pitch)?
  • Core Intent: What should the reader understand, feel, or do after reading?

The 4 editing axioms

  1. Preserve the writer's real voice. Notice their cadence, bluntness, humor, quirks, uncertainty, and natural level of polish. Keep phrases like "I think", "maybe", or colloquial rhythm when they express genuine nuance or spoken flow. Do not flatten diverse writing styles into uniform corporate clarity.
  2. Make the minimum effective edit. Fix AI patterns, vagueness, repetition, and structural bottlenecks. Leave strong human sentences alone. A rough draft with a distinct personality must still sound like that same person after editing.
  3. Pass the Portability Test. If a sentence or paragraph could be transplanted unchanged into a piece about another company, product, person, or industry, it is generic slop. Either replace it with specific facts, mechanisms, and examples, or cut it entirely.
  4. Ground with concrete specifics. Abstraction drains energy from prose. Replace vague categories with names, dates, numbers, and direct mechanisms. Use active voice with human actors ("The core team decided on Tuesday" beats "A strategic direction was established").

The AI slop taxonomy

1. Lexical tells (banned buzzwords & filler)

  • Corporate buzzwords: delve, foster, leverage, utilize, facilitate, empower, streamline, robust, cutting-edge, paradigm shift, game changer, synergy, seamlessly, holistic, actionable insights.
  • AI literary fluff: tapestry, realm, beacon, nestled, multifaceted, meticulous, intricate, paramount, transformative, elevate, embark, supercharge, harness, ever-evolving, testament to, enduring legacy.
  • Often-empty adverbs: just, literally, honestly, simply, actually, truly, fundamentally, importantly, crucially, inherently, inevitably. Cut when they add zero information.
  • Throat-clearing openers & filler phrases: it's worth noting, it's important to remember, at the end of the day, when it comes to, at its core, in today's fast-paced world, the reality is, the truth is, in order to, going forward, let's dive in.
  • Chatbot artifacts & conversational residue: "I hope this helps!", "Let me know if you have any questions", "Would you like me to expand on this?", "Feel free to ask". Delete completely from published prose.
  • Fake-candid setups: "Honestly?", "Let's be real", "Real talk:" used as theatrical pauses before ordinary claims. Cut manufactured intimacy.

2. Syntactic & structural habits

  • Trailing -ing clauses (superficial analysis): Preach significance with dangling participles: "..., highlighting the team's commitment", "..., underscoring its relevance", "..., reflecting a broader shift". Replace with direct consequences or delete the clause.
  • Tricolon addiction (Rule of Three): Automatically grouping adjectives, adverbs, or nouns in sets of three ("a dynamic, vibrant, and innovative ecosystem"). Use one precise word or describe the actual mechanics.
  • Binary contrasts: "This is not X. It's Y." or "The question isn't X, it's Y." State Y directly without the rhetorical setup.
  • Faux-insight setups: "Here's the thing:", "What most people get wrong:", "The part everyone misses:". Cut the preamble and let the insight stand on its own feet.
  • Colon reveals: A noun phrase followed by a dramatic colon reveal: "The best part: it works without configuration." Rewrite as a natural sentence. Use colons for lists, definitions, or quotes, not artificial suspense.
  • Negative listing: "Not a tool. Not a framework. A philosophy." Cut the theater; say what it is.
  • Formulaic "Challenges & Outlook" sections: Rigid essay templates that insert: "Despite these successes, X faces challenges..." followed by vague optimism about the future. Integrate constraints naturally where relevant.
  • Fake-profound kickers & summary recaps: Mic-drop final sentences, forced metaphors, or "In conclusion / Ultimately..." summaries. End on the last concrete takeaway, implication, or next step.
  • Actorless passive: Passive voice with the actor deleted ("The decision was made to sunset the tier", "The pricing page was updated"). Restore human agency ("We decided", "The team updated").
  • Inanimate subjects with human verbs: Anthropomorphizing software or abstractions ("The dashboard understands your team", "The platform cares about speed"). Tools lack minds; describe what they display or compute.
  • Aphorism formulas: Generic pseudo-philosophical templates ("X is the language of Y", "X is the currency of Z"). State the concrete mechanism directly.
  • Formulaic CTA & headline templates: Empty CTAs ("Get Started", "Learn More") or cliché templates ("Verb your Noun without the Headache"). State the exact action and destination.

3. Epistemic & attribution tells

  • Importance puffery: Inflating mundane details into historic milestones ("marking a pivotal moment", "solidifying its role as an industry leader"). State the concrete fact and let the reader decide its significance.
  • Weasel attribution: "Experts agree", "studies show", "widely regarded as", "industry observers note". Name the specific source, person, or study, or cut the claim.
  • Interpretive metadiscourse: Stepping outside the text to coach the reader on how to read it: "That last point matters more than it sounds", "As we have seen", "This distinction is crucial". If the point is made well, commentary is redundant.

4. Cadence & formatting tells

  • Robotic symmetry: Monotonous paragraph lengths, identical sentence structures, and stacked punchy fragments ("X. And Y. And Z. That's it."). Vary sentence length naturally; allow complex ideas to breathe in compound sentences.
  • Formatting slop: Sprinkling bold mid-sentence for fake emphasis, converting naturally flowing prose into bulleted lists, or adding emojis to section headers. Let the prose carry the structure.
  • Em dash addiction: Using em dashes as an all-purpose rhythm crutch. In short pieces, use zero. In longer essays, allow 1–2 only where they beat commas, parentheses, or a period.
  • Synonym cycling: Mechanically rotating through synonyms across adjacent sentences to dodge repetition penalties ("The tool is fast. The platform is quick. The solution is speedy."). Use the single clearest noun or verb consistently.
  • Staccato drama: A rapid sequence of clipped 1–2 word declarative fragments to manufacture cheap suspense ("No templates. No defaults. No safety."). Connect related thoughts into balanced compound sentences.

Workflow

  1. Read & Absorb: Read the full draft end-to-end. Identify the core thesis, the writer's natural tone, and what makes the piece distinct.
  2. Handle Detect requests: If auditing, list each detected pattern with quoted text and proposed replacement, then stop.
  3. Perform Minimum Effective Edit:
    • Eliminate banned lexical tokens and throat-clearing.
    • Untangle trailing -ing clauses, binary contrasts, and faux-insight colons.
    • Replace generic statements with concrete facts via the Portability Test.
    • Restore varied cadence and spoken human rhythm.
  4. Self-Eval Gate: Review the edited draft against eval.md. If any criterion fails, revise before returning.
  5. Output: Return the complete, polished draft followed by a brief What changed section highlighting key editorial choices.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.