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, dense workflow skill: lean body, explicit validation checkpoints and a feedback loop, and clean one-level-deep progressive disclosure. The only minor gap is reliance on MCP-loaded guidance rather than an inline copy-paste Mermaid example.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — no padding about what UML/ERD/flowchart are; rules are referenced by ID with only the essentials inline and the full ruleset deferred to a reference file.

5 / 5

Actionability

Concrete, executable authoring guidance — exact node syntax, banned shapes, edge-label verb lists, layout coordinate math, widget attributes, and XML-escaping rules — but relies on MCP-loaded guidance for full Mermaid mechanics rather than providing a complete inline worked example.

4 / 5

Workflow Clarity

Clearly sequenced seven-step workflow with explicit mandatory pre-compilation checks, a final shape audit, and a reflow feedback loop that iterates from the latest result_svg.

5 / 5

Progressive Disclosure

SKILL.md is an overview pointing to one real, well-signaled reference file (references/diagramming-principles.md) one level deep, with the full R/H ruleset appropriately split out and external format guidance loaded on demand.

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 description: concrete, third-person, with an explicit 'Use when' trigger and a distinctive Miro-specific niche. Only minor gap is slightly thinner natural-keyword synonym coverage.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — four named diagram types (flowchart, UML class, UML sequence, ERD) plus a companion document, grounded in repo artifacts — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (produces notation-correct diagrams plus a companion doc) 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

Includes natural phrases users would say ('explain or visualize a codebase on a Miro board', 'architecture...diagrams') with good coverage, but misses some synonyms and lacks a file-format-style trigger; not quite comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (Miro-board codebase visualization) with distinctive Miro-specific triggers, giving 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.