CtrlK
BlogDocsLog inGet started
Tessl Logo

diagram

Use the smallest visual when prose must carry structure—control flow, call depth, module ownership, or change shape: pseudocode, call tree, component/file tree, Mermaid diagram, or diff. Skip it when prose already answers the question.

75

Quality

94%

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

96%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 an excellent, disciplined piece of skill writing: every exemplar is minimal and purposeful, the decision rules are unambiguous, and the artifact escalation is explicitly bounded. The only structural note is that the vocabulary section is a self-contained exemplar catalog that could be split out if the skill grows.

Suggestions

If the vocabulary of views ever grows, move the exemplar blocks into a single reference file (e.g. references/views.md) and keep only the one-line definitions inline in SKILL.md.

DimensionReasoningScore

Conciseness

Lean throughout: each view gets one short exemplar and a single-line rationale ('Pseudocode — logic without language noise'), with zero space spent explaining concepts Claude already knows. Every token earns its place.

5 / 5

Actionability

Concrete exemplars for every view type and copy-paste-ready commands for the escalation path — 'Open it with the platform opener (start on Windows, open on macOS, xdg-open on Linux)'. The guidance is specific enough to execute without interpretation.

5 / 5

Workflow Clarity

A single unambiguous decision path: prose first, then 'pick the smallest view', escalating to exactly 'one focused HTML file' when 'text runs out' — with 'Pick one view; two at most' bounding the output. As a simple single-purpose skill with no risky operations, the flow is fully clear.

5 / 5

Progressive Disclosure

Sections are well organized ('The vocabulary', 'When text runs out', 'Discipline') and nothing needs external references, but the body runs ~120 lines — above the under-50-line threshold that would justify a top score on organization alone, and the exemplar gallery could live in a reference file.

4 / 5

Total

19

/

20

Passed

Description

92%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: it states exactly what the skill does, when to use it, and when not to, in a single tight sentence with concrete trigger vocabulary. Only minor headroom exists in adding a few more natural synonyms.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete visual forms — 'pseudocode, call tree, component/file tree, Mermaid diagram, or diff' — giving comprehensive, specific coverage of what the skill produces rather than vague capability language.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' is 'Use the smallest visual… pseudocode, call tree, component/file tree, Mermaid diagram, or diff' and the 'when' is the explicit trigger list plus the skip condition 'Skip it when prose already answers the question.'

5 / 5

Trigger Term Quality

Good natural trigger terms ('control flow', 'call depth', 'module ownership', 'change shape', 'Mermaid diagram', 'diff'), but common user phrasings like generic 'diagram', 'visualize', or 'architecture' are absent.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (choosing the smallest structural visual over prose) with distinct triggers like 'call depth' and 'module ownership', and the explicit skip boundary minimizes conflict with general visualization or chart skills.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Yeachan-Heo/oh-my-claudecode
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.