miro-browse

Use when the user wants to explore, list, summarize, or inspect items on a Miro board.

0.98x

Quality

66%

Does it follow best practices?

Impact

93%

0.98x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./claude-plugins/miro/skills/miro-browse/SKILL.md

Quality

Content

60%Weight 40%Scale 1-5

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

A short, well-structured instruction-only skill with a clear three-step workflow for a read-only browsing task. Its main weaknesses are abstract, deferring actionability and an intro paragraph that could be tighter.

Suggestions

Tighten the intro: drop the abstract 'source of truth for which tools exist...' sentence and state the skill's purpose in one line, since Claude can read the MCP tool descriptions itself.

Add concrete guidance for the common cases — e.g., name the high-level overview vs. item-level retrieval tools the Miro MCP server typically exposes, or show an example tool-call shape, so the workflow is actionable without runtime discovery.

Add a brief checkpoint in the workflow (e.g., confirm the board URL resolves and the user's intent is pinned before chaining calls) to lift workflow clarity toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the intro paragraph abstractly asserts 'The MCP server is the source of truth for which tools exist..., which tool to pick, how to chain them, and all parameters', which is prose that could be tightened.	3 / 5
Actionability	Guidance defers entirely to the MCP server's own tool descriptions ('call it per its description') and never names concrete tool names or parameters, leaving executable specifics missing despite reasonable workflow hints.	3 / 5
Workflow Clarity	A clear three-step sequence (board URL, user intent, pick tool) is present and the skill is read-only so the destructive-validation cap does not apply, but explicit checkpoints or feedback loops are absent.	4 / 5
Progressive Disclosure	The short body is well-organized into an intro and a Workflow section with no external references needed; structure is good with only minor organization gaps, falling just short of the score-5 anchor.	4 / 5
	Total	14 / 20 Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-triggered description that clearly signals when to use the skill and sits in a distinct Miro-board niche. It is held back from a top score by an implied-only 'what' and somewhat generic action verbs.

Dimension	Reasoning	Score
Specificity	Names the Miro-board domain and four actions (explore, list, summarize, inspect), but the verbs are generic and overlapping rather than the distinct concrete operations of the score-4 anchor.	3 / 5
Completeness	The 'when' is explicit ('Use when the user wants to...'), but the 'what' is only implied through the verbs rather than stated outright, so it falls short of the score-5 explicit both-what-and-when anchor.	4 / 5
Trigger Term Quality	Phrases like 'explore, list, summarize, or inspect items on a Miro board' are natural things a user would say, giving good keyword coverage, though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	'Miro board' carves out a clear, distinct niche with trigger terms unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	16 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: miroapp/miro-ai
Path: claude-plugins/miro/skills/miro-browse/SKILL.md
Commit: c2494b2

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