miro-platform
Comprehensive guide to Miro as a visual collaboration platform. Covers canvas features, content types, AI capabilities, and enterprise use cases. For MCP tool documentation, see the miro plugin's skill (miro-mcp).
47
20%
Does it follow best practices?
Impact
94%
2.76xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/miro-platform/SKILL.mdQuality
Discovery
32%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 identifies the domain (Miro) and lists broad topic categories but lacks concrete actions, natural trigger terms, and explicit 'when to use' guidance. The helpful cross-reference to miro-mcp is a nice touch for disambiguation, but the description reads more like a documentation summary than a skill selection guide. It needs significantly more specificity in both capabilities and trigger conditions.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about Miro features, whiteboard collaboration, board creation, sticky notes, or visual brainstorming workflows.'
Replace category labels with concrete actions, e.g., 'Explains how to create and organize boards, use sticky notes and shapes, leverage Miro AI for content generation, and configure enterprise settings.'
Include natural user terms like 'whiteboard', 'sticky notes', 'diagrams', 'brainstorming', 'flowcharts', and 'board templates' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Miro visual collaboration platform) and some broad areas (canvas features, content types, AI capabilities, enterprise use cases), but these are category labels rather than concrete actions like 'create boards', 'add sticky notes', or 'manage templates'. | 2 / 3 |
Completeness | Describes what the skill covers at a high level but has no explicit 'Use when...' clause or equivalent trigger guidance. The description reads more like a table of contents than actionable selection criteria. Per rubric guidelines, missing 'Use when' should cap completeness at 2, and the 'what' is also quite weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Miro', 'visual collaboration', 'canvas', and 'AI capabilities' which are somewhat relevant, but misses natural user terms like 'whiteboard', 'sticky notes', 'diagrams', 'brainstorming', 'board', or 'flowchart' that users would commonly say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Miro' specifically and the reference to the separate miro-mcp skill helps distinguish it somewhat, but 'visual collaboration platform' and 'AI capabilities' are broad enough to potentially overlap with other collaboration or diagramming tools. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a product overview or marketing document rather than an actionable skill for Claude. It contains no executable guidance, no concrete steps, and no novel information that Claude wouldn't already know. The progressive disclosure structure with references to sub-files is reasonable, but the top-level content provides almost no value beyond what a simple link list would offer.
Suggestions
Replace the descriptive/marketing content with actionable guidance — e.g., specific steps for common tasks like 'how to structure a board for sprint planning' or 'how to prepare content for design-to-code export'.
Add concrete examples: what does a well-structured Miro board look like for each use case? What specific content should Claude create or recommend?
Remove promotional statistics (100M+ users, 250K+ organizations) and general product descriptions that Claude already knows — focus only on information that changes Claude's behavior.
Include at least one complete workflow with specific steps, such as the Design-to-Code pipeline, with validation checkpoints (e.g., 'verify wireframe has all required annotations before sending to coding tool').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is largely informational/marketing material that Claude already knows or can infer. Phrases like 'Miro is the visual collaboration platform for every team' and '100M+ users across 250K+ organizations' are promotional filler. The tables of content types and enterprise use cases describe general knowledge rather than providing actionable, novel instructions. | 1 / 3 |
Actionability | There are no concrete commands, executable code, specific steps, or copy-paste-ready guidance anywhere in the skill. The content describes what Miro is and what it can do, but never instructs Claude on how to actually do anything. Every section ends with 'See [reference]' without providing any actionable content itself. | 1 / 3 |
Workflow Clarity | No workflows are defined. The enterprise use cases are listed as bullet points without any sequenced steps, validation checkpoints, or process guidance. The Design-to-Code section hints at a workflow but only provides three vague bullet points with no concrete sequence. | 1 / 3 |
Progressive Disclosure | The skill does reference multiple sub-files (content-types.md, ai-capabilities.md, design-to-code.md, enterprise-use-cases.md) which is good structure. However, the top-level content itself is too thin and descriptive to serve as a useful overview — it's essentially a table of contents with marketing copy rather than a substantive quick-start guide. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
100%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
c660f77
- Reviewed
Table of Contents
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.