miro-diagram

Use when the user wants to create or update a diagram as a widget on a Miro board they're already working on. For a brand-new, standalone diagram not tied to an existing board, use the miro-format skill instead.

1.33x

Quality

84%

Does it follow best practices?

Impact

100%

1.33x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 deliberately thin, well-organized delegation skill that correctly treats the Miro MCP server as the source of truth. It is concise and clearly structured, with only mild gaps in actionability and validation feedback given its defer-to-MCP design.

Suggestions

Add a brief note to validate the widget actually appeared on the board after the tool call (e.g., re-fetch or confirm via the MCP server) to give the workflow an explicit success checkpoint.

Include one short example of how to select among diagramming tools (e.g., a one-line cue like 'flowchart -> miro_create_flowchart') to lift actionability without hardcoding the full schema.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: a one-line summary plus a short paragraph deferring specifics to the MCP source of truth, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Concrete, actionable steps (identify board URL, identify what to diagram, pick and call the MCP tool per its schema) with gating prompts, though it intentionally defers the executable specifics to runtime MCP tool descriptions rather than giving an example call.	4 / 5
Workflow Clarity	A clearly sequenced three-step workflow with implicit checkpoints ('If missing, ask', 'Ask if unclear'), but no explicit validation or error-recovery loop around the tool call result.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references (it delegates to MCP at runtime) and well-organized sections (Workflow, When not to use), matching the simple-skill exception for progressive disclosure.	5 / 5
	Total	18 / 20 Passed

Description

82%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 focused, well-structured description that pairs a concrete trigger with explicit boundary guidance against a sibling skill. Its only weakness is that the named actions (create/update) are generic rather than enumerating the diagramming capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain (Miro board diagrams) with two concrete actions ('create or update a diagram as a widget'), but coverage is limited to those generic verbs rather than a comprehensive list of diagramming operations.	3 / 5
Completeness	Explicitly answers both what ('create or update a diagram as a widget on a Miro board') and when ('Use when the user wants to create or update a diagram...') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Natural user phrases like 'create or update a diagram', 'widget on a Miro board', and 'Miro board' are present and likely to be said, though synonym coverage is thin for so narrow a domain.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (widget on an existing board) and explicitly disambiguates from the sibling miro-format skill for standalone diagrams, minimizing wrong-skill triggering.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: claude-plugins/miro/skills/miro-diagram/SKILL.md
Commit: c2494b2

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.