Tweet Thread from Blog

What this skill does

Reads a blog post and produces a 6-12 tweet thread. The first tweet hooks the reader with a concrete claim or stat; each subsequent tweet carries one idea; the last tweet links to the post and a soft CTA.

Inputs

• post_path: markdown blog post.
• Optional target_length: number of tweets (default 8). Hard cap 12.
• Optional cta_text: closing tweet text override.
• Optional link: URL to the published post.

Steps

1. Read the post. Extract the title, the lede (first 200 words), and any H2-defined sections.
2. Identify the central claim: pick the most concrete sentence in the lede that contains a number, a contrarian assertion, or an outcome.
3. Compose tweet 1 (the hook): under 240 chars, no link, no hashtags. Lead with the central claim, set up tension, promise a thread.
4. Map sections to tweet candidates: each H2 contributes one tweet summarizing its key point. Drop sections that are pure recap.
5. Per tweet, enforce: under 270 chars (leave room for "X/N"), one idea per tweet, sentence-case (no all-caps), no hashtags except where genuinely useful.
6. Insert "X/N" counters on each tweet (1/8, 2/8...).
7. Compose the final tweet: link to the post + cta_text (default "Full post:").
8. Sanity-check the thread arc: tweet 1 to tweet N-1 must build toward a payoff; if tweets N/2..N-1 repeat earlier ideas, condense.
9. Output the thread as a numbered list with character counts.

Output

A markdown file thread-<post-slug>.md listing each tweet on its own line with [chars: N] annotation. A ready-to-paste sequence for Twitter/X. Stdout prints total character count and average tweet length.

Verification

For each tweet, count characters with awk '{ print length }'; assert each is <= 280. Read the thread out loud — confirm tweet 1 introduces tension and the closer references the same tension resolved. Cross-check: every tweet body must be a faithful paraphrase from the post; do not invent statistics not present in the source.

Edge cases

• Posts shorter than 600 words: produce a 4-6 tweet thread instead; padding to 8 is artificial.
• Posts with heavy code blocks: code rarely fits in tweets; surface a "code in the post" tweet pointing at the link rather than copying snippets verbatim.
• Posts in non-English: keep the language; do not auto-translate.
• Posts that argue a contested take: the lead tweet should signal the take is opinionated, not present it as fact.