miro-doc

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

1.18x

Quality

57%

Does it follow best practices?

Impact

77%

1.18x

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-doc/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.

The skill is admirably concise and well-structured, but it sacrifices actionability almost entirely by deferring all specifics to the MCP server's tool descriptions. While delegating to the MCP server as source of truth is a reasonable design choice, the skill provides no concrete tool names, example calls, parameter values, or expected outputs, making it little more than a generic 'use the MCP tools' instruction. It would benefit significantly from at least one concrete example of a document creation call.

Suggestions

Add at least one concrete example showing a specific MCP tool call with parameters (e.g., tool name, board ID, markdown content) and expected outcome.

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

List the specific MCP document tool names available (even if briefly) so Claude knows what to look for rather than having to discover them.

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. 'Pick the appropriate document tool' and 'call it according to its description' are vague directions that don't give Claude specific, executable guidance. It essentially tells Claude to figure it out from the MCP server.	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 workflow lacks specificity about which tools to call or what parameters to use.	2 / 3
Progressive Disclosure	For a simple, short skill under 50 lines with no bundle files and no need for external references, the content is well-organized with a clear header and workflow section. The structure is appropriate for its scope.	3 / 3
	Total	9 / 12 Passed

Description

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 establishes a clear niche (Miro board markdown documents) and includes a 'Use when' clause, 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 users might use. The 'what it does' portion is underdeveloped compared to the 'when to use it' portion.

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 with natural user variations such as 'doc', 'text document', 'write content', 'rich text', or 'document widget' to improve matching.

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 actions like formatting, inserting tables, adding headings, etc.	2 / 3
Completeness	It has a 'Use when...' clause addressing when to use it, but the 'what does this do' part is weak — it only says 'create or edit' without describing specific capabilities. The what is implied rather than explicitly stated.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'Google-Docs-style', 'markdown', 'Miro board', 'document', but misses common user variations like 'doc', 'text document', 'write', 'rich text', or 'Miro document widget'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Google-Docs-style markdown document' and 'Miro board' creates a very specific niche that is unlikely to conflict with other skills. The Miro board context is a clear distinguishing factor.	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: 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.