miro-table

Use when the user wants to create or update a structured table on a Miro board.

Quality

49%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

42%

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 all real guidance to the Miro MCP server's tool descriptions. While concise, it fails to provide actionable value — no concrete tool names, parameter examples, or sample calls are included. The workflow is a reasonable skeleton but lacks the specificity needed for Claude to act without further discovery.

Suggestions

Add at least one concrete example showing a complete table creation call with specific tool name, parameters, and expected output.

Include the actual MCP tool names available (e.g., `create_table`, `update_table`) so Claude knows what to look for rather than having to explore blindly.

Add a brief example of the column/option schema shape so Claude can construct valid parameters without trial and error.

Dimension	Reasoning	Score
Conciseness	Reasonably brief but includes some unnecessary filler like 'Shortcut to the Miro MCP table tools' and the vague paragraph about exploring tools. The repeated emphasis on 'MCP server is the source of truth' is somewhat redundant.	2 / 3
Actionability	The skill provides no concrete commands, code, tool names, or specific parameters. It essentially says 'find the right tool and use it' which is vague direction rather than executable guidance. There are no examples of table creation calls, parameter shapes, or expected outputs.	1 / 3
Workflow Clarity	Steps are listed in a logical sequence (get board URL, determine table spec, call tool), but there are no validation checkpoints, no error handling, and step 3 is essentially 'figure it out from the MCP server' which provides no real guidance.	2 / 3
Progressive Disclosure	For a simple, short skill with no bundle files, the content is appropriately organized with a clear overview and workflow section. No external references are needed given the skill's reliance on MCP server self-documentation.	3 / 3
	Total	8 / 12 Passed

Description

57%

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 a clear niche (Miro board tables) and includes a 'Use when' clause, which helps with distinctiveness and trigger matching. However, it lacks specificity about what concrete actions the skill performs beyond 'create or update' and could benefit from more natural trigger terms and a richer explanation of capabilities.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates tables with rows and columns, updates cell content, resizes tables, and formats headers on Miro boards.'

Expand trigger term coverage by including variations like 'grid', 'spreadsheet', 'add rows', 'Miro table widget', or 'tabular data on Miro'.

Dimension	Reasoning	Score
Specificity	It mentions a domain (Miro board) and a general action (create or update a structured table), but does not list multiple specific concrete actions like adding rows, formatting cells, or merging tables.	2 / 3
Completeness	It has a 'Use when...' clause addressing when to use the skill, but the 'what does this do' portion is weak—it only vaguely says 'create or update a structured table' without describing specific capabilities or actions the skill performs.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'table', 'Miro board', 'create', and 'update', but misses common variations users might say such as 'grid', 'spreadsheet on Miro', 'add rows/columns', or 'Miro table widget'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Miro board' and 'structured table' creates a clear niche that is unlikely to conflict with other skills, as it targets a specific platform and a specific artifact type.	3 / 3
	Total	9 / 12 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
Commit: 85c2c73

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