CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

diagram-generation

Geração de diagramas técnicos para tutoriais, artigos e documentação

Quality

63%

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

Quality

Content

63%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 delivers genuinely useful material — tool-selection tables, ready-to-use Mermaid templates, style conventions, and a verification checklist — but it is undermined by a verbatim duplication of the DALL-E/Gemini API sections, an empty 'Ferramentas Recomendadas' header, broken numbering, and a fully monolithic structure with no reference files. Tightening the duplication and splitting templates/API details into references would raise quality substantially.

Suggestions

Remove the duplicated OpenAI DALL-E and Gemini code blocks (identical content appears in both 'APIs Disponíveis' and 'Diagramas Ilustrativos (APIs de Imagem)') — keep one canonical section to cut ~50 wasted lines.

Fix structural flaws: the empty '## Ferramentas Recomendadas' header (line 17) has no content, and tool numbering is broken (Mermaid is unnumbered while PlantUML/Excalidraw are '### 2', '### 3').

Move the Mermaid template library and image-API examples into separate reference files (e.g., references/mermaid-templates.md, references/image-apis.md) so SKILL.md stays a lean overview with one-level-deep references.

Complete the Gemini code snippets by adding 'import os' before os.getenv so the examples are copy-paste executable.

DimensionReasoningScore

Conciseness

The OpenAI DALL-E and Gemini code blocks appear twice verbatim (early 'APIs Disponíveis' section and later 'Diagramas Ilustrativos'), the '## Ferramentas Recomendadas' header is empty, and numbering is broken (Mermaid unnumbered, then '### 2. PlantUML'). Most tables and templates earn their place, so it fits 'mostly efficient but includes some unnecessary content that could be tightened' rather than 'several padded sections'.

3 / 5

Actionability

Mermaid templates are copy-paste ready, the per-content-type tables give concrete tool/format decisions, and workflow steps are specific. Minor gaps: the Gemini snippets call os.getenv without importing os, and API setup (keys) is not shown, fitting 'mostly executable guidance; concrete code with minor gaps'.

4 / 5

Workflow Clarity

The 'Workflow de Criação' section lists a clear 7-step sequence ending with 'Testar renderização no destino final', and the final Checklist provides explicit verification checkpoints. It lacks an error-recovery/feedback loop, so it matches 'clear sequence with most checkpoints present; minor validation gaps' rather than 5.

4 / 5

Progressive Disclosure

Section structure is clear with well-labeled headers, but the file is a ~319-line monolith with zero external reference files; the Mermaid template library and image-API examples clearly belong in separate reference files. This sits between 'content that belongs in separate files is inlined' (2) and 'some structure but could be better organized' (3).

3 / 5

Total

14

/

20

Passed

Description

45%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 identifies the domain (technical diagram generation) and target content types, but it is a single generic clause with no concrete actions, no use-when triggers, and no distinguishing keywords like Mermaid, flowchart, or architecture diagram. It would benefit most from an explicit trigger clause and a list of concrete diagram actions.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use quando o usuário pedir fluxogramas, diagramas de arquitetura ou sequência, ou mencionar Mermaid/PlantUML/draw.io') — its absence currently caps completeness at 3.

List concrete actions instead of the generic 'Geração de diagramas' (e.g., 'Cria fluxogramas, diagramas de sequência, ER e de arquitetura com Mermaid, PlantUML, draw.io e APIs de imagem').

Include natural trigger terms and tool names users actually say — 'fluxograma', 'diagrama de arquitetura', 'Mermaid', '.drawio' — to improve trigger matching and distinctiveness from generic visualization skills.

DimensionReasoningScore

Specificity

"Geração de diagramas técnicos" names the domain but the only action stated is the generic "geração" (generation); no concrete actions like creating flowcharts, sequence diagrams, or ER models are listed, matching 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

The description has a clear 'what' (technical diagram generation for tutorials, articles, documentation) but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords are present ("diagramas técnicos", "tutoriais", "artigos", "documentação") but common natural trigger terms users would actually say are missing: "fluxograma", "arquitetura", "diagrama de sequência", "Mermaid", "draw.io", matching 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

"Diagramas técnicos" denotes a real niche, but the description would overlap with chart/dataviz/visualization skills (charts, dashboards, plots) and does not name distinct triggers like Mermaid or draw.io, matching 'Somewhat specific but could still overlap with similar skills'.

3 / 5

Total

11

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/documentation/diagram-generation/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.