CtrlK
BlogDocsLog inGet started
Tessl Logo

miro-code-explain-on-board

Use when the user wants to explain or visualize a codebase on a Miro board — produces a minimal, notation-correct set of architecture / structure / behavior diagrams (flowchart, UML class, UML sequence, ERD) plus a short companion document, grounded in real repo artifacts.

75

Quality

92%

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

The canonical home for this skill is miro-code-explain-on-board in miroapp/miro-ai

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A well-structured, highly actionable skill body with a clear sequenced workflow, explicit validation checkpoints, and clean progressive disclosure through one real reference file. Minor tightening of the prose in a few workflow steps would push conciseness to the top anchor.

Suggestions

Tighten the step 6 reflow-loop description into a compact checklist form to reduce prose and lift conciseness to the top anchor.

Consider compressing the 'Core diagramming principles' inline essentials now that the full ruleset lives in the reference, since some R-rules are restated in step 4 checks.

DimensionReasoningScore

Conciseness

The body is dense with actionable rules and assumes Claude's competence about Mermaid/Miro rather than explaining basics, though a few sections (e.g., the reflow-loop prose in step 6) could be tightened further.

4 / 5

Actionability

Gives concrete, executable guidance: exact node shape syntax (`id[Label]`), a named banned-verb list, explicit budgets (10–15 nodes, 1600×900 pitch), and specific widget types covering the common diagramming cases.

5 / 5

Workflow Clarity

An 8-step numbered workflow (0–7) with mandatory pre-compilation checks (step 4), a final shape audit, and a reflow feedback loop that iterates from the latest result_svg — explicit validation checkpoints and error recovery for the quasi-destructive board writes.

5 / 5

Progressive Disclosure

The essentials of the R1–R9/H1–H4 ruleset are inlined while the full ruleset is clearly signaled and offloaded to a single one-level-deep reference (`references/diagramming-principles.md`, verified present), keeping the overview navigable.

5 / 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.

A strong, third-person description that clearly states both capability and trigger, with concrete diagram-type coverage and a distinct niche. It could broaden trigger-term synonyms slightly to capture more natural phrasings.

Suggestions

Add a few natural synonyms to the trigger phrase (e.g., 'architecture diagram', 'draw', 'map this repo') so it surfaces for a wider range of user requests.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — producing notation-correct flowchart, UML class, UML sequence, and ERD diagrams plus a companion document, grounded in real repo artifacts — giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both what (a minimal set of notation-correct diagrams plus a companion document) and when ('Use when the user wants to explain or visualize a codebase on a Miro board') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Natural phrases like 'explain or visualize a codebase on a Miro board' map well to user requests, but common synonyms such as 'architecture diagram', 'draw', or 'diagram this repo' are not covered.

4 / 5

Distinctiveness Conflict Risk

The Miro-board-plus-codebase-diagrams niche is narrow and the triggers are distinct, leaving minimal overlap risk with other skills.

5 / 5

Total

19

/

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
miroapp/miro-ai
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.