skills/content/twitter-thread/SKILL.md
Use this skill when the user says 'twitter thread', 'tweet thread', 'X thread', 'viral thread', or wants to create a multi-tweet narrative with hook tweets, data points, and CTAs. Do NOT use for TikTok scripts, newsletters, or LinkedIn posts.
npx skillsauth add cwinvestments/memstack memstack-content-twitter-threadInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Creates multi-tweet threads (5-15 posts) with hook formulas, narrative arc, engagement tactics, data points, CTA placement, and scheduling strategy.
When this skill activates, output:
Twitter Thread — Writing viral thread...
Then execute the protocol below.
| Context | Status | |---------|--------| | User says "twitter thread", "tweet thread", "X thread" | ACTIVE | | User says "viral thread" or wants multi-tweet content | ACTIVE | | User wants to share insights, stories, or frameworks on Twitter/X | ACTIVE | | User wants a TikTok or Reels script | DORMANT — use TikTok Script | | User wants a newsletter | DORMANT — use Newsletter |
| Mistake | Why It's Wrong | |---------|---------------| | "Weak first tweet" | Tweet 1 is your headline. If it doesn't stop the scroll, no one reads tweets 2-15. | | "Wall of text per tweet" | White space matters. Short lines, line breaks, and punchy sentences get read. | | "No thread structure" | Random thoughts don't thread well. Use a framework: story, list, or lesson arc. | | "Forget the CTA" | Every thread should end with a clear ask: follow, retweet, reply, or click. | | "Post at random times" | Twitter engagement peaks at specific hours. Schedule for your audience's timezone. |
If the user hasn't provided details, ask:
- Topic — what's the thread about?
- Angle — personal story, tactical how-to, hot take, data breakdown, or curated list?
- Goal — followers, engagement, traffic to a link, or brand awareness?
- Length — short (5-7 tweets), medium (8-12), or long (13-15)?
- Key points — what are the 3-5 main takeaways?
| Structure | Best For | Pattern | |----------|---------|---------| | Story arc | Personal experience, case study | Setup → Conflict → Turning point → Resolution → Lesson | | Listicle | Tips, tools, resources | Hook → Item 1 → Item 2 → ... → Summary → CTA | | Framework | Teaching a method | Hook → Context → Step 1 → Step 2 → Step 3 → Recap → CTA | | Contrarian | Hot takes, challenging norms | Bold claim → Evidence 1 → Evidence 2 → Nuance → Reframe → CTA | | Before/After | Transformations, results | Old way → Problems → Discovery → New way → Results → CTA |
The hook tweet determines 90% of thread performance.
Hook formulas:
| Formula | Template | Example | |---------|---------|---------| | Bold claim | "[Counter-intuitive statement]:" | "Most marketing advice is wrong:" | | Numbered list | "[X] [things] that [outcome]:" | "7 pricing mistakes that cost me $50K:" | | Story opener | "In [year], I [dramatic situation]." | "In 2023, I almost shut down my startup." | | Question | "Why do [group] always [action]?" | "Why do most SaaS founders underprice?" | | Data hook | "I analyzed [X] and found [surprising result]." | "I analyzed 500 landing pages. Here's what converts:" | | Time-based | "[Time period] ago, I [situation]. Today, [result]." | "6 months ago I had 200 followers. Today: 50K." |
Hook rules:
: or "Here's what I learned:" to signal more is comingBody tweet rules:
1/, 2/) OR natural flow (no numbers) — don't mixFormatting patterns:
[Concept tweet]
This is the key insight.
Most people think [common belief].
But the reality is [contrarian truth].
Here's why:
[Tactical tweet]
Step 3: [Action]
→ Do [specific thing]
→ Then [specific thing]
→ Result: [outcome]
This alone [impressive result].
[Data tweet]
I tested this on [X samples].
Results:
• [Finding 1]: [XX]%
• [Finding 2]: [XX]%
• [Finding 3]: [XX]%
The winner? [Finding].
Engagement re-hooks (insert at tweets 4, 7, 10):
CTA formulas:
| Goal | CTA Template | |------|-------------| | Followers | "Follow me @[handle] for more [topic]. I share [value] every [frequency]." | | Retweet | "If this was helpful, retweet the first tweet so others can find it." | | Reply | "What would you add? Drop your best [topic] tip below." | | Link click | "I wrote a full breakdown here: [link]" | | Newsletter | "I go deeper on this in my newsletter. Subscribe: [link]" | | Engagement | "Which of these was most surprising? Reply with the number." |
CTA rules:
Thread checklist:
Scheduling strategy:
# Twitter/X Thread — [Topic]
**Structure:** [Story / Listicle / Framework / etc.]
**Length:** [X] tweets
**Goal:** [Followers / Engagement / Traffic]
**Best posting time:** [Day, Time, Timezone]
## Thread
**Tweet 1 (Hook):**
[Hook tweet — under 180 chars]
**Tweet 2:**
[Body tweet]
**Tweet 3:**
[Body tweet]
[...all tweets...]
**Tweet [N] (CTA):**
[Closing CTA tweet]
**Reply to thread:**
[Link or bonus content — posted as a reply to tweet 1]
Twitter Thread — Complete!
Topic: [Topic]
Structure: [Type]
Length: [X] tweets
Hook type: [Formula used]
CTA: [Primary action]
Next steps:
1. Read the full thread aloud — trim anything that doesn't flow
2. Schedule for [optimal time] using a scheduling tool
3. Self-retweet 6-8 hours after posting
4. Engage with every reply in the first 2 hours (boosts algorithm)
5. Track impressions and engagement rate to learn what works
tools
Use when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session.
tools
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
development
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
development
Use when the user says 'teach me', 'explain as you go', 'mentor mode', 'walk me through', 'help me learn', 'explain why', 'learning mode', or wants real-time plain language narration of decisions and tradeoffs while building. Do NOT use for code review or debugging.