bluf-rewriter
Reorganizes a memo, email, status update, or report so the bottom line is up front. Implements Kramon's BLUF (Bottom Line Up Front) rule. Use when a draft…
Scrubs the three surface tells that make prose feel AI-generated, padded, or jargon-heavy. Three targets behind one skill, picked via the --target arg. em-dashes (default off in cold email / memo / Slack, max one per page in op-eds), adverbs (the -ly and intensifier pile),
$ npx -y skills add kalyvask/winning-writing --skill style-tells --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/style-tellsContext preview
The summary Claude sees to decide when to auto-load this skill.
Scrubs the three surface tells that make prose feel AI-generated, padded, or jargon-heavy. Three targets behind one skill, picked via the --target arg. em-dashes (default off in cold email / memo / Slack, max one per page in op-eds), adverbs (the -ly and intensifier pile),
name: style-tells description: Scrubs the three surface tells that make prose feel AI-generated, padded, or jargon-heavy. Three targets behind one skill, picked via the --target arg. em-dashes (default off in cold email / memo / Slack, max one per page in op-eds), adverbs (the -ly and intensifier pile), jargon (the Silicon Valley / consultant kill-list plus AI-tell phrases). Use when the user says "kill the AI tells," "scrub jargon," "remove em-dashes," "cut the adverbs," "make this sound human," "less corporate," "sounds like ChatGPT," "—," "very," "really," "leverage," "synergy," "delve," "tapestry." Pass --target em-dashes|adverbs|jargon|all (default all).
Source: `points/ai-writing-rules.md` (em-dash rule), `points/core-rules.md` rule 5 (be shorter), `points/banned-jargon.md`, and Stephen King's *On Writing* (the adverb rule).
Three passes behind one skill. Each pass removes a different surface tell that flags writing as AI-generated, padded, or jargon-heavy:
| Target | What it removes | When to run alone | |---|---|---| | **em-dashes** | em-dashes (—), double-hyphens (--), the "not just X — it's Y" construction | When the only problem is AI-flavored punctuation | | **adverbs** | empty intensifiers, -ly adverbs the verb already implies, sentence-starting adverbs | When the draft is bloated with qualifiers | | **jargon** | banned consultant words, AI-tell phrases, wordy substitutions | When the draft sounds corporate or AI-generated |
Default `--target all` runs all three in order: jargon → adverbs → em-dashes. The order matters: jargon and adverbs often expose dashes that were holding bloated clauses together.
/style-tells "draft text" /style-tells --target em-dashes "draft text" /style-tells --target adverbs "draft text" /style-tells --target jargon "draft text" /style-tells --target all "draft text"
Without `--target`, default to `all`.
---
In 2026 the em-dash is the **#1 AI tell**. Models love them. Humans use them sparingly. A draft with twelve em-dashes per page is a confession that an AI wrote it.
| Format | Em-dashes allowed | |--------|-------------------| | Cold email | **Zero** | | Memo / status update | **Zero** | | Slack message | **Zero** | | LinkedIn post | One, max | | Op-ed / essay | One per page (~250 words), max two | | Substack post | One per major section break |
Over the limit → scrub.
| Pattern | Rewrite options | |---------|-----------------| | `X — Y` (parenthetical aside) | `X (Y)` or `X, Y,` or `X: Y` | | `X — and Y` (continuing thought) | `X. And Y.` or `X, and Y` | | `X — Y — Z` (interrupted clause) | `X, Y, Z` (commas) or `X. Y. Z.` (sentences) | | `If — and only if — Z` | `If, and only if, Z` | | `I built X — A, B, C — from scratch` | `I built X from scratch: A, B, C.` | | `She said — wait, did she?` | `She said. Wait, did she?` | | `It's not just X — it's Y` (AI tic) | Cut entirely. Rewrite without the construction. |
The right substitution depends on what the em-dash was *doing*:
If unsure, ask the user.
---
> *"The adverb is not your friend. The road to hell is paved with adverbs."* — Stephen King
Most adverbs are evidence the verb wasn't strong enough. *"She walked quickly"* → *"she rushed."* *"He smiled broadly"* → *"he grinned."* *"It is very important"* → *"it matters."*
Adverbs also leak the writer's anxiety: *"clearly,"* *"obviously,"* *"of course"* are tells that the writer is afraid the reader won't agree. Kill them; let the argument stand.
| Cut | Why | |---|---| | `very` | If "very" makes a difference, the adjective was wrong. *"Very tired"* → "exhausted." | | `really` | Same problem. *"Really fast"* → "fast" or "blistering." | | `actually` | Almost always pure throat-clearing. | | `basically` | Filler. Cut. | | `literally` | If metaphorical, cut. If literal, you don't need to say so. | | `definitely` | Hedge dressed up as confidence. Just say it. | | `clearly` | The reader decides what's clear. Don't tell them. | | `obviously` | Same problem, plus condescending. | | `essentially` | Filler. | | `simply` | Often patronizing. Cut. | | `quite` | British, weak. Cut. | | `rather` | Hedge. Cut. | | `somewhat` | Hedge. Cut or commit. | | `pretty` (as in "pretty good") | Cut — softens the claim. | | `truly`, `genuinely` | If you have to say it, they don't believe you. | | `arguably` | Then make the argument. |
| Adverb + weak verb | Stronger verb | |---|---| | walked quickly | rushed, sprinted, hurried | | said loudly | shouted, barked | | said quietly | whispered, murmured | | smiled broadly | grinned, beamed | | held tightly | clutched, gripped | | ran very fast | sprinted | | looked carefully | examined, scrutinized | | ate quickly | wolfed down, devoured |
| Cut | Why | |---|---| | `Importantly,` | If it's important, the sentence shows it | | `Notably,` | Same | | `Interestingly,` | Let the reader decide | | `Surprisingly,` | Same | | `Frankly,` | What were you being before? | | `Honestly,` | Same | | `Crucially,` | If it's crucial, write a stronger sentence | | `Ultimately,` | Usually filler | | `Fundamentally,` | Filler |
31 Claude skills for cold outreach, op-eds, pitches, press inquiries, bios, exec memos, performance reviews, spoken-delivery talks, fact-checking, and reply-rate tracking.
Repo: kalyvask/winning-writing
Reorganizes a memo, email, status update, or report so the bottom line is up front. Implements Kramon's BLUF (Bottom Line Up Front) rule. Use when a draft…
Cuts a draft to a target word count without losing substance. Two modes behind one skill. target-count hits a specific number (200 for a cold email, 500 for an…
Rewrites blunt downward or peer feedback as "what I like plus what I would like," focused on the work rather than the person, ideally phrased as a question.…
Finds the unexpected, dry, or self-deprecating angle that makes an email memorable. Turns "professional and polite" into "this person sounds like a real…
Rewrites section titles, slide titles, op-ed headlines, email subject lines, and chapter headings from category labels into bold arguable claims. Implements…
Cuts cinematic details that don't serve the main point. The opposite move from vividness. Vividness adds sensory detail; this skill removes detail that's vivid…