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).
45
Quality
31%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./claude-plugins/miro-solutions/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 topic categories but lacks concrete actions and explicit trigger guidance. It reads more like a table of contents than a skill description that helps Claude decide when to use it. The reference to the separate miro-mcp skill is helpful for disambiguation but doesn't compensate for missing 'Use when' triggers.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when users ask about Miro features, whiteboard collaboration, or need guidance on visual brainstorming tools'
Replace category names with specific actions: instead of 'Covers canvas features', say 'Navigate canvas, create frames, organize content with sticky notes and shapes'
Include natural user terms like 'whiteboard', 'sticky notes', 'brainstorming', 'diagrams', 'online collaboration' that users would actually say
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Miro visual collaboration platform) and mentions some areas covered (canvas features, content types, AI capabilities, enterprise use cases), but these are categories rather than concrete actions like 'create boards' or 'add sticky notes'. | 2 / 3 |
Completeness | Describes what the skill covers at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Miro' and 'visual collaboration platform' as relevant keywords, but misses common user terms like 'whiteboard', 'sticky notes', 'diagrams', 'brainstorming', or 'online whiteboard'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Miro' specifically and the reference to 'miro-mcp' for tool documentation helps distinguish it, but 'visual collaboration platform' is generic enough to potentially overlap with other whiteboard or collaboration tools. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a high-level overview/index of Miro capabilities with good progressive disclosure to reference materials. However, it lacks actionability - it describes what Miro is rather than instructing Claude how to work with it. The content reads more like product documentation than a skill that enables Claude to perform specific tasks.
Suggestions
Add at least one concrete, actionable workflow inline (e.g., steps to create a diagram or extract content from a board) rather than deferring everything to reference files
Remove marketing language and user statistics that don't help Claude perform tasks (e.g., '100M+ users across 250K+ organizations')
Include specific examples of when to use different content types rather than just listing them with generic purposes
Add a 'Quick Start' section with executable guidance for the most common task Claude would perform with Miro
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary context like explaining what Miro is (100M+ users, 250K+ organizations) and marketing language ('AI Innovation Workspace') that Claude doesn't need. The tables and lists are well-structured but some content could be tightened. | 2 / 3 |
Actionability | The skill is almost entirely descriptive with no concrete code, commands, or executable guidance. It describes what Miro can do but provides no actionable instructions on how to accomplish specific tasks. Everything is deferred to reference files. | 1 / 3 |
Workflow Clarity | No workflows are defined in this skill. It lists capabilities and use cases but provides no step-by-step processes, sequences, or validation checkpoints. All workflow details are deferred to reference documents without any inline guidance. | 1 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear, one-level-deep references to detailed materials. Each section points to specific reference files (content-types.md, ai-capabilities.md, etc.) with clear signaling of what each contains. | 3 / 3 |
Total | 7 / 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.
- 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.