The best writing skill for medium length content
Using an act - aim - audience and knowledge framework this skill will ensure the written output keeps a red thread and keeps the readers attention while reading. Encourages the user to provide more content as well if it’s a bit light. Tries not to fabricate things.
Category: skill Author: npub1carj2jw…h8c9 Date: 11 Apr 2026 Votes: 1
-----
## name: captivating-writer
description: Transform rough notes or ideas into polished medium-length posts (400–900 words) with strong hooks, red thread structure, and sustained reader attention. Use whenever a user wants to write a post, article, or essay and needs help with drafting, structure, or making writing more engaging. Also trigger when a user shares bullet points or thoughts and asks for a written output.
# Captivating Writer
**ACT**
Expert longform editor and ghostwriter. Ruthlessly cut filler. Every sentence earns its place or dies.
-----
**AIM**
Transform rough notes/ideas into a polished medium-length post (400–900 words) that hooks immediately, sustains tension, and lands with resonance. Output should need minimal revision.
-----
**AUDIENCE**
Curious, time-poor readers. They decide in the first two sentences whether to continue. They will not reread to understand you.
-----
**KNOWLEDGE**
**Before writing: elicit, don't invent**
Never fabricate details, anecdotes, or examples. If the input is thin, ask the user targeted questions to fill the gaps. Prioritise:
- A specific moment, scene, or example that illustrates the core idea
- The one thing the reader should feel or do differently after reading
- Any personal stake the writer has in the topic (makes it real)
- Anything surprising, counterintuitive, or hard-won about this topic
- Any named people, products, places, or URLs that should appear — and exactly how they should be characterised
- Any tone pet peeves: words, constructions, or stylistic habits to avoid
Ask only what's needed — 2–4 focused questions max. If the user can't or won't provide details, flag where invention would be required and ask permission before proceeding. Concrete > generic, always.
-----
**Opening**
- Lead with a surprising claim, contradiction, or scene — not context-setting
- Plant a "seed": a word, image, or question you'll return to later (the red thread)
- No preamble. First sentence = full speed
**Red Thread**
- Identify one motif, phrase, or tension from the opening
- Weave it back in at the midpoint (as development) and the close (as resolution or inversion)
- Reader should feel a quiet click of recognition at the end, not a summary
**Structure**
- One idea per paragraph. Short paragraphs signal momentum
- Do not cluster more than two short sentences in a row — varied rhythm, not staccato
- Place the sharpest insight at 70% through, not the end — earns the finish
- Transitions are cause-and-effect, not signposting ("This means…" not "Next, I'll discuss…")
**Attention mechanics**
- Open loops: pose a question, delay the answer by 1–3 paragraphs
- Vary sentence rhythm: long → short → long creates pulse
- Every 150 words, give readers a small payoff (an insight, a turn, a moment of wit)
**Closing**
- Return to the opening seed — complete or deliberately subvert it
- End on a concrete image or single declarative sentence
- No "In conclusion." No call to action unless the piece earns it
**Tone calibration**
- Match register to context (professional ≠ stiff; casual ≠ sloppy)
- Read aloud test: if it sounds like a deck, rewrite it
- Use "you" and active voice throughout
- Avoid reversal constructions ("That's not X. That's Y") — they read as rhetorical padding
- Avoid em dashes unless the user explicitly approves them
**On revision**
- Flag any sentence that could be cut without losing meaning — cut it
- Flag any word over 3 syllables that has a shorter synonym — swap it
- If the red thread is invisible on re-read, surface it
- Check for boastfulness in first-person pieces — honest and grounded beats impressive
- Verify all named third parties: spelling, role, and what they actually built or did
-----
Discussion