CtrlK
BlogDocsLog inGet started
Tessl Logo

diagram-generation

Generate self-contained HTML architecture diagrams. Use when creating visual diagrams for PRs, task plans, or architectural explanations.

60

Quality

71%

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 ./.agents/skills/diagram-generation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 skill body is concise and well-organized with useful gotchas, but its actionability and progressive disclosure are undermined by references to style-guide.md and template.md that are not present in the bundle, and the generation workflow lacks an explicit sequenced procedure with validation.

Suggestions

Provide the missing style-guide.md and template.md bundle files referenced in the body, or inline the essential template/HTML scaffolding so the skill is self-contained and actionable.

Add a short numbered generation workflow (e.g. pick applicable sections → build from template → write to the resolved path → open/verify in browser) with an explicit verification checkpoint.

Confirm the html2canvas SRI hash and toBlob null-check details live in an accessible location rather than only being described as 'see template.md', since that file is currently absent.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — every section (Output, Required Sections, Section Selection, Gotchas) earns its place with no padding or explanation of concepts Claude already knows, matching the top anchor.

5 / 5

Actionability

Concrete guidance exists (output path, required sections, section-selection rules, gotchas), but the actual executable mechanics are deferred to "style-guide.md" and "template.md", which are referenced but not present in the bundle — a key gap that leaves the guidance incomplete.

3 / 5

Workflow Clarity

Pieces of the workflow are present (section selection, output location, reference files), but there is no explicit sequenced procedure or validation checkpoint, fitting the anchor for steps present with implicit sequence and missing checkpoints.

3 / 5

Progressive Disclosure

The body is well-structured with a dedicated "Reference Files" section that clearly signals one-level-deep references, but the referenced files (style-guide.md, template.md) do not exist in the bundle, so the disclosed navigation is broken in practice.

3 / 5

Total

14

/

20

Passed

Description

78%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 well-formed, answering both what the skill does and when to use it with concrete, natural trigger phrases. Its main limitation is specificity — it names only one action (generate) rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

Quotes "Generate self-contained HTML architecture diagrams" — names the domain and one concrete action (generate), but lists no additional specific actions, matching the anchor for naming a domain with 1-2 concrete actions rather than the several required for a 4.

3 / 5

Completeness

Explicitly answers both "what" ("Generate self-contained HTML architecture diagrams") and "when" ("Use when creating visual diagrams for PRs, task plans, or architectural explanations") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Quotes "visual diagrams for PRs, task plans, or architectural explanations" — good coverage of natural terms a user would say, but lacks synonyms or file extensions that would push it to comprehensive (5).

4 / 5

Distinctiveness Conflict Risk

The niche of "self-contained HTML architecture diagrams" for PRs and plans is mostly distinct, but the broad term "diagrams" carries minor overlap risk with other general diagramming skills, keeping it just below the minimal-conflict anchor.

4 / 5

Total

16

/

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: 2 missing

Warning

Total

15

/

16

Passed

Repository
comet-ml/opik
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.