Punchy Insight Refiner
Turn correct-but-dead prose into lines a human will finish.
When to Use
- Newsletter, Substack, or skill intro drafts sound like a model wrote them
- The claim is right; the sentences are long, soft, or hedged to death
- You need a hook title + tight body without adding new facts
- An agent produced a summary and you want the publishable cut
Do not use to invent evidence, soften a hard claim into mush, or expand short text into essays.
Not for LinkedIn algorithm / forensic de-AI audit → linkedin-humanizer (tiered scrub, detector spread, profile voice).
Not for full LinkedIn post drafting from a topic → linkedin-post-writer / linkedin-marketing.
This skill = claim-preserving short-form for any channel (newsletter, skill intro, CTA).
Contract
| In |
Out |
| Draft prose + must-keep claims |
Punchy rewrite |
| Optional audience + max words |
Title options (2–3) |
|
Claim checklist (what stayed true) |
Inputs
- Draft — the raw text
- Must-keep claims — bullets that cannot change meaning
- Constraints — max words, tone (direct / warm / dry), forbidden words
Process
Extract claims
List every factual or instructional claim. If the user supplied must-keeps, those win.
Kill the sludge
Cut: “In today’s world”, “It’s important to note”, “delve”, stacked adverbs, fake wonder, throat-clearing intros.
One idea per sentence
Split compound sentences. Prefer subject–verb–object. Put the cost or surprise early.
Hook first
Open with tension, a concrete failure, or a sharp rule—not with the topic name.
Rewrite short
Target 30–40% fewer words unless constrained otherwise. Keep verbs active.
Claim check
For each must-keep claim: still true? still present? If a line sounds better but changes meaning, revert that line.
Title pass
Offer 2–3 titles: specific > clever. No clickbait that the body doesn’t pay off.
Return package
TITLE OPTIONS
...
REFINED
...
CLAIMS PRESERVED
- ...
CUTS (optional)
- removed X because ...
Invocation (agent)
load_skill("punchy-insight-refiner")
# draft: <text>
# must_keep: [claim1, claim2]
# max_words: 400
Verification
- Every must-keep claim appears in refined output (paraphrase OK, meaning not OK to drop)
- No new numbers, names, or guarantees introduced
- First two sentences work as a standalone hook
- Word count under constraint
NEVER
- Add facts “for color”
- Replace a precise claim with a vague vibe
- Use hype stacks (“revolutionary”, “game-changing”, “unleash”)
- Lengthen the draft
- Open with “In this article/post/skill”
- Run LinkedIn 2026 algorithm audits or multi-detector AI-score loops (use
linkedin-humanizer)
- Build a voice/brand profile from past posts (use
linkedin-humanizer --mode profile)
Related skills
| Need |
Skill |
| LinkedIn de-AI + audit + voice profile |
linkedin-humanizer |
| Native LinkedIn post from a theme |
linkedin-post-writer |
| Full series episode (skill+video+newsletter) |
ai-skills-episode-factory |
Minimal Example
Draft:
It is important to note that agents often lose valuable work when a session ends, and packaging that work into a skill can help future runs.
Must-keep: Session-end loses work; packaging into a skill helps future runs.
Refined:
Your agent solved it. Then the session ended—and the solution died with it.
Package the path into a skill, or solve it from zero again tomorrow.
Why it compounds
Publishable voice is a skill. Agents that refine before they ship stop flooding you with correct sludge.
1---2name: punchy-insight-refiner3description: Use when prose is correct but dull, long, or AI-flat and you need short human lines that keep the claim. Rewrites for punch without hype, without inventing facts.4---56# Punchy Insight Refiner78Turn correct-but-dead prose into lines a human will finish.910## When to Use1112- Newsletter, Substack, or skill intro drafts sound like a model wrote them13- The claim is right; the sentences are long, soft, or hedged to death14- You need a hook title + tight body without adding new facts15- An agent produced a summary and you want the publishable cut1617**Do not use** to invent evidence, soften a hard claim into mush, or expand short text into essays.1819**Not for LinkedIn algorithm / forensic de-AI audit** → `linkedin-humanizer` (tiered scrub, detector spread, profile voice). 20**Not for full LinkedIn post drafting from a topic** → `linkedin-post-writer` / `linkedin-marketing`. 21This skill = **claim-preserving short-form** for any channel (newsletter, skill intro, CTA).2223## Contract2425| In | Out |26|----|-----|27| Draft prose + must-keep claims | Punchy rewrite |28| Optional audience + max words | Title options (2–3) |29| | Claim checklist (what stayed true) |3031## Inputs32331. **Draft** — the raw text 342. **Must-keep claims** — bullets that cannot change meaning 353. **Constraints** — max words, tone (direct / warm / dry), forbidden words 3637## Process38391. **Extract claims** 40 List every factual or instructional claim. If the user supplied must-keeps, those win.41422. **Kill the sludge** 43 Cut: “In today’s world”, “It’s important to note”, “delve”, stacked adverbs, fake wonder, throat-clearing intros.44453. **One idea per sentence** 46 Split compound sentences. Prefer subject–verb–object. Put the cost or surprise early.47484. **Hook first** 49 Open with tension, a concrete failure, or a sharp rule—not with the topic name.50515. **Rewrite short** 52 Target 30–40% fewer words unless constrained otherwise. Keep verbs active.53546. **Claim check** 55 For each must-keep claim: still true? still present? If a line sounds better but changes meaning, revert that line.56577. **Title pass** 58 Offer 2–3 titles: specific > clever. No clickbait that the body doesn’t pay off.59608. **Return package**61 ```text62 TITLE OPTIONS63 ...64 REFINED65 ...66 CLAIMS PRESERVED67 - ...68 CUTS (optional)69 - removed X because ...70 ```7172## Invocation (agent)7374```text75load_skill("punchy-insight-refiner")76# draft: <text>77# must_keep: [claim1, claim2]78# max_words: 40079```8081## Verification8283- Every must-keep claim appears in refined output (paraphrase OK, meaning not OK to drop) 84- No new numbers, names, or guarantees introduced 85- First two sentences work as a standalone hook 86- Word count under constraint 8788## NEVER8990- Add facts “for color” 91- Replace a precise claim with a vague vibe 92- Use hype stacks (“revolutionary”, “game-changing”, “unleash”) 93- Lengthen the draft 94- Open with “In this article/post/skill” 95- Run LinkedIn 2026 algorithm audits or multi-detector AI-score loops (use `linkedin-humanizer`) 96- Build a voice/brand profile from past posts (use `linkedin-humanizer --mode profile`) 9798## Related skills99100| Need | Skill |101|------|--------|102| LinkedIn de-AI + audit + voice profile | `linkedin-humanizer` |103| Native LinkedIn post from a theme | `linkedin-post-writer` |104| Full series episode (skill+video+newsletter) | `ai-skills-episode-factory` | 105106## Minimal Example107108**Draft:** 109It is important to note that agents often lose valuable work when a session ends, and packaging that work into a skill can help future runs.110111**Must-keep:** Session-end loses work; packaging into a skill helps future runs.112113**Refined:** 114Your agent solved it. Then the session ended—and the solution died with it. 115Package the path into a skill, or solve it from zero again tomorrow.116117## Why it compounds118119Publishable voice is a skill. Agents that refine before they ship stop flooding you with correct sludge.
cassidyrice