CtrlK
BlogDocsLog inGet started
Tessl Logo

mikaelkaron/cli

Manages the skills CLI and its plugins. Use when installing, listing, updating, or removing skills plugins, or setting up shell autocomplete.

80

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

This is a well-crafted skill that efficiently documents the mks CLI and its plugin management commands. It's concise, fully actionable with executable commands, includes verification steps, and is logically organized. The inclusion of short-name examples and error handling guidance adds practical value without bloat.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It assumes Claude knows what npm, CLI tools, and plugins are. Every section provides direct commands without unnecessary explanation. The brief contextual sentence at the top is useful for disambiguation.

3 / 3

Actionability

All guidance is concrete and copy-paste ready: exact bash commands for every operation, specific short-name examples, clear error message to output if CLI is missing, and explicit naming convention for plugins.

3 / 3

Workflow Clarity

For this relatively simple skill (CLI command reference), the workflow is clear: install, verify, then use commands. It includes a validation step after install/uninstall ('run mks plugins to confirm') and a troubleshooting step for missing plugins. No destructive batch operations require feedback loops.

3 / 3

Progressive Disclosure

For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized into logical sections (Setup, Plugin management, Autocomplete, Help) that are easy to scan and navigate.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, well-crafted description that clearly identifies the tool (mks CLI), lists concrete actions (install, list, update, remove plugins), and provides an explicit 'Use this when...' clause with natural trigger examples. It is concise, specific, and highly distinguishable from other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: installing, listing, updating, and removing skills plugins. Also mentions managing the mks CLI, which grounds the domain clearly.

3 / 3

Completeness

Clearly answers both 'what' (manage the mks CLI and its plugins — installing, listing, updating, removing) and 'when' (explicit 'Use this when...' clause with concrete trigger examples).

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'install', 'list installed plugins', 'update plugins', 'remove', 'skills plugins', 'cherry-pick-filter plugin', and 'mks CLI'. These cover common variations of how users would phrase plugin management requests.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — targets a specific CLI tool ('mks') and its plugin ecosystem. The trigger terms like 'mks CLI', 'skills plugins', and specific plugin names make it very unlikely to conflict with other skills.

3 / 3

Total

12

/

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.

Reviewed

Table of Contents