Thread Explainer
A page of every open T3 Code thread, sorted into lanes by what each one wants from Mike, read straight from T3's own database. Use when he asks for the thread explainer, what his open threads want from him, or to catch up on all of them at once.
Install
npx skills add thatmike1/claude-skills --skill thread-explainergit clone --depth 1 https://github.com/thatmike1/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/thread-explainer ~/.claude/skills/thread-explainerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# thread explainer
Mike fires threads as ideas arrive, then comes back and cannot tell what each one wants. The page answers that per thread in one line he can act on, sorted into lanes and numbered by sidebar position, so Ctrl and the number jumps straight to it. You do the judging; the scripts collect and lay out.
`S=~/.claude/skills/thread-explainer/scripts`
## 1. Gather
`node $S/gather.mjs` reads T3's state read-only and prints a new run folder holding `facts.json` for the build and `read.md` for you. The thread you run in is found from your session id and left out (for a delegated agent, the thread it works for), and so are snoozed threads.
## 2. Judge every thread
Read `read.md` whole, then write `judgments.json` beside it, one entry per thread id:
```json
{ "threads": { "<thread id>": {
"kind": "answer",
"about": "What the thread is about now, one sentence.",
"you": "The one thing he does next.",
"happened": "What it did and found, two or three sentences.",
"context": "Optional: what he needs to know before acting.",
"links": [{ "label": "overnight page", "href": "/home/thatmike1/.../index.html" }]
} } }
```
The lanes, one `kind` per thread:
- `answer`: the last reply asks him something he can answer from the chat.
- `look-answer`: it made something (a page, an image, a PR) and wants his verdict on it.
- `do`: his next step happens outside the chat: a click, a setting, a key to rotate, a fresh thread to start.Details
- Skill name
thread-explainer- Repository
- thatmike1/claude-skills
- Path
thread-explainer/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Thread Explainer skill do?
A page of every open T3 Code thread, sorted into lanes by what each one wants from Mike, read straight from T3's own database. Use when he asks for the thread explainer, what his open threads want from him, or to catch up on all of them at once.
How do I install the Thread Explainer skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add thatmike1/claude-skills --skill thread-explainer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Thread Explainer popular?
It lives in thatmike1/claude-skills, which has 10 GitHub stars and 1 forks.
Related skills
Afk Prompt
10thatmike1/claude-skills
Write a copy-paste prompt that hands one or more tasks (usually beads issues) to a fresh Claude instance to run autonomously while the user is away — no questions, no waiting for input. Includes picking which tasks are safe to run unattended. Use when the user says they're going AFK (shower, lunch, errand, overnight), asks "which tasks can just run without me", or wants an autonomous/batch prompt. For attended sessions the user will steer, use the live-prompt skill instead.
AI CV Scanner
10thatmike1/claude-skills
Mine Claude Code conversation history to answer questions about your AI experience. Scans session indexes, spawns parallel subagents to deep-dive relevant conversations, and drafts evidence-based answers. Use when user mentions CV, AI experience, questionnaire, scan my conversations, or needs to document their AI usage.
Arena
10thatmike1/claude-skills
Give several T3 child candidates the same prompt, rank them against a rubric written before they run, pick a base and graft the best of the rest into it. Run with /arena when one attempt at a non-trivial artifact would lock in the wrong shape.
Connect Cdc Mongodb
9redpanda-data/skills
Streams change data capture from MongoDB into Redpanda or Kafka using Redpanda Connect's mongodb_cdc input, built on MongoDB Change Streams over a replica set or sharded cluster. Use when configuring mongodb_cdc, setting up Change Streams, enabling an initial or incremental snapshot alongside live streaming, backfilling a collection on demand through a signal collection, choosing between update_lookup and pre_and_post_images document modes, or checkpointing with resume tokens in a cache resource. Also covers Redpanda Enterprise destination features like Iceberg Topics, Tiered Storage, and serv
Settle Sweep
10thatmike1/claude-skills
Answers "what can I settle", "what's open", "which threads can I close" with one line per open T3 Code thread, settle it, it needs him, or still running, read from T3's own database. Use for any quick pass over his open threads; the full page of every thread is thread-explainer.
Connect Cdc Mysql
9redpanda-data/skills
Streams change data capture from MySQL or MariaDB into Redpanda or Kafka using the mysql_cdc input in Redpanda Connect, which replicates row-level changes via binlog. Use when configuring mysql_cdc, setting up binlog replication and an initial snapshot, wiring a checkpoint_cache resource, using AWS RDS or Aurora with IAM auth, or routing per-table CDC events to separate topics. Also covers Redpanda Enterprise destination features such as Iceberg Topics, Tiered Storage, and server-side Schema ID Validation, since mysql_cdc itself is an Enterprise connector requiring a Redpanda Enterprise licens
Browse the most popular Claude skills, all databases skills, or write your own with the skills generator.