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

Blog Docs Log in Get started

webiny-cli-command-catalog

cli/command — 1 abstractions.

Quality

42%

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

85%

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 clean, well-structured catalog entry that efficiently points Claude to source files, but it stops short of giving executable usage examples for the abstraction it lists. Workflow and disclosure are appropriate for a simple single-purpose skill.

Suggestions

Add a minimal executable example showing how to invoke CliCommandFactory (e.g. a short snippet creating and registering a command) so the skill is copy-paste ready without forcing a source read.

Clarify what to read for in the source file (interface signature, required options) so the 'read the source' step is actionable rather than open-ended.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive ('You MUST read the source file...'), with no padding or explanation of concepts Claude already knows, matching the 'Lean and efficient; every token earns its place' anchor; it is not a 2 because there is no unnecessary explanation.	3 / 3
Actionability	It gives a concrete, copy-paste import line and a source path, but defers real usage to 'read the source file' with no executable example of how to call CliCommandFactory, matching the 'Some concrete guidance but incomplete; missing key details' anchor; it is not a 3 because no executable usage code is provided.	2 / 3
Workflow Clarity	The numbered 'How to Use' sequence (find abstraction, read source, import) is clear and unambiguous for this simple catalog skill, and no destructive/batch validation is needed, matching the simple-skill allowance for a 3.	3 / 3
Progressive Disclosure	The SKILL.md acts as a one-level-deep overview pointing to source files, with well-organized 'How to Use' and 'Abstractions' sections and no nested references; for a simple skill under 50 lines this matches the well-organized anchor for a 3.	3 / 3
	Total	11 / 12 Passed

Description

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 critically underspecified: it names only a domain and a count of abstractions with no capabilities, user-facing triggers, or use-when guidance. It is unlikely to surface for the right request and gives Claude almost nothing to act on.

Suggestions

Replace the description with concrete actions, e.g. 'Implement custom CLI commands for Webiny CLI: define command handlers, options, and lifecycle hooks.'

Add an explicit trigger clause: 'Use when the user needs to create or customize Webiny CLI commands or asks about webiny cli command abstractions.'

Drop the meta-count '1 abstractions' and use natural third-person terms users would actually say (CLI commands, webiny cli).

Dimension	Reasoning	Score
Specificity	The description "cli/command — 1 abstractions" names a domain but lists no concrete actions, matching the 'vague or no actions; abstract language' anchor; it is not a 2 because no specific verbs or capabilities are stated.	1 / 3
Completeness	It answers neither 'what does this do' (no actions) nor 'when to use it' (no Use-when clause), matching the 'Missing what OR when, or both very weak' anchor; the missing trigger guidance alone would cap at 2, but both are weak.	1 / 3
Trigger Term Quality	There are no natural keywords a user would say; 'cli/command — 1 abstractions' is internal jargon, matching the 'No natural keywords; technical jargon or overly generic' anchor rather than level 2 which requires some relevant user-facing terms.	1 / 3
Distinctiveness Conflict Risk	The phrase is so generic it could describe many CLI skills, matching the 'Very generic; would conflict with many skills' anchor; it lacks the niche-specific triggers needed for a 2.	1 / 3
	Total	4 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: webiny/webiny-js
Path: skills/user-skills/generated/cli/command/SKILL.md
Commit: 484553b

Reviewed: about 12 hours 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.