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 findings from the security scan

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 is a very thin skill that essentially acts as a routing shortcut to the Miro MCP server's own tool descriptions. While it's concise and well-structured, it provides almost no actionable guidance—no example tool calls, no parameter examples, no error handling, and no verification steps. It relies entirely on the MCP server's self-documentation, which undermines the purpose of having a skill file.

Suggestions

Add at least one concrete example of a Miro MCP tool call with specific parameters (e.g., creating a flowchart or sequence diagram) so Claude has executable guidance rather than purely abstract direction.

Include a verification step after diagram creation (e.g., confirming the API response indicates success, or checking the board URL for the new content).

List the specific diagramming tool names available on the Miro MCP server so Claude doesn't have to discover them at runtime, or at minimum provide a command/method to enumerate available tools.

Dimension	Reasoning	Score
Conciseness	The content is fairly lean and doesn't over-explain concepts Claude already knows. The phrase 'The MCP server is the source of truth for which diagram types and inputs are supported, which tool to pick, the order in which tools must be called, and all placement parameters' is slightly verbose and could be tightened, but overall it respects token budget.	4 / 5
Actionability	The skill provides only high-level direction ('pick the appropriate diagramming tool') without any concrete tool names, example calls, parameter schemas, or executable code. It essentially delegates all specifics to the MCP server's own descriptions, leaving Claude with minimal concrete guidance.	2 / 5
Workflow Clarity	There is a clear 3-step sequence and it includes prompts to ask the user for missing info, which is good. However, there are no validation or verification steps (e.g., confirming the diagram was created successfully, handling errors), and the final step is vague ('call it according to its description').	3 / 5
Progressive Disclosure	For a simple, short skill under 50 lines with no need for external references, the content is well-organized with clear sections (overview paragraph + workflow). No bundle files are needed for this level of content.	5 / 5
	Total	14 / 20 Passed

Description

39%

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 is too sparse, functioning almost entirely as a 'when' clause with minimal detail about what the skill actually does. While the Miro-specific focus provides good distinctiveness, the lack of concrete actions and missing trigger term variations significantly weaken its effectiveness for skill selection among many options.

Suggestions

Add specific capabilities the skill supports, e.g., 'Creates flowcharts, mind maps, org charts, and other diagrams on Miro boards using shapes, connectors, and sticky notes.'

Expand trigger terms to include natural synonyms users might say, such as 'flowchart', 'whiteboard', 'visual diagram', 'draw', 'mind map', or 'chart'.

Restructure to lead with a concrete 'what' statement before the 'when' clause, e.g., 'Creates and updates diagrams including flowcharts, mind maps, and org charts on Miro boards. Use when the user wants to build or modify visual diagrams on Miro.'

Dimension	Reasoning	Score
Specificity	Names the domain (Miro board diagrams) but actions are minimal and generic — only 'create or update a diagram' without specifying what kinds of diagrams, what operations are supported, or what formats are involved.	2 / 5
Completeness	Has a 'when' clause but the 'what' is extremely vague — it only says 'create or update a diagram' without describing concrete capabilities. The description is essentially only a 'when' statement with a minimal implied 'what'.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'diagram', 'Miro board', 'create', and 'update', but misses common synonyms and variations such as 'flowchart', 'whiteboard', 'visual', 'chart', 'draw', or 'mind map' that users might naturally say.	3 / 5
Distinctiveness Conflict Risk	The mention of 'Miro board' specifically narrows the scope and makes it fairly distinct from other diagramming or drawing skills. Minor overlap risk with general diagramming tools, but Miro is a specific enough platform.	4 / 5
	Total	11 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: miroapp/miro-ai
Path: claude-plugins/miro/skills/miro-diagram/SKILL.md
Commit: 85c2c73

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