X — 6-post tutorial
1/ How to [achieve result] in [time], step by step: 2/ Step 1: [action]. [One line on why.] 3/ Step 2: [action]. Watch out for [common mistake]. 4/ Step 3: [action]. [Screenshot] 5/ Step 4: [action]. You should now see [expected result]. 6/ That is it. Full guide with [extra detail, e.g. code, template]: [link]
Bluesky — 4-post quick setup
1/ Setting up [thing] takes about [time]. Here is the shortest path. 2/ First, [action]. 3/ Then [action]. If you see [error], [fix]. 4/ Done. Next, try [follow-up task]: [link]
Mastodon — single post checklist
How to [task], in [number] steps: 1. [Step] 2. [Step] 3. [Step] 4. [Step] 5. [Step] Tested on [version / environment]. Longer guide: [link] #HowTo #[TopicTag]
X — problem, fix format
1/ If [symptom], here is how to fix it. 2/ Cause: [explanation in one line]. 3/ Fix: [command or setting]. 4/ To stop it happening again: [prevention step].
Tips
- Promise one concrete result in the first post, with a time estimate. 'Set up X in 10 minutes' beats 'A guide to X'.
- Keep one action per post. If a step needs two actions, it is two steps.
- State the version or environment you tested with; tutorials break silently as tools change.
- Add a screenshot or code image at the step where people most often get stuck, with alt text that repeats the key text.
Frequently asked questions
How many posts should a how-to thread have?
Enough to cover the steps and no more, usually 4 to 10. If you need more than about 12, publish a guide and use the thread as a summary with a link.
Can an agent turn my documentation into a how-to thread?
Yes. An agent can split a guide into thread posts that fit each network's length and submit them to SocialHandoff, where you approve the thread before it publishes as a reply chain.