Name: webiny-cli-command-catalog
Rating: 40 (1 reviews)
Author: webiny

Blog Docs Log inGet started

webiny-cli-command-catalog

cli/command — 1 abstractions.

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

71%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 efficiently written abstraction catalog with a clear find-read-import workflow, but its actionability rests entirely on a source file that is not included in the bundle. Shipping the referenced source (or inlining the interface) would resolve the main weakness.

Suggestions

Include the referenced source file in the bundle (e.g. under references/) or inline the CliCommandFactory interface/types so the 'read the source file' step is actually executable.

Add one minimal copy-paste example of defining a command with CliCommandFactory so the common case is covered without reading the source.

Make the Source reference a resolvable relative path (e.g. [CliCommand.ts](references/CliCommand.ts)) instead of an opaque package path.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — three short usage steps plus a single catalog entry with no padding and no explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.	5 / 5
Actionability	The import statement is copy-paste ready, but the central instruction 'You MUST read the source file to get the exact interface and types!' points to '@webiny/cli-core/abstractions/features/CliCommand.ts', which is not present in the bundle, leaving the key detail (the actual interface) unobtainable — concrete but incomplete guidance.	3 / 5
Workflow Clarity	A clear, ordered three-step sequence (find abstraction → read source → import) appropriate for a simple catalog skill; the minor gap is the dangling source reference, and no validation checkpoints are needed since no destructive or batch operations are involved.	4 / 5
Progressive Disclosure	Sections are well organized for such a short file, but the skill's only reference — the source file the whole workflow depends on — does not exist in the bundle, so navigation to the promised detail is broken rather than clearly signaled and resolvable.	3 / 5
	Total	15 / 20 Passed

Description

3%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 effectively a stub: a module path and an abstraction count with no statement of what the skill does or when to use it. It would rarely trigger correctly and cannot be distinguished from other CLI skills.

Suggestions

State the concrete capability in third person, e.g. 'Implements custom CLI commands for Webiny CLI, including the CliCommandFactory abstraction for defining command handlers.'

Add an explicit trigger clause, e.g. 'Use when the user asks to add, customize, or troubleshoot Webiny CLI commands or the webiny/cli-command interface.'

Include natural trigger keywords users would actually say (e.g. 'Webiny CLI command', 'custom CLI command', 'cli plugin') and drop the mechanical '1 abstractions' count, which carries no information.

Dimension	Reasoning	Score
Specificity	The description is 'cli/command — 1 abstractions.' — a module path and a count with no action verbs or concrete capabilities whatsoever, matching the anchor for 'entirely vague; no concrete actions; pure abstract language'.	1 / 5
Completeness	Neither 'what' (no capability statement, just a count of abstractions) nor 'when' (no 'Use when...' clause or equivalent trigger guidance) is present, so it sits at the bottom anchor rather than merely having a vague 'what'.	1 / 5
Trigger Term Quality	It contains only technical jargon ('cli/command', 'abstractions') and none of the natural phrases a user would say when needing this skill, matching the lowest anchor.	1 / 5
Distinctiveness Conflict Risk	Naming the 'cli/command' module gives slight specificity, but with no capability description it would overlap virtually any CLI-related skill — 'very broad; high overlap risk' fits better than the entirely-generic anchor 1.	2 / 5
	Total	5 / 20 Passed

Validation

100%

Warnings & errors only

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: webiny/webiny-js
Path: skills/user-skills/generated/cli/command/SKILL.md
Commit: f0d3d3e

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.