CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

diagram-validated

Cria diagramas tecnicos e valida sua sintaxe e coerencia. Trigger em: "diagrama de arquitetura", "diagrama de classe", "diagrama de sequência", "UML", "diagrama de deployment", "diagrama ER", "state machine diagram", "gerar diagrama técnico", "diagrama com validação", "SVG determinístico", "diagrama fica desalinhado", "roteamento ortogonal", "geometry-safe diagram", "diagrama de componentes".

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

Quality

Content

62%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's greatest strength is its workflow: a validate→render→check→look protocol with explicit checkpoints, anti-patterns, and an evidence-of-completion checklist that embodies 'avalie, não afirme'. It is dragged down by a Diagram Contract step with no schema or example, commands that reference an unshipped `scripts/fireworks.py`, and noticeable duplication of the ImageMagick-fidelity caveat across four sections. Solid mid-to-good content that would rise sharply with a bundled script and a contract example.

Suggestions

Ship `scripts/fireworks.py` (or another executable engine) in the bundle's `scripts/` directory so the validate/render/check commands can actually run.

Add a minimal Diagram Contract JSON example (one container, two nodes with `kind`, one arrow with `flow` and port anchors) to make step 1 executable instead of prose-described.

State the ImageMagick fidelity caveat once — in 'Governanca Global' — and have 'Anti-Padroes', 'Evidencia', and 'Fontes' reference it in a single line instead of restating it; merge 'Integracao com Pipeline' into 'Handoff' to remove the duplicated skill-10/38 relationships.

DimensionReasoningScore

Conciseness

The body is mostly tight — the protocol steps are command-driven with no padding — but the same ImageMagick fidelity caveat (foreignObject/filter/embedded fonts untested) is repeated four times across 'Governanca Global', 'Anti-Padroes', 'Evidencia de Conclusao', and 'Fontes', and 'Integracao com Pipeline' restates the skill-10/38 relationships already given in 'Handoff'. That places it at 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 4's 'minor instances of over-explanation', since whole duplicated sections could be cut.

3 / 5

Actionability

The protocol supplies four concrete, fully-argumented commands (validate/render/check, `magick diagrama.svg diagrama.png`), but the central artifact — the Diagram Contract JSON of step 1 — has no example or schema, only a prose sketch ('containers, nós com `kind`, setas com `flow`'), so the reader must invent the IR format. Additionally, every command invokes `scripts/fireworks.py`, yet no `scripts/` directory exists in the bundle, so the commands are not executable as shipped — 'concrete guidance but incomplete, missing key details' rather than 'mostly executable with minor gaps'.

3 / 5

Workflow Clarity

The six-step protocol is explicitly sequenced with validation checkpoints baked in: validate-before-render ('falha rápido em vez de gerar SVG malformado'), a geometry check, and a mandatory visual readback ('Nunca pular este passo e declarar o diagrama pronto só porque o `check` passou'), plus error-recovery guidance (use `layout.json` to 'debugar um roteamento inesperado') and a completion checklist in 'Evidencia de Conclusao'. This matches the top anchor: clear sequence, explicit validation steps, feedback guidance, and a checklist for a complex process; nothing significant is missing.

5 / 5

Progressive Disclosure

Section structure is clear and the inline 12-style table and 14-type list are appropriately placed in the body, but the skill's referenced resources do not resolve: `scripts/fireworks.py` (the entire engine) is absent from the bundle, and the governance/policy files (`GLOBAL.md`, `policies/execution.md`, `policies/handoffs.md`, `skills/10-documenter/SKILL.md`) are also not shipped. Per the guideline to score against the actual bundle structure, references that promise content that isn't there keep this at 'some structure but could be better organized' rather than level 4's 'references mostly clear' with everything in its right place.

3 / 5

Total

14

/

20

Passed

Description

70%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-populated trigger clause with natural phrases in both Portuguese and English, giving it solid completeness and distinctiveness. Its main weakness is a terse 'what' — only two verbs with no mention of outputs or the breadth of supported diagram types — plus a few jargon-y triggers and missing common variants like 'flowchart'. Overall a solid, above-mid description with room to sharpen the capability statement.

Suggestions

Expand the 'what' clause to state concrete outputs and scope, e.g. 'Gera SVG determinístico + PNG de verificação para 14 tipos UML e diagramas de arquitetura/fluxo, e valida geometria (setas órfãs, sobreposição, canvas) antes de declarar pronto'.

Add missing natural trigger variants: 'diagrama de fluxo', 'flowchart', 'ERD', 'entity relationship', 'diagrama de atividades'.

Drop or de-emphasize insider-jargon triggers like 'geometry-safe diagram' and 'roteamento ortogonal' that a user would rarely say, in favor of more user-natural phrasing.

DimensionReasoningScore

Specificity

The description states exactly two concrete actions — "Cria diagramas tecnicos" and "valida sua sintaxe e coerencia" — which matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive' (e.g., no mention of the SVG/PNG outputs or the 14 supported UML types). It is above level 2 because the domain is named precisely and both actions are real capabilities, not generic filler, but below level 4 because 'several specific actions' are not listed and 'valida sua sintaxe e coerencia' is abstract about what validation entails.

3 / 5

Completeness

Both halves are present: the 'what' ("Cria diagramas tecnicos e valida sua sintaxe e coerencia") and an explicit 'when' clause ("Trigger em: ...") with 14 concrete trigger phrases, so the level-3 cap for missing trigger guidance does not apply. It does not reach level 5 because the 'what' is thin — it never states the deliverables (deterministic SVG, PNG readback) or the scope (14 UML types plus architecture/flow), leaving the capability description less concrete than the trigger side.

4 / 5

Trigger Term Quality

The trigger list has strong natural coverage in both Portuguese and English — "diagrama de arquitetura", "diagrama de classe", "diagrama de sequência", "UML", "diagrama ER", "state machine diagram", "gerar diagrama técnico", "diagrama fica desalinhado" — phrases users would genuinely say. It falls short of level 5 because common variations are missing ("diagrama de fluxo", "flowchart", "ERD", "entity relationship", "diagrama de atividades") and a few entries like "geometry-safe diagram" and "roteamento ortogonal" are insider jargon a user would rarely utter; it is clearly above level 3, where only some relevant keywords are present.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche — technical/UML diagrams with validation rigor — and nearly all triggers ("UML", "diagrama ER", "diagrama de deployment") would not plausibly route to another skill. It sits below level 5 because "SVG determinístico" and generic diagram wording could overlap with a general image-generation or drawing skill, and nothing in the description itself distinguishes this from decorative SVG illustration.

4 / 5

Total

15

/

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

allowed_tools_field

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

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

13

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/76-diagram-validated/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.