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.

54

Quality

60%

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 ./.agents/skills/skills-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

This is a lean, well-scoped meta-skill that clearly communicates its core principles without verbosity. Its main weakness is the lack of concrete examples (good vs bad SKILL.md snippets) and the absence of a lightweight workflow or checklist for applying these principles when authoring or revising a skill file.

Suggestions

Add a brief before/after example showing a bad SKILL.md snippet (with hardcoded tool/param names) vs a good one (using prose descriptions), to make the principles immediately actionable.

Include a short checklist or workflow (e.g., 'Draft → verify no tool names → verify no param names → confirm MCP fetch instruction') to give authors a concrete review process.

DimensionReasoningScore

Conciseness

Every sentence carries unique, non-obvious information. No padding, no explanation of concepts Claude already knows. The prose-over-code-names rationale is genuinely novel guidance that wouldn't be inferred.

3 / 3

Actionability

The skill provides clear principles (don't duplicate, don't name tools/params, fetch from MCP at call time), but it lacks concrete examples of a well-written vs poorly-written SKILL.md snippet. The guidance is specific enough to follow but would benefit from a before/after example.

2 / 3

Workflow Clarity

The skill is a set of principles rather than a multi-step workflow, but for a skill about authoring/revising SKILL.md files, a brief sequence (e.g., 1. Draft skill, 2. Check against these principles, 3. Verify no tool/param names leaked) would improve clarity. The current bullet-list format is clear but lacks any validation or review checkpoint.

2 / 3

Progressive Disclosure

For a simple, short skill under 50 lines with no need for external references, the content is well-organized into a concise set of principles. No monolithic walls of text or unnecessary nesting.

3 / 3

Total

10

/

12

Passed

Description

47%

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 (SKILL.md authoring) and includes a 'Use when' clause, but it is too abstract about what the skill actually does. It reads more like a purpose statement than an actionable description, lacking concrete actions and sufficient trigger term coverage.

Suggestions

Replace 'Captures the principles for keeping skills as compact shortcuts to MCP tool groups' with specific actions like 'Guides structure, frontmatter fields, and content organization for SKILL.md files'.

Expand trigger terms to include natural variations like 'create a skill', 'skill template', 'skill file', 'write a new skill', or 'skill format'.

Add more concrete 'what' details, e.g., 'Provides conventions for naming, description writing, and scoping skills to MCP tool groups.'

DimensionReasoningScore

Specificity

The description uses vague language like 'captures the principles' and 'compact shortcuts to MCP tool groups' without listing any concrete actions. It doesn't specify what authoring or revising actually entails (e.g., writing frontmatter, structuring sections, validating format).

1 / 3

Completeness

It has a 'Use when' clause ('Use when authoring or revising plugin SKILL.md files'), which addresses the 'when'. However, the 'what' is weak — 'captures the principles for keeping skills as compact shortcuts' is abstract and doesn't clearly describe what the skill actually does or produces.

2 / 3

Trigger Term Quality

It includes some relevant terms like 'SKILL.md', 'plugin', and 'MCP tool groups' that a user working on skills might mention. However, it misses common variations like 'skill file', 'skill description', 'skill template', 'create a skill', or 'write a skill'.

2 / 3

Distinctiveness Conflict Risk

The description targets a very specific niche — authoring SKILL.md files in a particular repo with MCP tool group conventions. This is unlikely to conflict with other skills due to its narrow, meta-level focus.

3 / 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.