Name: miro-doc
Rating: 84.2 (1 reviews)
Author: miroapp

miro-doc

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

1.41x

Quality

80%

Does it follow best practices?

Impact

85%

1.41x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is miro-doc in miroapp/miro-ai

Quality

Content

78%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 tight, well-organized skill body that delegates specifics to the Miro MCP server rather than duplicating them. It is admirably concise and clearly structured, but actionability is held back by the absence of any concrete example tool call or representative parameters.

Suggestions

Include one short example invocation showing a representative Miro MCP document tool name and its key parameters (e.g. board URL + content) so Claude has a concrete anchor before deferring to the live schemas.

Add a brief error-recovery note for common failure modes (e.g. invalid board URL, unsupported markdown element) to turn the workflow's clarifying gates into a full validate-and-retry loop.

Optionally name the one or two most common document tools inline as a quick-pick hint, while keeping the MCP server as the source of truth.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding about what Miro or MCP is, and every line carries useful guidance, matching the anchor-5 'lean and efficient' example.	5 / 5
Actionability	The workflow gives concrete gates ('Identify the board URL. If missing, ask.'; 'Pick the appropriate document tool... and call it according to its description and parameter schema') but provides no example tool name or sample invocation, leaving key execution details to the MCP server — the anchor-3 'some concrete guidance but incomplete' fit.	3 / 5
Workflow Clarity	A clear 3-step numbered sequence with clarifying checkpoints ('If missing, ask'; 'Ask if unclear'), but it lacks an explicit error-recovery/feedback loop, so it lands at anchor-4 rather than 5.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references, and it is organized into clear, well-signaled sections (Workflow, When not to use this skill), qualifying for the simple-skill anchor-5 exception.	5 / 5
	Total	17 / 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 concise, well-structured description that clearly states what the skill does and when to use it, with strong disambiguation from a sibling skill. Its only real weakness is moderate specificity — it names only two high-level actions (create/edit) rather than a comprehensive action list.

Dimension	Reasoning	Score
Specificity	Names the domain (Miro board) and two concrete actions ('create or edit' a 'Google-Docs-style markdown document as a widget'), but does not enumerate several specific actions, so it sits at the anchor-3 level rather than 4.	3 / 5
Completeness	It explicitly answers both 'what' (create/edit a Google-Docs-style markdown document as a board widget) and 'when' ('Use when the user wants to create or edit...') with a concrete trigger phrase, matching the anchor-5 example.	5 / 5
Trigger Term Quality	Natural terms like 'create or edit', 'markdown document', 'widget on a Miro board', and 'Miro' give good keyword coverage; a few common synonyms (e.g. 'doc', 'board card') are missing, so it is above the midpoint but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (document widget on an existing Miro board) and actively disambiguates from miro-format via the 'When not to use' boundary, giving minimal conflict risk per the anchor-5 description.	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-doc/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.