explain

Read and explain code or a flow without making changes

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./app/src/main/assets/skills/explain/SKILL.md

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured read-only workflow that gives concrete, actionable guidance without explaining basics Claude already knows, scoring at the top across all content dimensions.

Dimension	Reasoning	Score
Conciseness	The ~16-line body is lean and assumes Claude's competence, with no padding or explanation of concepts Claude already knows; every line instructs.	3 / 3
Actionability	Concrete, executable guidance such as "ListFiles first to orient yourself" and "Reference real line numbers and file paths (`src/foo.js:42`)"; absence of code is appropriate for a read-only instruction skill.	3 / 3
Workflow Clarity	A clear, unambiguous numbered sequence (Read → Trace call graph → State purpose/mechanism → Reference locations → Note surprises); as a simple read-only skill it needs no validation checkpoints.	3 / 3
Progressive Disclosure	Under 50 lines with no external references and well-organized into Approach/Don't sections; no bundle files exist, so there is no nested-reference risk.	3 / 3
	Total	12 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and third-person with a clear read-only framing, but it lists only two actions and lacks an inline "when to use" trigger, keeping it at the mid level across dimensions.

Suggestions

Expand the description with more specific actions (e.g. "trace call graphs, summarize purpose and mechanism, flag surprising behavior") to raise specificity.

Add an explicit trigger clause such as "Use when the user wants to understand what code does or how a feature works" inside the description.

Broaden natural trigger terms ("what does this do", "how does this work", "explain this function") to improve distinctiveness and trigger coverage.

Dimension	Reasoning	Score
Specificity	"Read and explain code or a flow" names the domain and two concrete actions (read, explain) but does not enumerate multiple specific actions like the top anchor.	2 / 3
Completeness	The description clearly answers "what" but lacks an explicit "Use when..." trigger clause inside the description itself (the trigger lives in a separate when_to_use field), capping completeness at 2 per the guideline.	2 / 3
Trigger Term Quality	"explain" is a natural keyword, but within the description field alone coverage of common phrasings (e.g. "what does this do", "understand") is thin, so it sits at the partial-coverage level.	2 / 3
Distinctiveness Conflict Risk	Read-only explanation is a defined niche, but "understand code" overlaps with general coding assistance skills, so it could still conflict with similar skills.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: shiaho777/web-to-app
Path: app/src/main/assets/skills/explain/SKILL.md
Commit: fc7af6a

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.