miro-diagram

Use when the user wants to create or update a diagram on a Miro board.

2.37x

Quality

48%

Does it follow best practices?

Impact

56%

2.37x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./claude-plugins/miro/skills/miro-diagram/SKILL.md

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is admirably concise and correctly delegates to the MCP server as the authoritative source, but it sacrifices actionability almost entirely. It reads more like a meta-instruction ('go figure it out from the MCP server') than a skill that teaches Claude how to perform a specific task. The workflow is too generic to be meaningfully helpful.

Suggestions

Add at least one concrete example showing a sample tool call with realistic parameters (e.g., creating a flowchart on a board), even if the MCP server is the source of truth for the full schema.

Include a validation step in the workflow, such as confirming the board URL is accessible or verifying the diagram was created successfully.

List the most common diagram types and their corresponding MCP tool names so Claude doesn't have to discover them at runtime every time.

Dimension	Reasoning	Score
Conciseness	The skill is very lean—no unnecessary explanations of what Miro is or how MCP works. It correctly defers to the MCP server as the source of truth rather than duplicating documentation. Every sentence serves a purpose.	3 / 3
Actionability	The skill provides no concrete commands, code, tool names, or examples. It essentially says 'explore the MCP server and use whatever you find,' which is vague direction rather than executable guidance. There are no specific tool names, parameter examples, or sample calls.	1 / 3
Workflow Clarity	There is a basic 3-step sequence, but it lacks validation checkpoints (e.g., confirming the board exists, verifying the diagram was created successfully). The steps are also quite generic—step 3 is essentially 'do the thing.'	2 / 3
Progressive Disclosure	For a simple, short skill with no bundle files and under 50 lines, the content is appropriately organized with a clear overview and workflow section. No external references are needed given the skill's reliance on the MCP server as the source of truth.	3 / 3
	Total	9 / 12 Passed

Description

40%

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 correctly includes a 'Use when...' clause and mentions the specific platform (Miro), which provides some distinctiveness. However, it is too sparse on concrete capabilities — it doesn't describe what types of diagrams, what specific actions are supported, or what elements can be manipulated. The trigger term coverage is narrow, missing many natural terms users might use.

Suggestions

Add specific concrete actions and diagram types, e.g., 'Creates and updates diagrams on Miro boards, including flowcharts, mind maps, org charts, adding shapes, connectors, and text labels.'

Expand trigger terms in the 'Use when...' clause to include natural variations like 'flowchart', 'whiteboard', 'visual diagram', 'Miro', 'shapes', 'connectors'.

Rewrite to clearly separate the 'what it does' from the 'when to use it', e.g., 'Creates flowcharts, mind maps, and visual diagrams on Miro boards using shapes, connectors, and labels. Use when the user mentions Miro, whiteboard diagrams, or wants to visually map out processes.'

Dimension	Reasoning	Score
Specificity	The description mentions 'create or update a diagram' which names two actions but remains vague about what kinds of diagrams, what specific operations are involved, or what capabilities exist. It lacks concrete details like 'flowcharts, mind maps, org charts, add shapes, connectors, text labels.'	1 / 3
Completeness	It has a 'Use when...' clause that addresses the 'when' question, but the 'what does this do' part is very thin — it only says 'create or update a diagram' without describing specific capabilities or actions the skill performs.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'diagram', 'Miro board', 'create', and 'update' that users might naturally say. However, it misses common variations like 'flowchart', 'whiteboard', 'shapes', 'connectors', 'visual', 'mind map', or file-related terms.	2 / 3
Distinctiveness Conflict Risk	'Miro board' is a fairly distinct trigger that narrows the domain, but 'diagram' is broad enough to potentially overlap with other diagramming skills (e.g., Lucidchart, draw.io, or general diagram generation skills). More specificity about Miro-specific features would help.	2 / 3
	Total	7 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: miroapp/miro-ai
Commit: 85c2c73

Reviewed: 26 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.