CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

anatomy

Explain an idea as an interactive isometric machine figure.

Quality

72%

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 ./optional-skills/creative/anatomy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 content is an exceptionally actionable, tightly sequenced working manual with genuine validation loops and concrete commands throughout, held back mainly by length and by inlined detail that duplicates the reference files. The missing kit/ and examples/ directories in the bundle are the one integrity gap an executor would actually trip over.

Suggestions

Tighten the examples section: compress the narrative scene descriptions into what each example demonstrates and its part counts, moving the rest into a short per-example README.

Trim the inline WebGL and 3D rule lists to the few load-bearing rules and point to references/webgl.md and references/3d.md for the remainder, as is already done for craft rules.

Ship the referenced kit/ and examples/ files (or correct the paths), since the setup instructions copy from $SKILL_DIR/kit and every example's build.mjs imports them.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific craft rules and avoids explaining generic concepts, but at ~200 lines it includes narrative flourishes in the examples section (e.g. the arcade cabinet's coin travelling "down the coin chute at the speed a rolling disc reaches on a 30° slope") and full WebGL/3D rule sets inlined alongside the dedicated reference files that already cover them — "mostly efficient but could be tightened" rather than minor-trim territory.

3 / 5

Actionability

Guidance is fully executable: a copy-paste-ready workspace setup block (mkdir/cp/node build.mjs), exact verification commands ("node scripts/lines.mjs page.html --out shots/lines.png ... must print `line ends: 0`"), precise function signatures ("fitProjection(points, width, height, { pad, azimuth })"), numeric craft parameters (bevels 0.4–1.6, screws 0.4–0.55), and per-example build patterns covering the common paths. Not 4 because no step is left at hint level.

5 / 5

Workflow Clarity

A 10-step workflow with explicit sequencing and validation checkpoints ("Run the audit to zero", "Run the line check to zero", 4× close-ups in both themes), error-recovery feedback loops ("Fix an interlock in the geometry, never with a key bias"; iterate until the example-comparison questions pass), and time-tracking with escalation when a step runs past twice its estimate.

5 / 5

Progressive Disclosure

References are well-signaled and one level deep, each annotated in the References section with when to read it ("Read these as you need them"), and all eight referenced files exist. However, the body inlines substantial kit API detail and rule sets that parallel the dedicated reference files, and every referenced `kit/` and `examples/` path is missing from the actual bundle, so structure falls short of the fully split, easily navigable 5.

4 / 5

Total

17

/

20

Passed

Description

53%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 short, third-person, and clearly communicates a distinctive niche, but it captures only a single action and omits any explicit trigger guidance or natural synonyms (diagram, illustration, explainer). Adding a "Use when..." clause with the common phrasings users would say would lift the completeness and trigger-term dimensions.

Suggestions

Add a trigger clause, e.g. "Use when the user asks to explain, illustrate, or visualize a concept, mechanism, or system, or wants an interactive isometric diagram/figure rather than boxes and arrows."

Include common synonyms users would naturally say (diagram, illustration, explainer, visualization) and the output formats (standalone HTML, SVG, React/Next.js components) in the description.

Keep the one-sentence length but make the sentence do double duty: state both what the skill produces and when it applies.

DimensionReasoningScore

Specificity

"Explain an idea as an interactive isometric machine figure" names a specific domain and one concrete action (building an interactive isometric machine figure), but does not list the several specific actions or output formats (HTML, SVG, React) that a 4 would require, and is far above the generic single-verb level of 2.

3 / 5

Completeness

The "what" is clear (explain an idea as an interactive isometric machine figure), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline; the "when" is only weakly implied.

3 / 5

Trigger Term Quality

"interactive", "isometric", "machine figure" and "explain an idea" are relevant and natural keywords, but common user phrasings a person would actually say — "diagram", "illustration", "explainer", "visualization", "SVG" — are missing, matching the "some relevant keywords but missing common variations or synonyms" anchor.

3 / 5

Distinctiveness Conflict Risk

"Interactive isometric machine figure" carves out a clear niche with minimal overlap, but because the when-to-use guidance is thin, requests phrased as "draw me a diagram" or "explain how this works" could also reach general diagramming skills — a minor overlap risk typical of a 4 rather than the distinct-triggers confidence of a 5.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/creative/anatomy/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.