agentleFS
nirholasnirholas/XActions/skills/viral-thread-generation/SKILL.md

viral-thread-generation

Skill648 starsChanged 9 months agoApache-2.0View on GitHub

Researches trending topics and competitor threads to generate high-engagement thread content with optimized hooks, value ladders, and calls to action. Use when creating threads or planning viral content.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every thread follows this 5-part structure:

    line 25
  2. Distinctive:

    No hashtags in hook tweet

    line 45
  3. Distinctive:

    Add line breaks in tweets for readability

    line 91

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Viral Thread Generation

MCP-powered workflow for researching trends, analyzing successful threads, and generating high-engagement thread content.

MCP Tools Used

ToolPurpose
x_search_tweetsFind trending conversations and competitor threads
x_get_tweetsAnalyze competitor content patterns
x_get_profileAudience context for tone matching
x_get_followersUnderstand target audience interests

Thread Structure Template

Every thread follows this 5-part structure:

  1. Hook — First tweet. Stops the scroll. Use: curiosity gap, bold claim, or surprising stat.
  2. Credibility — Why the reader should listen. Brief proof, experience, or data.
  3. Value ladder — 3-7 tweets delivering the core content. Each tweet is self-contained but builds on the previous. Use numbered lists, one idea per tweet.
  4. Twist/insight — Unexpected angle, counterintuitive takeaway, or personal story.
  5. CTA — Call to action: follow, retweet, bookmark, reply, or link.

Workflow

  1. Research trending topics — Call x_search_tweets with 3-5 queries related to your niche. Sort by engagement. Identify topics with high reply counts (indicates discussion potential).
  2. Analyze competitor threads — Call x_get_tweets for 3-5 competitor accounts with limit: 50. Filter for threads (tweets with "🧵" or "Thread:" or high reply counts). Note which hooks and formats performed best.
  3. Mine audience interests — Call x_get_followers with limit: 100 for your account. Scan bios for common interests, job titles, and pain points.
  4. Generate 3 thread drafts — For each, apply the thread structure template:
    • Thread A: Educational (how-to or framework)
    • Thread B: Story-driven (case study or personal experience)
    • Thread C: Contrarian (challenge common wisdom)
  5. Optimize hooks — Write 3 hook variations per thread. Test criteria:
    • Creates curiosity gap or tension
    • Under 200 characters
    • No hashtags in hook tweet
    • Includes a number, question, or bold claim
  6. Add engagement triggers — Insert throughout each thread:
    • "Bookmark this" at the value peak
    • A reply prompt ("What would you add?")
    • Retweet hook in final tweet
  7. Format for posting — Number each tweet, keep under 280 chars, end thread with CTA.

Output Template

## Thread Drafts: {topic}

### Thread A: {title} (Educational)
**Hook options:**
1. "{hook variation 1}"
2. "{hook variation 2}"
3. "{hook variation 3}"

**Thread (selected hook):**
1/ {hook}
2/ {credibility}
3/ {value point 1}
4/ {value point 2}
5/ {value point 3}
6/ {twist/insight}
7/ {CTA — follow + retweet}

**Engagement triggers:** {where bookmarks/replies are prompted}

### Thread B: {title} (Story)
{same structure}

### Thread C: {title} (Contrarian)
{same structure}

### Posting Strategy
- Best day/time: {recommendation}
- Space threads 2-3 days apart
- Reply to your own thread with bonus content 1hr after posting

Tips

  • Threads with 7-12 tweets perform best — long enough for value, short enough to finish
  • First tweet determines 80% of thread performance — invest most time there
  • Add line breaks in tweets for readability
  • End mid-thread tweets with a hook to the next ("But here's what most people miss →")

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.