CtrlK
BlogDocsLog inGet started
Tessl Logo

skills-development

Use when authoring or revising plugin SKILL.md files in this repo. Captures the principles for keeping skills as compact shortcuts to MCP tool groups.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/skills-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 an exemplar of token-efficient, action-oriented principle listing with no padding and no over-explanation of known concepts. It is held just below top marks on actionability, workflow clarity, and progressive disclosure for lack of a concrete before/after snippet and minimal sectioning, both of which are minor for a skill this short.

Suggestions

Add one short before/after SKILL.md snippet pair to make the 'no code-shaped parameter names' rule copy-paste concrete.

Split the principles under two labeled subsections (e.g., 'What to avoid' and 'What to do instead') to strengthen navigation.

DimensionReasoningScore

Conciseness

The body is a lean four-bullet list of directives with only a brief, value-adding rationale per bullet; it assumes Claude's competence, explains no concepts Claude already knows, and every token earns its place.

5 / 5

Actionability

Guidance is concrete and specific ('fetch parameter definitions and tool descriptions from the MCP server directly at call time', describe values in prose like 'the board item ID' rather than `item_id`), with a worked contrast example; it stops short of a 5 only because no good-vs-bad SKILL.md snippet is shown to anchor the rules.

4 / 5

Workflow Clarity

As a simple, single-purpose skill with no multi-step or destructive process, the clean bulleted list is clear and well-organized; it is not a 5 because the content is a set of principles rather than an explicitly sequenced workflow.

4 / 5

Progressive Disclosure

At under 50 lines with no external references needed, the single heading and organized bullet list meet the bar for a simple skill; it is not a 5 because there is only one flat section rather than clearly delineated subsections.

4 / 5

Total

17

/

20

Passed

Description

70%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 concise, third-person, and provides an explicit 'Use when' trigger plus a clear (if abstract) statement of what the skill does. It is strong on trigger phrasing and distinctiveness but loses points for abstract rather than concretely enumerated capabilities.

Suggestions

Replace 'Captures the principles' with 1-2 concrete verbs describing what the skill does (e.g., 'Defines the rules for keeping SKILL.md files lean and MCP-tool-agnostic').

Add a natural synonym such as 'writing or editing skill files' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('authoring or revising plugin SKILL.md files') and a framing action ('Captures the principles'), but the stated action is abstract rather than a list of several concrete capabilities, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Explicitly answers both 'what' ('Captures the principles for keeping skills as compact shortcuts to MCP tool groups') and 'when' ('Use when authoring or revising plugin SKILL.md files'); the 'when' is present and clear but the 'what' is somewhat abstract rather than concretely enumerated, so it is not a 5.

4 / 5

Trigger Term Quality

Includes natural terms a user would say ('authoring or revising', 'SKILL.md files', 'plugin') with an explicit 'Use when' trigger; a few common synonyms ('writing skills', 'skill files') are missing, so it sits just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The trigger 'authoring or revising plugin SKILL.md files in this repo' carves a clear niche with minimal overlap risk; it could marginally collide with a generic skills-development skill, keeping it just below a 5.

4 / 5

Total

15

/

20

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 — 16 / 16 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.