CtrlK
BlogDocsLog inGet started
Tessl Logo

miro-table

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

45

Quality

46%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./claude-plugins/miro/skills/miro-table/SKILL.md
SKILL.md
Quality
Evals
Security

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 almost all specifics to the Miro MCP server's tool descriptions. While it's concise and well-structured, it provides almost no actionable content—no tool names, no example parameters, no sample payloads, and no validation steps. It reads more like a placeholder than a skill that teaches Claude how to perform a specific task.

Suggestions

Add at least one concrete example showing a specific Miro MCP tool call with actual parameter values (e.g., creating a simple 3-column table with sample data).

List the specific Miro MCP tool names relevant to table operations so Claude knows exactly which tools to look for rather than 'exploring' them.

Add a validation step after table creation (e.g., verify the table was created successfully, confirm column count matches expectations).

Include an example of the expected parameter schema shape for at least one common table operation to make the skill actionable.

DimensionReasoningScore

Conciseness

Reasonably brief but includes some unnecessary filler like 'Shortcut to the Miro MCP table tools' and the verbose sentence about the MCP server being the 'source of truth.' The repeated emphasis on deferring to the MCP server could be tightened.

2 / 3

Actionability

The skill provides no concrete code, commands, tool names, or parameter examples. It essentially says 'explore the MCP tools and use them,' which is vague direction rather than executable guidance. There are no specific tool names, example payloads, or API calls.

1 / 3

Workflow Clarity

There is a 3-step sequence that covers the basic flow (get board URL, determine table spec, call tool), and it includes prompts to ask the user when info is missing. However, there are no validation or verification steps after table creation, and step 3 is essentially 'figure it out from the MCP server' rather than concrete guidance.

2 / 3

Progressive Disclosure

This is a simple, short skill under 50 lines with no bundle files. The content is well-organized with a clear header and workflow section. No external references are needed for this level of content, and the structure is clean.

3 / 3

Total

8

/

12

Passed

Description

50%

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 provides a basic 'Use when...' trigger and identifies the Miro board context, which is helpful for selection. However, it lacks specificity about what concrete actions the skill performs (e.g., defining columns, populating rows, formatting) and misses common trigger term variations users might use. It reads more as a trigger clause without a substantive capability statement.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates tables with defined columns and rows, populates cells with data, updates existing table content on Miro boards.'

Expand trigger terms to include natural variations like 'grid', 'rows and columns', 'tabular layout', 'Miro table', or 'data table'.

Strengthen the 'what' portion by listing 2-3 specific capabilities before the 'Use when...' clause to clearly separate what the skill does from when to use it.

DimensionReasoningScore

Specificity

The description mentions 'create or update a structured table' which names a domain (Miro board) and some actions (create, update), but doesn't list specific concrete actions like adding rows, formatting cells, importing data, etc.

2 / 3

Completeness

The description has a 'Use when...' clause addressing when to use it, 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 in detail.

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', 'rows and columns', 'tabular data', or 'Miro table'.

2 / 3

Distinctiveness Conflict Risk

The mention of 'Miro board' provides some distinctiveness, but 'structured table' is somewhat generic and could overlap with other table-creation skills (e.g., spreadsheet tools, database tools, or other whiteboard platforms).

2 / 3

Total

8

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
miroapp/miro-ai
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.