Write a multi-post social thread that earns continuation through one coherent idea, strong sequencing, self-contained posts, evidence, and a useful conclusion rather than splitting an article arbitrarily.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add Dadmin88/hermes-profile-packs --skill thread-writing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Thread Writing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dadmin88-thread-writing)More formats (shields.io, HTML) on the badges page.
---
name: thread-writing
description: Write a multi-post social thread that earns continuation through one coherent idea, strong sequencing, self-contained posts, evidence, and a useful conclusion rather than splitting an article arbitrarily.
---
# Social Thread Writing
Use when a topic genuinely benefits from several sequential social posts.
## Procedure
1. Define the one idea, story, tutorial, argument, or build narrative the thread should deliver and the audience takeaway at the end.
2. Open with enough context and tension that an unfamiliar reader understands why continuing is worthwhile without clickbait that the thread cannot satisfy.
3. Outline the sequence as distinct beats where each post advances the idea and naturally creates the need for the next.
4. Make each post understandable if encountered alone while preserving clear continuity with the thread.
5. Use screenshots, diagrams, clips, examples, numbers, or source evidence at the beat where they strengthen understanding rather than dumping media at the end.
6. Vary post length and rhythm according to content; avoid repetitive filler transitions such as announcing every next point.
7. End with the useful conclusion, result, lesson, or next action and link only where it genuinely extends the thread.
8. Check current platform limits and media behavior at publishing time and adjust packaging without changing the underlying narrative.
## Decision rules
- Use a thread because sequencing adds value, not because one post feels too short.
- Every post should advance the argument or story.
- The opening should promise what the thread actually delivers.
- Avoid forced engagement prompts that add nothing to the reader.
## Quality gate
The thread is ready when it has one coherent arc, every post contributes distinct value, a stranger can enter at the beginning without prior context, evidence appears where needed, the ending pays off the opening, and platform packaging can be updated without rewriting the substance.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!