Cut AI tells from text you write or edit for a human reader (commit messages, PR titles and bodies, docs, code comments, replies). Apply before committing, posting, or sending; leave prose you didn't touch alone.
SkillScore91Maintained
Automatic
◆Writing & Editing pack
Last verified 10/10/2026
What it changes
Passed 20 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill91%
Checks it passed that the model alone missed
The output uses sentence case for headings.
The output uses sentence case for all section headings.
The output contains no curly quotes or curly apostrophes.
and 3 more in the full report
4 fixed16 passed either way1 still failing1 broke
Pass-rate lift
+14 pp
Tokens
+163%
Agent turns
0%
Response time
+12%
Model gemini-3.6-flashMeasured 10/10/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
Clean up this release announcement snippet for our CLI tool. The draft was generated by an LLM and left curly apostrophes and smart double quotes throughout: “We’ve updated the engine’s configuration parser, so it won’t crash when reading nested YAML files.” Rewrite it to follow clean plain-text developer style.
What was checked, without and with the skill
Checked
Without skill
With skill
The output uses straight single and double quotes instead of curly quotes.
Missed
Passed
case-05 · gemini-3.6-flash · 10/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md75 linessingle file
Unslop
Edit text to remove AI patterns and add human voice.
Process
Scan for the patterns below.
Rewrite. Preserve meaning, match intended tone.
Add soul (see next section).
Self-audit: "What makes this obviously AI generated?" Fix remaining tells.
Adding soul
Removing patterns is half the job. Sterile, voiceless writing is just as obvious.
Have opinions. React to facts instead of neutrally listing pros and cons.
Vary rhythm. Short sentences. Then longer ones that take their time. Mix it up.
Acknowledge complexity. "Impressive but also kind of unsettling" beats "impressive."
Use "I" when it fits. First person isn't unprofessional.
Let some mess in. Perfect structure looks machine-made.
Be specific. Not "this is concerning" but "there's something unsettling about agents churning away at 3am."
Patterns to detect and fix
Content
Puffery. "pivotal moment", "testament to", "evolving landscape", "setting the stage for", "indelible mark", "deeply rooted". Cut puffery, state what happened.
Name-dropping. Listing media outlets without context. Pick one, say what was said.
Superficial -ing phrases. "highlighting...", "ensuring...", "reflecting...", "showcasing...", "fostering...". Delete or expand with real sources.