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.
84
Quality
84%
Does it follow best practices?
Impact
75%
2.14xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
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 well-structured description that clearly communicates capabilities and includes explicit trigger terms. The main weakness is the broad scope ('code, files, or concepts') which could cause conflicts with other skills. The explicit 'Triggers on:' clause is a strength, though some triggers like 'explain' may be too generic.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'deep explanation', 'routes to expert agents', 'uses structural search', 'generates mermaid diagrams'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (deep explanation, routes to agents, structural search, mermaid diagrams) AND when (explicit 'Triggers on:' clause with specific terms). The trigger guidance is explicit and actionable. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'explain', 'deep dive', 'how does X work', 'architecture', 'data flow'. These are common phrases users naturally use when seeking explanations. | 3 / 3 |
Distinctiveness Conflict Risk | While 'deep explanation' and 'mermaid diagrams' are somewhat distinctive, terms like 'explain' and 'how does X work' are very broad and could conflict with general Q&A or documentation skills. The scope of 'complex code, files, or concepts' is quite wide. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and workflow clarity. The multi-step process is clearly documented with concrete commands and expert routing logic. However, the skill is somewhat verbose for its purpose, and the extensive inline tables and repeated patterns could benefit from consolidation or extraction to reference files.
Suggestions
Consolidate the repeated CLI tool availability checks into a single reference section or separate file
Consider extracting the depth modes and focus modes detailed tables into a REFERENCE.md file, keeping only brief summaries inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary verbosity, such as the detailed ASCII architecture diagram and extensive tables that could be condensed. The fallback patterns and tool checks are repeated multiple times. | 2 / 3 |
Actionability | Provides fully executable bash commands, concrete code examples, and copy-paste ready patterns. The CLI tool integration section with specific commands and fallbacks is highly actionable. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit sequencing from detection through integration. Each step has concrete actions and the architecture diagram provides excellent visual guidance for the multi-step process. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is inline in one large file. References to other skills/commands exist but the depth modes, focus modes, and CLI tool tables could be split into separate reference files. | 2 / 3 |
Total | 10 / 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
5342bca
- 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.