explain
Deep explanation of complex code, files, or concepts. Routes to expert agents, uses structural search, generates mermaid diagrams. Triggers on: explain, deep dive, how does X work, architecture, data flow.
68
59%
Does it follow best practices?
Impact
75%
2.14xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/explain/SKILL.mdQuality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly communicates its capabilities and includes explicit trigger terms. The specific mention of techniques (expert agents, structural search, mermaid diagrams) adds clarity about the skill's approach. The main weakness is that some trigger terms like 'explain' are very broad and could conflict with simpler explanation-oriented skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'deep explanation of complex code, files, or concepts', 'routes to expert agents', 'uses structural search', 'generates mermaid diagrams'. These are concrete, identifiable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (deep explanation, routing to expert agents, structural search, mermaid diagrams) and 'when' (explicit 'Triggers on:' clause with specific trigger terms). The trigger clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would actually say: 'explain', 'deep dive', 'how does X work', 'architecture', 'data flow'. These are realistic phrases users would type when seeking code/concept explanations. | 3 / 3 |
Distinctiveness Conflict Risk | While the trigger terms like 'explain' and 'how does X work' are natural, they are quite broad and could overlap with simpler explanation or documentation skills. 'Architecture' and 'data flow' add some distinctiveness, but 'explain' alone could trigger conflicts with many other skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is significantly over-engineered and verbose for what it accomplishes. It describes an elaborate multi-agent orchestration system with expert routing, but much of the content is template boilerplate (the full explanation output format), information Claude already knows (mermaid diagram syntax, basic bash commands), and aspirational architecture rather than concrete executable guidance. The content would benefit enormously from being cut to ~30% of its current size and splitting reference material into separate files.
Suggestions
Cut the full explanation output template entirely—Claude knows how to structure markdown explanations. Instead, provide only the key structural requirements (e.g., 'Include: overview, mermaid diagram, how-it-works steps, dependencies table, design decisions').
Remove mermaid diagram syntax examples—Claude already knows these. Just specify when to use each type (e.g., 'flowchart for control flow, sequence for interactions').
Split the depth/focus mode tables, CLI tool reference, and expert routing table into separate reference files to improve progressive disclosure.
Add error handling and validation checkpoints: what to do when ast-grep/tokei aren't available, when no symbol is found, or when the target is ambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~250+ lines. Includes extensive template markdown that Claude already knows how to produce, explains basic concepts like mermaid diagram types, and provides lengthy architecture diagrams and routing tables that could be dramatically condensed. The full explanation output template alone is unnecessary boilerplate. | 1 / 3 |
Actionability | Provides concrete bash commands and code snippets for target detection and context gathering, but much of the skill describes an idealized orchestration system (expert agent routing, Task tool invocation, parallel execution) without fully executable implementation details. The 'Route to Expert Agent' section references subagent types that may not exist. | 2 / 3 |
Workflow Clarity | The 5-step architecture diagram provides a clear sequence, and individual steps have some detail. However, there are no validation checkpoints or error recovery steps—what happens if ast-grep finds nothing? If the expert agent fails? The workflow assumes a happy path throughout. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files despite the content being long enough to warrant splitting. The full output template, CLI tool reference, depth/focus mode details, and expert routing table could all be separate reference files. No bundle files exist to support this either. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
3ae408c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.