miro-doc

Use when the user wants to create or edit a Google-Docs-style markdown document on a Miro board.

Quality

57%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./claude-plugins/miro/skills/miro-doc/SKILL.md

Quality

Discovery

57%

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 has a clear trigger clause and a distinctive niche (Miro board markdown documents), which are strengths. However, it lacks specificity about what concrete actions the skill performs beyond 'create or edit' and could benefit from more natural trigger terms that users might use when requesting this functionality.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates and edits Google-Docs-style markdown documents on Miro boards, including formatting text, adding headings, inserting lists, and structuring content.'

Expand trigger terms to include natural variations users might say, such as 'rich text document', 'write a doc on Miro', 'Miro document', 'text content on Miro board'.

Dimension	Reasoning	Score
Specificity	It names the domain (Google-Docs-style markdown document on Miro board) and mentions two actions (create, edit), but doesn't list specific concrete sub-actions like formatting, inserting tables, collaborating, etc.	2 / 3
Completeness	It has a clear 'Use when...' clause addressing the 'when', but the 'what does this do' part is weak — it only says 'create or edit a document' without describing the skill's actual capabilities or outputs in detail.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'Google-Docs-style', 'markdown', 'document', and 'Miro board', but misses common user variations like 'rich text', 'doc', 'write', 'text editor', or 'Miro document'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Google-Docs-style markdown document' and 'Miro board' is quite specific and creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Implementation

57%

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

The skill is admirably concise and well-structured, but it sacrifices actionability almost entirely by deferring all concrete guidance to the MCP server's runtime tool descriptions. It essentially tells Claude to 'explore and figure it out,' which provides minimal value over having no skill at all. The workflow is reasonable but lacks validation checkpoints.

Suggestions

Add at least one concrete example showing a typical tool call with actual parameter names/values (e.g., the tool name for creating a document, required parameters like board_id and content).

Include a brief example of the expected markdown subset supported by Miro documents, or at minimum name the specific MCP tools available (e.g., create_document, update_document).

Add a verification step to the workflow, such as confirming the document was created/updated successfully or handling error responses from the MCP server.

Dimension	Reasoning	Score
Conciseness	The skill is very lean—no unnecessary explanations of what Miro is or how MCP works. It correctly assumes Claude's competence and delegates to the MCP server as the source of truth. Every sentence earns its place.	3 / 3
Actionability	The skill provides no concrete tool names, no specific commands, no code examples, and no parameter schemas. 'Explore the document tools' and 'call it according to its description' are vague directions, not executable guidance. Claude is told to figure it out from the MCP server at runtime.	1 / 3
Workflow Clarity	There is a clear 3-step sequence with prompts to ask the user for missing info, which is good. However, there are no validation or verification steps (e.g., confirming the document was created successfully), and the final step is essentially 'figure out which tool to use,' which lacks specificity.	2 / 3
Progressive Disclosure	For a simple, short skill under 50 lines with no need for external references, the content is well-organized with a clear header and workflow section. No bundle files are needed or referenced, which is appropriate given the skill's simplicity.	3 / 3
	Total	9 / 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: da5405f

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