thread-analysis
Analyze Twitter/X threads to extract insights from viral and educational content. Use when the user mentions Twitter, X, thread, tweets, viral thread, or provides a twitter.com or x.com URL.
When & Why to Use This Skill
This Claude skill automates the extraction of insights from Twitter (X) threads, converting viral and educational social media content into structured, high-quality Markdown reports. By streamlining the process of fetching, analyzing, and archiving conversational data, it helps users transform fleeting social media interactions into permanent, actionable knowledge assets.
Use Cases
- Knowledge Management: Summarize long-form educational threads from industry experts into concise, structured notes for personal or professional knowledge bases.
- Market Intelligence: Analyze viral X threads to identify emerging trends, public sentiment, and key takeaways within specific industries.
- Content Curation: Quickly extract core insights from thought-leader discussions to fuel newsletters, research papers, or social media repurposing.
- Digital Archiving: Automatically save and log valuable Twitter conversations as organized Markdown files, complete with metadata and author information for future reference.
| name | thread-analysis |
|---|---|
| description | Analyze Twitter/X threads to extract insights from viral and educational content. Use when the user mentions Twitter, X, thread, tweets, viral thread, or provides a twitter.com or x.com URL. |
Twitter/X Thread Analysis
Analyze Twitter/X threads to generate structured reports with summaries, key points, and insights from conversational content.
When to Use
Activate this skill when the user:
- Mentions "Twitter", "X", "thread", "tweets", "tweet thread"
- Provides a twitter.com or x.com URL
- Asks to summarize a viral thread
- Wants to analyze a thread they copied
- References a thought-leader's thread
Instructions
- Get the thread content:
- If URL: Fetch using WebFetch (try nitter mirror if needed)
- If text: Use directly
- Ask for URL or content if not provided
- If fetch fails:
- Inform user: "Could not fetch thread content"
- Suggest copying thread text manually
- Stop here
- Read the analysis prompt from
prompts/thread.md - Extract thread metadata:
- Author handle and name
- Thread topic/title
- Number of tweets
- Generate analysis following the prompt structure exactly
- Create output directory
reports/threads/if needed - Save the report to
reports/threads/YYYY-MM-DD_sanitized-title.md - Update the activity log at
logs/YYYY-MM-DD.md:- Add entry under "## Threads Read" section
- Format:
- [Title](../reports/threads/filename.md) - HH:MM
- Confirm to user what was saved and where
Report Format
# [Thread Topic/Title]
**Source**: [URL or "Manual Input"]
**Author**: [@handle]
**Date**: YYYY-MM-DD
**Type**: Twitter/X Thread
---
[Analysis content following prompts/thread.md structure]
---
## My Notes
[Empty space for user notes]
Error Handling
- If URL invalid: Ask for correct URL or suggest copy
- If thread too short: Analyze but note limited content
- If prompts/thread.md missing: Use prompts/default.md
Related
- Slash command:
/thread <url-or-content> - Prompt file:
prompts/thread.md - Output:
reports/threads/