CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

anatomy

Cria figuras isometricas para explicar anatomia de sistemas. Trigger em: "desenhar diagrama isométrico", "figura isométrica", "isometric svg", "desenho técnico Linear-style", "isometric explainer", "diagrama de arquitetura em máquina", "ilustração isométrica", "interativo em svg", "shader webgl no svg", "anatomy diagram".

Quality

81%

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

77%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 strong operational document: a well-sequenced construction protocol with explicit validation checkpoints, concrete kit primitives, and clear when-to-use/when-not-to-use boundaries. Its main weaknesses are the absence of an inline executable example and a bundle whose referenced paths (kit/, policies/, examples/) and half of its reference files are not actually reachable or surfaced.

Suggestions

Surface all files in references/ from the body (motion.md, react.md, verify.md, walkthrough.md are currently undiscoverable), for example by extending the context-manager routing list or the relevant protocol steps.

Resolve dangling bundle paths: either ship kit/, policies/, GLOBAL.md, examples/, and LICENSE-ANATOMY with the skill or clearly state that they live in the parent skill collection so navigation doesn't dead-end.

Include one short, complete inline code example (e.g. a minimal build.mjs composing a few kit primitives into a figure) so the common case is copy-paste executable without opening references/kit.md.

DimensionReasoningScore

Conciseness

The body is dense and directive — rules, commands, and parameters with no explanation of concepts Claude already knows — e.g. "**Quatro tons automáticos:** preserve a iluminação calculada por `extrude`". Minor over-length in the Handoff/Integração com Pipeline sections and some wordy phrasing keep it below the lean-and-efficient top anchor.

4 / 5

Actionability

Concrete, mostly executable guidance throughout: named kit primitives (`slabOf`, `cylinder`, `extrude`, `knurl`, `coil`), exact commands (`node build.mjs --audit`, `node scripts/lines.mjs`), and specific parameters (azimuth 45°, elevation 30° via `fitProjection()`, 1.5 radii clearance). It stops short of a 5 because no complete, copy-paste-ready code example composing a figure is shown inline — composition is deferred to kit/ and references/.

4 / 5

Workflow Clarity

A clearly sequenced 10-step "Protocolo de Construção" is paired with an explicit validation section ("Evidência de Conclusão") requiring the audit to return zero issues, the line validator to confirm zero disconnected lines, 4x zoom inspection, and a live browser check before delivery — a full feedback loop matching the top anchor.

5 / 5

Progressive Disclosure

Scored against the actual bundle: cited references (`references/craft.md`, `kit.md`, `webgl.md`, `3d.md`) and `scripts/lines.mjs` exist and are one level deep, but the body also points to `kit/iso-kit.mjs`, `kit/audit.mjs`, `kit/lathe.mjs`, `kit/tube.mjs`, `kit/react/draw.tsx`, `policies/*.md`, `GLOBAL.md`, `examples/`, and `LICENSE-ANATOMY`, none of which exist in the bundle, and 4 of the 8 files in references/ (motion.md, react.md, verify.md, walkthrough.md) are never surfaced from the body. This is more than the minor organization gaps allowed at 4, but structure and signaling are present, keeping it above a 2.

3 / 5

Total

16

/

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 has an explicit, well-structured trigger clause and a distinctive niche, but the "what" is a single sentence that undersells the skill's concrete capabilities. Broadening the action list and adding a few natural synonyms would push it to the top band.

Suggestions

Enumerate the concrete outputs in the description itself (standalone HTML pages, React components, pure SVG figures, optional WebGL shader layers, geometric audit) instead of one general sentence.

Add natural trigger variations users would actually say, such as "technical illustration", "isometric drawing", "diagrama técnico", and ".svg" file references.

Consider replacing or qualifying "anatomy diagram" with something like "system anatomy diagram" to reduce collision with medical/anatomy illustration skills.

DimensionReasoningScore

Specificity

The description states one concrete action ("Cria figuras isometricas para explicar anatomia de sistemas") in a clearly named domain, but omits the several other specific capabilities the body covers (standalone HTML/React/SVG outputs, WebGL shader layers, geometric auditing). This matches the anchor for naming a domain with 1-2 concrete actions, not the level above, which requires a list of several specific actions.

3 / 5

Completeness

It clearly answers "what" (creates isometric figures to explain system anatomy) and explicitly answers "when" with a dedicated "Trigger em:" clause listing concrete trigger phrases, matching the top anchor. Not a 4 because the "when" is already fully explicit rather than in need of more specificity.

5 / 5

Trigger Term Quality

Ten explicit trigger phrases provide good bilingual keyword coverage ("desenhar diagrama isométrico", "isometric svg", "anatomy diagram", "ilustração isométrica"), but a few natural terms users would say are missing (e.g. "technical illustration", "isometric drawing") and no file extensions (.svg) appear, so it falls short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The niche (isometric physical-machine explainer diagrams in Linear style) is mostly distinct with dedicated triggers, but "anatomy diagram" risks overlap with biological/medical illustration skills and "interativo em svg" is fairly broad, giving minor conflict risk rather than minimal.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/88-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.