explain
Explain a file, function, or system — architectural walkthrough using query tools
npx skills add majiayu000/claude-skill-registry --skill explain-cwilliams5-alt-tabby --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
The user wants to understand how something works. Not a review, not an audit — just teach. Build a concise architectural explanation using the query tools. Minimize context cost — don't load entire files when a query tool can answer. ## How to Research Use the query tools to build understanding efficiently: - `query_interface.ps1 <filename>` — Start here. Shows a file's public functions and globals — the API surface without loading the implementation. - `query_function.ps1 <funcName>` — Read a specific function body when you need implementation details. - `query_function_visibility.ps1 <funcName>` — Who calls this function? Who does it call? Traces the call graph. - `query_global_ownership.ps1 <globalName>` — Who reads/writes this global? Shows data flow across files. - `query_config.ps1 <keyword>` — Find config settings related to the topic. `-Usage <key>` shows which files consume a setting. - `query_ipc.ps1 <msgType>` — Trace IPC message flow between processes. - `query_timers.ps1 <keyword>` — Find timers related to the topic. - `query_state.ps1 <State> [Event]` — Trace state machine paths. **Prefer interface queries over file reads.** `query_interface.ps1` gives you the shape o
- How to Research
- How to Explain
- 1. Overview (1-3 sentences)
- 2. Files involved
- 3. Data flow
- 4. Key functions
- 5. Key decisions
- 6. Config
- Tone
What does the explain skill do?
Explain a file, function, or system — architectural walkthrough using query tools
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill explain-cwilliams5-alt-tabby --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.