CtrlK
BlogDocsLog inGet started
Tessl Logo

html-diagram

Direct-invocation specialist for self-contained HTML diagrams whose layout, notation, and interaction clarify relationships, sequence, topology, state, hierarchy, or quantitative structure. Use when the user explicitly invokes html-diagram or the broad html skill routes a diagram request here. Do not activate independently from a general request.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a concise, well-structured instruction skill that leads the reader from model selection through rendering choices to a verification checklist without over-explaining. Its only soft spot is that verification guidance is a checklist rather than an explicit error-recovery feedback loop.

Suggestions

Tighten the 'Build and verify' section into an explicit validate-then-fix-retry loop so errors during inspection have a clear recovery path.

Add one minimal inline HTML/SVG skeleton or concrete parameter hint to lift actionability from design guidance toward copy-paste-ready output.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: no padding, no explanations of concepts Claude already knows, and every line (form selection, rendering guidance, verification checks) earns its place.

5 / 5

Actionability

Provides concrete, decision-level guidance (which form for which question, specific rendering choices, an explicit verification checklist) but stays at design-instruction level rather than executable code, which is appropriate yet leaves minor gaps.

4 / 5

Workflow Clarity

A clear sequence (choose model -> choose rendering -> build and verify) with verification checkpoints in the final section, though the verify step is a checklist rather than an explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

A short, single-purpose skill under 50 lines with well-organized sections and an optional one-level-deep reference to design-artifact; no monolithic walls or nested references, so it earns the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

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

The description is strong: it states a concrete capability, gives explicit trigger guidance, and includes boundary language that minimizes conflict with sibling skills. Its main weakness is trigger-term breadth, covering 'diagram' and 'html-diagram' but omitting common synonyms users would naturally say.

Suggestions

Broaden trigger terms to include natural synonyms users say, such as 'diagrams', 'flowchart', 'visualization', or 'schematic'.

Consider naming a concrete output action (e.g. 'Generate', 'Render') alongside the specialist framing to strengthen specificity.

DimensionReasoningScore

Specificity

Names the domain ('self-contained HTML diagrams') and enumerates specific structural forms it clarifies ('relationships, sequence, topology, state, hierarchy, or quantitative structure'), giving several concrete capabilities with only minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both 'what' (builds self-contained HTML diagrams clarifying structural relationships) and 'when' ('Use when the user explicitly invokes html-diagram or the broad html skill routes a diagram request here') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes the natural term 'diagram' and the invocation phrase 'html-diagram', but lacks common synonyms and variations users might say (e.g. 'diagrams', 'chart', 'flowchart', 'visualization').

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche and actively reduces conflict risk with 'Do not activate independently from a general request' and explicit routing guidance from the broad html skill.

5 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
plannotator/effective-html
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.