CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

explain-diff

Produce a rich, interactive, self-contained HTML explanation of a code change — background, intuition with diagrams, a code walkthrough, and a comprehension quiz. Use when the user asks to explain a diff, branch, commit range, or PR, wants to understand a change before reviewing or merging it, or wants to pay down cognitive debt on code an agent wrote.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

A well-crafted, highly actionable instruction-only body with concrete commands, exact output-placement and escaping rules, and an explicit pre-save validation checkpoint. Its main defects are a broken bundle reference (MICROWORLDS.md is cited but absent) and mild over-writing in the motivational opening. Workflow ordering is clear but distributed across sections rather than presented as one sequence.

Suggestions

Ship MICROWORLDS.md with the bundle (in references/) or inline its essentials — the body delegates the microworld catalog, when-to-use heuristics, and honesty rules to a file that does not exist.

Compress the two opening motivation paragraphs and the Kleppmann style note to one or two lines each; the stance ("it teaches; it never judges") is the only load-bearing part.

Present the execution order as a short ordered list (resolve target → explore background → draft sections → pre-save scan of both escaping sinks → write outside repo and report the path) so the workflow reads as one sequence.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific, non-obvious instruction (exact CSP directive, filename pattern, per-sink escaping rules, quiz randomization) with almost no explanation of concepts Claude already knows. It is not 5 because the two opening motivation paragraphs on cognitive debt and the Kleppmann-style flourish could be trimmed to a line each without losing guidance value.

4 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: concrete git commands for merge-base resolution, an exact output path pattern ($TMPDIR/YYYY-MM-DD-explanation-<slug>.html with a slug charset), copy-paste-ready CSP policy, per-sink escaping rules, and a defined pre-save validation scan. It is not 4 because the specific commands and patterns leave no gaps for the common cases.

5 / 5

Workflow Clarity

The sequence is present and ordered (resolve target → explore background → build the four sections → write outside the repo → report the path) and includes an explicit validation checkpoint ("Before saving the file, scan each code block... confirm its CSS includes white-space: pre or pre-wrap", extended to both escaping sinks). It is not 5 because the process order must be assembled across the Scope/Sections/Format sections rather than being laid out as a single workflow, and there is no error-recovery loop around the pre-save scan.

4 / 5

Progressive Disclosure

The main file is well sectioned, and its single external reference is clearly signaled ("[MICROWORLDS.md](./MICROWORLDS.md) carries the catalog of world types, the when-to-use heuristics, and the honesty rules"), but that file does not exist in the bundle — no references/, scripts/, or assets/ directories are present, so the delegated microworlds material is unreachable. It is not 4 because a dead-end reference on which the skill leans for a whole output modality is more than a minor organization gap; it is not 2 because the body itself is well structured and self-contained apart from that one link.

3 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

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

An exemplary description: third-person voice, a concrete multi-part "what", and an explicit "Use when" clause with natural trigger phrases covering diff, branch, commit range, and PR. It is well positioned against adjacent review skills and contains no padding beyond the mild "rich, interactive" flourish.

DimensionReasoningScore

Specificity

The description names the concrete artifact ("self-contained HTML explanation") and enumerates its full deliverable — "background, intuition with diagrams, a code walkthrough, and a comprehension quiz" — which comprehensively covers what the skill produces. It is not score 4 because coverage of the output is complete rather than having minor gaps.

5 / 5

Completeness

Both halves are explicit: the "what" ("Produce a rich, interactive, self-contained HTML explanation... background, intuition... code walkthrough, and a comprehension quiz") and the "when" ("Use when the user asks to explain a diff, branch, commit range, or PR, wants to understand a change before reviewing or merging it...") with concrete trigger phrases. This matches the anchor-5 good example pattern exactly.

5 / 5

Trigger Term Quality

"explain a diff, branch, commit range, or PR" plus "wants to understand a change before reviewing or merging it" covers all the natural ways a user would name this need, including synonyms for the change target. "Pay down cognitive debt" is mild jargon, but the surrounding trigger phrases are exactly what users would say, so this sits above score 4's "a few natural terms missing".

5 / 5

Distinctiveness Conflict Risk

The description carves a clear pre-review niche ("wants to understand a change before reviewing or merging it") distinct from review or fix skills; its triggers ("explain a diff/PR") would not fire for a review request. Minimal conflict risk with related review-oriented skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 possibly missing (./MICROWORLDS.md)

Warning

Total

15

/

16

Passed

Repository

agranado2k/google-books-clojure

Path

.claude/skills/explain-diff/SKILL.md

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.