CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-cli-command-catalog

cli/command — 1 abstractions.

51

Quality

55%

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 ./skills/user-skills/generated/cli/command/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a concise, well-structured command catalog that gives concrete import and source-file guidance for its one abstraction. Its main weakness is that the generic import template uses placeholders rather than a fully executable example.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of concepts Claude already knows; the three-step 'How to Use' and the single abstraction entry each earn their place.

5 / 5

Actionability

It gives a concrete import line and source path for CliCommandFactory and an import template, but the workflow step 'import { Name } from "<importPath>"' is a placeholder rather than fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

The numbered three-step sequence (find abstraction, read source, import) is clear and this is a simple non-destructive skill, but there are no checkpoints or error-handling notes, keeping it just below 5.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized 'How to Use' and 'Abstractions' sections and no need for external reference files; per the simple-skill exception this is appropriately structured.

5 / 5

Total

18

/

20

Passed

Description

25%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 terse but uninformative: it names the cli/command domain yet states no concrete actions and gives no trigger guidance for when to use it. It reads more as a label than a usable skill description.

Suggestions

Add concrete actions, e.g. 'Implement and register custom CLI commands for the Webiny CLI'.

Include an explicit 'Use when...' clause naming natural triggers such as 'adding a new CLI command' or 'customizing Webiny CLI behavior'.

Drop the opaque '1 abstractions' count in favor of language a user would actually say.

DimensionReasoningScore

Specificity

The description names the domain ('cli/command') but the only action language is '1 abstractions', which is not a concrete action; it falls between the score-1 (no concrete actions) and score-3 (1-2 concrete actions) anchors, closer to the minimal side.

2 / 5

Completeness

It provides a vague 'what' (cli/command abstractions) and no 'when' / 'Use when' clause at all; the missing trigger guidance caps it below 3.

2 / 5

Trigger Term Quality

'cli/command' is technical jargon and '1 abstractions' is not a phrase a user would naturally say, so it offers only a generic domain keyword and misses natural trigger phrases.

2 / 5

Distinctiveness Conflict Risk

'cli/command — 1 abstractions' is very broad and technical with high overlap risk against other CLI-related skills, matching the score-2 'very broad; high overlap risk' anchor.

2 / 5

Total

8

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
webiny/webiny-js
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.