CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-documentation-code-explain

Explain complex code through clear narratives, visual diagrams, and step-by-step breakdowns that make difficult concepts understandable. Use when someone needs to understand how unfamiliar or complex code works.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/code-documentation-code-explain/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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.

The body is well-sectioned and appropriately brief, with clear use/do-not-use boundaries, but all substantive guidance remains high-level directives. Its one concrete escape hatch — the implementation playbook reference — is a dangling pointer to a file missing from the bundle, which undermines both actionability and navigation.

Suggestions

Fix the dangling reference: either add the actual resources/implementation-playbook.md to the bundle (or move it to a standard references/ directory and update both the Instructions bullet and Resources section) so detailed examples resolve.

Replace directive-only bullets with one small worked example inline (e.g., a short mermaid/ASCII flow diagram or a sample walkthrough structure) so guidance is concrete even before opening the playbook.

Cut the redundant Context and Requirements sections, which restate the description and add no instruction, tightening token efficiency.

DimensionReasoningScore

Conciseness

The body is short and mostly bulleted, but the "Context" section ("The user needs help understanding complex code sections... Focus on clarity, visual aids, and progressive disclosure of complexity") merely restates the frontmatter description, and "Requirements: Take the requirements, target, and scope from the user's request" is content-free filler. Both could be trimmed, matching anchor 3 rather than the minor-trim profile of anchor 4.

3 / 5

Actionability

The instructions give a recognizable procedure ("Assess structure, dependencies, and complexity hotspots", "Explain the high-level flow, then drill into key components") but stay at the directive level with no worked example, diagram format, or template — the concrete detail is deferred to "resources/implementation-playbook.md". That deferral leaves the guidance incomplete in-situ, matching anchor 3 ('missing key details') rather than anchor 4.

3 / 5

Workflow Clarity

A rough sequence exists (assess → high-level flow → drill into components → pitfalls), but it is presented as unnumbered bullets with ordering only implied by one "then", and there are no checkpoints confirming the explanation landed (e.g., verifying comprehension or covering the user's specific question). This matches anchor 3 (sequence present, checkpoints implicit); no destructive/batch cap applies since the task is explanatory.

3 / 5

Progressive Disclosure

Section structure is clean and the external reference is clearly signaled twice ("If detailed examples are required, open resources/implementation-playbook.md" plus a Resources section), but the referenced file does not exist in the skill bundle — no resources/ directory is present — so the one-level-deep pointer is broken. This lands at anchor 3 (references present but the organization does not actually resolve) rather than 4.

3 / 5

Total

12

/

20

Passed

Description

83%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.

A strong description that clearly states both what the skill does and when to use it, with concrete actions and natural trigger phrasing in third-person voice. Minor room for improvement in keyword coverage and distinguishing from adjacent teaching/documentation skills.

DimensionReasoningScore

Specificity

"Explain complex code through clear narratives, visual diagrams, and step-by-step breakdowns" names several concrete actions (narratives, diagrams, breakdowns). Not 5 because coverage has minor gaps (e.g., onboarding walkthroughs and pattern teaching from the body are absent); not 3 because it lists more than 1-2 concrete actions.

4 / 5

Completeness

The 'what' is explicit ("Explain complex code through clear narratives, visual diagrams, and step-by-step breakdowns") and the 'when' is an explicit concrete trigger ("Use when someone needs to understand how unfamiliar or complex code works"). Anchor 4 would require the 'when' to be vague or improvable, but this trigger names the user situation directly, matching anchor 5.

5 / 5

Trigger Term Quality

Natural terms like "explain complex code", "understand how unfamiliar or complex code works" match what users would say (e.g., "how does this code work?"). A few natural variations are missing ("walkthrough", "what does this code do", "onboarding"), matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The explanation/understanding niche ("explain complex code", "understand how unfamiliar or complex code works") is distinct from implementation or review skills. Minor overlap risk remains with closely related skills like code documentation or general teaching skills; anchor 5 would require a fully distinct trigger set.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/code-documentation-code-explain/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.