RightBlogger/bloggingskills / skills/humanize
humanize
VerifiedRewrites AI-sounding prose so it reads like a person wrote it, removing AI tells (em dashes, 'it's not X, it's Y', model vocabulary, stock openers) while keeping every fact. Use when the user says 'humanize this', 'de-slop', 'this sounds like AI', 'robotic', 'like ChatGPT', or 'too many em dashes', or asks why a draft feels off. For a report without a rewrite, see house-style. For matching a specific person's voice, see brand-voice. For a new post, see article.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.5 KB |
| references/ai-tells.md | markdown | 21.2 KB |
| references/example.md | markdown | 3.7 KB |
references/example.md
View on GitHub# Worked example: humanizing a slopped paragraph
One annotated rewrite, because the hard part isn't spotting a single tell, it's
untangling a paragraph where they stack. Read this before a heavy de-slop.
## Before (almost every sentence is a tell)
> In today's rapidly evolving digital landscape, choosing the right project management
> tool isn't just important, it's absolutely critical. Let's dive in. The truth is
> simple: most teams are drowning. Not in work. Not in deadlines. In tools. Here's the
> kicker: the very software meant to help is quietly suffocating their productivity.
> Studies show that teams waste countless hours every week. It's worth noting that this
> is a pervasive issue. Think of it as a tax on every single thing you do. So what's the
> solution? A unified platform. From scrappy startups to sprawling enterprises,
> organizations everywhere are leveraging robust, cutting-edge solutions to streamline
> their workflows and unlock their team's full potential. In conclusion, the right tool
> can be a genuine game-changer.
What's wrong, in order of damage:
- Banned opener ("In today's rapidly evolving digital landscape").
- Negative parallelism and fragments ("isn't just important, it's critical"; "Not in
work. Not in deadlines. In tools.").
- Pedagogical and false-suspense filler ("Let's dive in", "Here's the kicker", "The
truth is simple", "It's worth noting").
- Magic adverbs and stakes inflation ("quietly suffocating", "absolutely critical").
- Vague attribution and filler quantity ("Studies show", "countless hours").
- Self-answered question ("So what's the solution? A unified platform.").
- Patronizing analogy ("Think of it as a tax").
- False range ("From scrappy startups to sprawling enterprises").
- AI-ese pileup ("leveraging robust, cutting-edge solutions to streamline ... unlock ...
full potential").
- Signposted conclusion and a banned noun ("In conclusion", "game-changer").
Because most sentences are tells, this is a Scope case (Method step 6): rewrite from the
argument, don't patch sentence by sentence. The argument is small and true: teams lose
time to tool sprawl, and consolidating onto one platform helps.
## After (same length, same claim, human)
> Picking a project management tool is one of those decisions that quietly shapes how a
> team spends its days. Get it wrong and the cost compounds.
>
> Most teams lose more time to their tools than to their workload. The software that
> promised to speed things up ends up slowing everyone down: an hour lost switching
> apps, another hunting for a file. Over a week that adds up, and it
> works like a tax on everything the team is trying to ship.
>
> The fix is usually consolidation. Startups and large companies alike are moving their
> work onto one platform instead of stitching five together. When the tool fits, the
> hours spent switching apps come back.
What changed, and why:
- Kept the one real idea (tool sprawl wastes time; consolidating helps) and the one
concrete image (the "tax"), since that was the draft's best line. Cut only the "Think
of it as" frame around it.
- Removed every banned phrase, the false range, and the AI-ese stack.
- Replaced "Studies show countless hours" with a concrete, honest picture ("an hour lost
switching apps") instead of a fake statistic. If a real number existed it would go
here; since none was given, the rewrite doesn't invent one. When a fact you need is
missing, flag it to the user rather than launder it into vagueness.
- Varied sentence openings and lengths so no rhythm repeats.
Note: "quietly" survives once, where it does real work rather than inflating. One
instance is fine. The original's problem was the pile-up, not any single word.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |