miro-table

Use when the user wants to create or update a structured table as a widget on a Miro board they're already working on. For a brand-new, standalone table not tied to an existing board, use the miro-format skill instead.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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.

The body is a concise, well-structured, instruction-only skill that correctly treats the live Miro MCP server as the source of truth rather than duplicating its details. Its main limitation is the absence of an explicit verification step after the table is created and reliance on runtime tool discovery for concrete tool names.

Suggestions

Add a brief verification step to the workflow (e.g., confirm the table appears on the board with the expected columns before finishing), to close the feedback loop.

Optionally include one concrete example of a board URL format and a proposed column set for a common topic, to make step 2 more immediately actionable.

Name one or two representative Miro MCP table tools inline (if stable) so Claude has a concrete starting point before exploring the server.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: it does not explain what Miro, tables, or MCP are, and delegates specifics to the live MCP server rather than restating them, so every token earns its place.	5 / 5
Actionability	Gives concrete, actionable steps (identify board URL, identify title/columns, pick the tool per its schema) with explicit decision points, but relies on runtime-discovered MCP tools rather than naming them, leaving a minor gap.	4 / 5
Workflow Clarity	A clear 3-step sequence with explicit checkpoints ("If missing, ask"; "Ask if unclear"), but lacks an explicit post-creation verification step, which keeps it just short of a full feedback loop.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references (it delegates to the live MCP server), and is organized into clear, well-scoped sections (Workflow, When not to use this skill).	5 / 5
	Total	18 / 20 Passed

Description

82%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.

The description is clear, well-triggered, and well-disambiguated, explicitly covering both what and when with concrete trigger phrasing and boundary guidance. Its only weakness is modest action specificity — it names create/update but does not enumerate richer concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain (Miro board tables) and two concrete actions ("create or update a structured table as a widget"), but does not enumerate further specific actions, so coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers both what (create/update a structured table widget on an existing Miro board) and when (an explicit "Use when..." clause with a concrete trigger), plus clear boundary guidance.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ("create or update a structured table... on a Miro board", "widget") with good keyword coverage, though a few synonyms or extensions are absent.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (table widgets on an existing board) and explicit disambiguation against the sibling miro-format skill for standalone tables, minimizing conflict risk.	5 / 5
	Total	17 / 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-table/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.