SkillHub ClubShip Full StackFull Stack

thread-analysis

Imported from https://github.com/az9713/cerebro.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C3.1

Composite score

3.1

Best-practice grade

S96.0

Install command

npx @skill-hub/cli install az9713-cerebro-thread-analysis

Repository

az9713/cerebro

Skill path: .claude/skills/thread-analysis

Imported from https://github.com/az9713/cerebro.

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: az9713.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install thread-analysis into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/az9713/cerebro before adding thread-analysis to shared team environments
Use thread-analysis for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
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

1. **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
2. If fetch fails:
   - Inform user: "Could not fetch thread content"
   - Suggest copying thread text manually
   - Stop here
3. **Read the analysis prompt** from `prompts/thread.md`
4. **Extract thread metadata**:
   - Author handle and name
   - Thread topic/title
   - Number of tweets
5. **Generate analysis** following the prompt structure exactly
6. **Create output directory** `reports/threads/` if needed
7. **Save the report** to `reports/threads/YYYY-MM-DD_sanitized-title.md`
8. **Update the activity log** at `logs/YYYY-MM-DD.md`:
   - Add entry under "## Threads Read" section
   - Format: `- [Title](../reports/threads/filename.md) - HH:MM`
9. **Confirm to user** what was saved and where

## Report Format

```markdown
# [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/`