miro-doc

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

1.18x

Quality

49%

Does it follow best practices?

Impact

77%

1.18x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/miro-doc/SKILL.md

Quality

Content

50%

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

This skill is essentially a thin wrapper that delegates nearly all actionable detail to the Miro MCP server's tool descriptions. While it's concise and has a basic workflow structure, it provides almost no concrete guidance—no tool names, no example calls, no parameter examples, and no validation steps. It reads more like a routing instruction than a skill that teaches Claude how to perform a task.

Suggestions

Add at least one concrete example showing a specific MCP tool call with parameters (e.g., creating a document with sample markdown content and placement coordinates).

Include the names of the key Miro MCP document tools so Claude knows what to look for, rather than relying entirely on runtime discovery.

Add a verification step after document creation/editing (e.g., confirm the document appears on the board, check for errors in the response).

Dimension	Reasoning	Score
Conciseness	The content is fairly lean and doesn't over-explain concepts Claude already knows. The sentence about the MCP server being the source of truth is useful context. Minor verbosity in the intro paragraph ('Shortcut to the Miro MCP document tools') could be trimmed.	4 / 5
Actionability	The skill provides only high-level direction ('pick the appropriate document tool') without any concrete tool names, code examples, API calls, or specific parameters. It essentially delegates all actionable detail to the MCP server's own descriptions, making this more of a pointer than executable guidance.	2 / 5
Workflow Clarity	There is a clear 3-step sequence, but it lacks any validation or verification steps. Steps are high-level ('pick the appropriate document tool and call it') without specifics. For a skill involving creating/editing content on a board, there's no confirmation or error-handling guidance.	3 / 5
Progressive Disclosure	The skill is short and doesn't need external files, but it references the MCP server as the source of truth without providing any concrete pointers to tool names or schemas. There are no bundle files to support the content. For a simple skill this structure is acceptable but the lack of any reference material or examples is a gap.	3 / 5
	Total	12 / 20 Passed

Description

48%

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 provides a clear 'when' trigger but lacks specificity about what concrete actions the skill performs beyond generic 'create or edit.' It carves out a reasonably distinct niche by combining Miro boards with Google-Docs-style markdown documents, but would benefit from listing specific capabilities and including more natural trigger terms users might use.

Suggestions

Add specific capabilities beyond 'create or edit', such as 'format text with headings, lists, and tables' or 'insert images and links into the document'.

Include additional natural trigger terms and synonyms users might say, such as 'rich text document', 'write a doc on Miro', 'text editor', or 'Miro document'.

Separate the 'what' from the 'when' — start with a clear statement of capabilities, then follow with the 'Use when...' clause.

Dimension	Reasoning	Score
Specificity	Names the domain (Google-Docs-style markdown document on Miro board) but the actions are minimal and generic — only 'create or edit' are mentioned with no further detail about what creating or editing entails.	2 / 5
Completeness	The 'when' is explicitly stated ('Use when the user wants to...'), but the 'what' is only weakly described — it says 'create or edit' without specifying concrete capabilities like formatting, inserting tables, adding headings, etc. The 'what' is implied through the 'when' clause rather than independently stated.	3 / 5
Trigger Term Quality	Includes some relevant keywords like 'Google-Docs-style', 'markdown', 'document', and 'Miro board', but misses natural user phrases and synonyms such as 'rich text', 'write', 'doc', 'text document', or 'Miro document'.	3 / 5
Distinctiveness Conflict Risk	The combination of 'Google-Docs-style markdown document' and 'Miro board' is fairly distinctive and narrows the scope well. Minor overlap risk exists with other Miro-related skills or general markdown/document editing skills.	4 / 5
	Total	12 / 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: skills/miro-doc/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.