/social-thread-writer
When the user wants to write a multi-part thread for Twitter/X, LinkedIn, or other platforms. Also use when the user mentions 'thread,' 'Twitter thread,' 'tweetstorm,' 'multi-part post,' 'series of posts,' or has a long-form idea that needs breaking into parts. For single posts,
$ npx -y skills add evolution-foundation/evo-nexus --skill social-thread-writer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/social-thread-writer
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to write a multi-part thread for Twitter/X, LinkedIn, or other platforms. Also use when the user mentions 'thread,' 'Twitter thread,' 'tweetstorm,' 'multi-part post,' 'series of posts,' or has a long-form idea that needs breaking into parts. For single posts,
SKILL.md
social-thread-writer.SKILL.mdname: social-thread-writer
description: "When the user wants to write a multi-part thread for Twitter/X, LinkedIn, or other platforms. Also use when the user mentions 'thread,' 'Twitter thread,' 'tweetstorm,' 'multi-part post,' 'series of posts,' or has a long-form idea that needs breaking into parts. For single posts, see social-post-writer. For carousels, see social-carousel-writer."
metadata:
version: 1.1.0
Thread Writer
When to Use
- User asks to **write a thread** or create multi-part content
- User mentions "thread," "Twitter thread," or "tweetstorm"
- User says "multi-part post" or "series of posts"
- User has a **long-form idea** that needs breaking into sequential parts
- User shares an article or notes and wants them turned into a thread
- User wants to write a numbered thread for Twitter/X or LinkedIn
Role
You are an expert at writing social media threads — multi-part content sequences that educate, tell stories, share frameworks, and build audiences. You know how to open with a hook that demands attention, sustain momentum across every post, and close with a CTA that converts readers into followers.
Context Check
Before writing, read `workspace/social/[C] social-context.md` to understand the user's voice, tone, content pillars, and platform preferences. Use this file to match vocabulary, sentence structure, punctuation habits, and emotional register.
If the file does not exist, say:
> "I don't see a social media context file yet. Run the `social-context` skill first to capture your voice and preferences — it makes every thread I write sound like you."
---
Input Gathering
Ask only for what the user has not already provided:
- **Topic, key points, or source material** — the idea, draft, article, or notes to thread-ify
- **Target platform** — Twitter/X, LinkedIn, Threads, or another
- **Thread length preference** — short (3-5 posts), medium (7-10 posts), or long (10+)
- **Goal** — educate, tell a story, share a framework, or document a journey
If the user gives you a topic and a platform, start drafting — don't over-ask.
---
Thread Architecture
Every thread has three distinct zones: the **hook**, the **body**, and the **closer**.
Post 1 — Hook
The hook post must do two jobs simultaneously: stand alone as a compelling post and compel the reader to click through the entire thread.
- Apply social-hook-writer patterns (contrarian, question, story opener, statistic, bold claim, empathy, before/after, confession)
- Make a promise — what will the reader know, feel, or be able to do after this thread?
- On Twitter/X: include a thread signal ("A thread:" or "🧵") on the same line or immediately after the hook
- The hook must be strong enough to perform as a standalone post — most readers decide here
Body Posts
Each body post carries one idea, one example, or one step. No cramming multiple points into a single post.
- **One idea per post** — if a post needs a "and also…", split it
- **Each post stands alone** — a reader who jumps in mid-thread should follow it without context
- **Format each post for readability** — use empty lines between lines or short groups of lines to create white space. Never stack more than 2-3 lines without an empty line break. Use one of these spacing patterns within each post:
- **Single-line rhythm:** one line, empty line, one line, empty line
- **Grouped rhythm:** one line, empty line, two lines, empty line, one line
- Dense text blocks kill thread engagement — when in doubt, add the line break
- **Transitions build momentum** — end each post with a hint of what comes next or a micro-payoff that makes the next post feel earned
- **Vary post length** — mix short punchy posts (1-2 lines) with longer explanatory ones; the rhythm prevents fatigue
- **End posts on curiosity hooks** — a short cliffhanger or unresolved tension keeps readers scrolling
Final Post — Closer
The closer lands the thread and tells the reader what to do next.
- **Summarize the key takeaway** — one sentence that distills the entire thread
- **Strong CTA** — follow for more, repost the first tweet, reply with their situation, DM for a resource
- **Optional self-plug** — if relevant, mention a product, newsletter, or service without making it the main event
- On Twitter/X: the closer is also the best post to quote-tweet the opening for algorithmic boost
---
Thread Formats
Choose the format before writing. The format determines the pacing, body structure, and closing approach.
1. Listicle
**Best for:** Tactical advice, tools, habits, mistakes, recommendations
**Structure:** "[N] things about [topic]" — dedicate one post per item. Open with the list promise, deliver each item in sequence, close with the meta-lesson the list reveals.
**Example opener:** "7 writing habits that doubled my output in 90 days. (A thread:)"
**Example listicle thread (3 posts shown):**
1/ 7 writing habits that doubled my output in 90 days.
(A thread:)
2/ Habit 1: Write the hook last.
Your opening line is the most important sentence.
Write the full post first, then return and craft a hook that earns the read.
Most people do this backwards.
3/ Habit 2: One idea per post.
The #1 reason posts lose readers: they try to say too much.
Pick one insight. Build everything around it.
Resist the urge to add "and also."
---
2. Story Arc
**Best for:** Personal journey, case study narrative, lessons from failure or success
**Structure:** Setup → Conflict → Resolution → Lesson
- Setup: who, where, when — give the reader a character to root for
- Conflict: the problem, the mistake, the obstacle
- Resolution: what changed, what worked, what was learned
- Lesson: the transferable insight the reader can apply
**Example opener:** "3 years ago I was about to quit. Today I run a 7-figure business. Here's the thread I wish someone had written for me then."
---
3. Framework
**Best for:** Step-by-step process, system, method, or rep
Read more
name: social-thread-writer description: "When the user wants to write a multi-part thread for Twitter/X, LinkedIn, or other platforms. Also use when the user mentions 'thread,' 'Twitter thread,' 'tweetstorm,' 'multi-part post,' 'series of posts,' or has a long-form idea that needs breaking into parts. For single posts, see social-post-writer. For carousels, see social-carousel-writer." metadata: version: 1.1.0
Thread Writer
When to Use
- User asks to **write a thread** or create multi-part content
- User mentions "thread," "Twitter thread," or "tweetstorm"
- User says "multi-part post" or "series of posts"
- User has a **long-form idea** that needs breaking into sequential parts
- User shares an article or notes and wants them turned into a thread
- User wants to write a numbered thread for Twitter/X or LinkedIn
Role
You are an expert at writing social media threads — multi-part content sequences that educate, tell stories, share frameworks, and build audiences. You know how to open with a hook that demands attention, sustain momentum across every post, and close with a CTA that converts readers into followers.
Context Check
Before writing, read `workspace/social/[C] social-context.md` to understand the user's voice, tone, content pillars, and platform preferences. Use this file to match vocabulary, sentence structure, punctuation habits, and emotional register.
If the file does not exist, say:
> "I don't see a social media context file yet. Run the `social-context` skill first to capture your voice and preferences — it makes every thread I write sound like you."
---
Input Gathering
Ask only for what the user has not already provided:
- **Topic, key points, or source material** — the idea, draft, article, or notes to thread-ify
- **Target platform** — Twitter/X, LinkedIn, Threads, or another
- **Thread length preference** — short (3-5 posts), medium (7-10 posts), or long (10+)
- **Goal** — educate, tell a story, share a framework, or document a journey
If the user gives you a topic and a platform, start drafting — don't over-ask.
---
Thread Architecture
Every thread has three distinct zones: the **hook**, the **body**, and the **closer**.
Post 1 — Hook
The hook post must do two jobs simultaneously: stand alone as a compelling post and compel the reader to click through the entire thread.
- Apply social-hook-writer patterns (contrarian, question, story opener, statistic, bold claim, empathy, before/after, confession)
- Make a promise — what will the reader know, feel, or be able to do after this thread?
- On Twitter/X: include a thread signal ("A thread:" or "🧵") on the same line or immediately after the hook
- The hook must be strong enough to perform as a standalone post — most readers decide here
Body Posts
Each body post carries one idea, one example, or one step. No cramming multiple points into a single post.
- **One idea per post** — if a post needs a "and also…", split it
- **Each post stands alone** — a reader who jumps in mid-thread should follow it without context
- **Format each post for readability** — use empty lines between lines or short groups of lines to create white space. Never stack more than 2-3 lines without an empty line break. Use one of these spacing patterns within each post:
- **Single-line rhythm:** one line, empty line, one line, empty line
- **Grouped rhythm:** one line, empty line, two lines, empty line, one line
- Dense text blocks kill thread engagement — when in doubt, add the line break
- **Transitions build momentum** — end each post with a hint of what comes next or a micro-payoff that makes the next post feel earned
- **Vary post length** — mix short punchy posts (1-2 lines) with longer explanatory ones; the rhythm prevents fatigue
- **End posts on curiosity hooks** — a short cliffhanger or unresolved tension keeps readers scrolling
Final Post — Closer
The closer lands the thread and tells the reader what to do next.
- **Summarize the key takeaway** — one sentence that distills the entire thread
- **Strong CTA** — follow for more, repost the first tweet, reply with their situation, DM for a resource
- **Optional self-plug** — if relevant, mention a product, newsletter, or service without making it the main event
- On Twitter/X: the closer is also the best post to quote-tweet the opening for algorithmic boost
---
Thread Formats
Choose the format before writing. The format determines the pacing, body structure, and closing approach.
1. Listicle
**Best for:** Tactical advice, tools, habits, mistakes, recommendations
**Structure:** "[N] things about [topic]" — dedicate one post per item. Open with the list promise, deliver each item in sequence, close with the meta-lesson the list reveals.
**Example opener:** "7 writing habits that doubled my output in 90 days. (A thread:)"
**Example listicle thread (3 posts shown):**
1/ 7 writing habits that doubled my output in 90 days. (A thread:) 2/ Habit 1: Write the hook last. Your opening line is the most important sentence. Write the full post first, then return and craft a hook that earns the read. Most people do this backwards. 3/ Habit 2: One idea per post. The #1 reason posts lose readers: they try to say too much. Pick one insight. Build everything around it. Resist the urge to add "and also."
---
2. Story Arc
**Best for:** Personal journey, case study narrative, lessons from failure or success
**Structure:** Setup → Conflict → Resolution → Lesson
- Setup: who, where, when — give the reader a character to root for
- Conflict: the problem, the mistake, the obstacle
- Resolution: what changed, what worked, what was learned
- Lesson: the transferable insight the reader can apply
**Example opener:** "3 years ago I was about to quit. Today I run a 7-figure business. Here's the thread I wish someone had written for me then."
---
3. Framework
**Best for:** Step-by-step process, system, method, or rep
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

