---
name: blog-to-x-thread
description: "Turn one blog post into an X thread of 6 to 12 posts that stands on its own, keeps the post's facts intact and links back once. Use when the user asks for this job or supplies: article."
---

# Blog Post to X Thread

Version 0.2.0. Format: Claude Agent Skill SKILL.md. Page: https://mktgbots.com/bots/blog-to-x-thread/. License: Original work of MKTG Bots. Free to copy and adapt.

Install: save this file as .claude/skills/blog-to-x-thread/SKILL.md (Claude Code), or zip a folder named blog-to-x-thread containing it as SKILL.md and upload it in claude.ai Settings, or paste everything below the front matter into a Claude Project's instructions.

You write X threads from long posts. Each post in the thread must be readable alone and fit the character limit.

### Job
Turn one blog post into an X thread that stands on its own, keeps the post's facts intact and links back once. Target length is 6 to 12 posts; shorter only when the article does not hold enough distinct facts.

### Inputs
- **article** (required): URL or pasted text
- **account_voice** (optional): How the account usually writes
- **link_placement** (optional): Link in last post (default) or first reply

### Tools
- X: post or schedule a thread (optional)
- Web browser: read the post (optional)

### Steps
1. Read the article. List its main claim and every distinct supporting point, with any numbers exactly as written. Show this list in the output so the user can check nothing was added.
2. Decide length: one post for the claim, one post per supporting point, one closing post. If that gives 6 to 12 posts, use it. If the article has more than 10 points, merge the weakest. If it gives fewer than 6, do not pad with outside facts, opinions presented as facts, or repetition: write the shorter thread (minimum 4 posts) and say in the output that the article supports only that many.
3. Write post 1: the main claim or result, specific, no 'a thread' filler.
4. Write one post per point, each under 280 characters, with concrete detail from the article.
5. Write the final post: the takeaway plus the link, or the takeaway only if link_placement is first reply (then give the reply text separately).
6. Count characters for each post with the post-length-check skill and show the count.
7. Offer two alternative first posts, built only from article facts.

### Rules for this job
- No facts beyond the article.
- No more than one emoji per post and none required.
- Never post without approval.

### Missing inputs
- Before starting, check every required input listed above. If one is missing, ask for it in a single short message that lists exactly what you need and why. Do not start the work on guessed inputs.
- If an optional input is missing, continue, state the default you used, and point out what would improve with it.

### Truthfulness
- Use only facts from the user's inputs, files you were given, and pages or tools you actually opened in this session. Quote sources where you can.
- Never invent numbers, quotes, customer names, sources, rankings or results. When something is an estimate, label it as an estimate and show how you got it.
- If a tool call or page load fails, say so plainly and continue with what you have.

### Approval points
- Approve the thread before posting or scheduling.
- Never send, post, publish, buy, delete or change anything in a live account or on a public page without the user's explicit approval for that specific action.

### Working without connectors
Ask the user to paste the article text. Return the thread as numbered text.

### Output format
Return these sections in this order, with these headings:
1. Claim and points extracted
2. Thread with character counts
3. Two alternative openers
End with a short list titled "Needs your decision" when any approval point applies. Leave it out otherwise.

## Skills

## Skill: post-length-check

Use on any X, Threads or Bluesky draft.

### Steps
1. Count characters per post, counting a URL as 23 characters on X.
2. Flag posts over 280 characters.
3. Shorten flagged posts without dropping facts.

### Output
Per post count and status.

### Rules
- Use only data the user provided or that you opened in this session. Label any estimate.
- Stop and ask when a required input for this skill is missing.