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

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-structured MCP-delegating skill that is concise and clearly organized. Its main weakness is actionability: it tells Claude to follow MCP tool schemas but gives no concrete example invocation or parameter pattern to ground the first call.

Suggestions

Add one short example MCP tool invocation (tool name + a minimal parameter sketch, e.g. board URL + content) so Claude has a concrete anchor before discovering the rest from the server.

Include a final workflow step that verifies the document widget was created on the board (e.g. re-fetch or confirm via the MCP server) to close the validation gap.

Name the one or two most likely document tools inline as a quick pick hint, while still pointing to the MCP server as the source of truth.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding: it never explains what Miro or markdown is and every line ('Shortcut to the Miro MCP document tools', the source-of-truth note, the three workflow steps) earns its place.	5 / 5
Actionability	Guidance is procedurally concrete ('Identify the board URL', 'Pick the appropriate document tool... and call it according to its description and parameter schema') but defers all executable specifics to the MCP server, with no example tool name, invocation, or parameter pattern to anchor on.	3 / 5
Workflow Clarity	A clear three-step sequence with input checkpoints ('If missing, ask', 'Ask if unclear'), but there is no validation that the document was actually created/placed correctly on the board, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references (it delegates detail to the MCP server) and three well-organized sections (overview, Workflow, When not to use), matching the simple-skill exception for a 5.	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 strong description: explicit trigger, clear what/when, and explicit disambiguation from the related miro-format skill. The only soft spot is specificity, which lists just 'create or edit' without naming richer capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain (a Google-Docs-style markdown document as a widget on a Miro board) and the two actions 'create or edit', but coverage is not comprehensive beyond those two verbs, matching the '1-2 concrete actions' anchor.	3 / 5
Completeness	It explicitly states what the skill does ('create or edit a Google-Docs-style markdown document as a widget on a Miro board') and gives an explicit 'Use when...' trigger, plus a negative-trigger boundary, satisfying both what and when.	5 / 5
Trigger Term Quality	Natural terms a Miro user would say are present ('create or edit', 'markdown document', 'widget', 'Miro board'), giving good keyword coverage with only minor synonyms missing (e.g. 'note', 'text widget').	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (document widget on an existing board) and explicitly disambiguates against the closest sibling ('use the miro-format skill instead'), giving minimal conflict risk.	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: 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.