CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webiny-cli-extensions

Adding custom commands to the Webiny CLI using CliCommandFactory. Use this skill when the developer wants to create a custom CLI command, add a data migration script, build a code generator, create deployment scripts, export CMS content, or add health check commands. Covers CliCommandFactory.Interface, command definition, typed parameters, the Ui service for terminal output, and registration via <Cli.Command>.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is a well-structured, highly actionable guide: one complete executable example plus compact API tables and an explicitly flagged registration pitfall. Its main gaps are mild redundancy (the Quick Reference and Use Cases sections restate earlier content) and the absence of any verification step confirming the command registered and runs.

Suggestions

Cut or shrink the 'Quick Reference' block — it repeats imports, export, and registration lines already fully shown — and fold 'Use Cases' into the TL;DR to remove duplication.

Add a validation step after registration (e.g., run `yarn webiny --help` or invoke the command once) so the workflow ends with a checkpoint confirming the command is registered.

Consider moving the full worked example and/or the property tables into a references/ file, leaving SKILL.md as a tighter overview, to strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens: a complete code example, tight API tables, and a highlighted registration gotcha ("YOU MUST include the .ts file extension... omitting it will cause a build failure"). It falls short of 5 mainly because the 'Quick Reference' block and 'Use Cases' list largely duplicate information already shown in the TL;DR, code, and tables — trimming that repetition would match the 'lean and efficient' anchor.

4 / 5

Actionability

The guidance is fully executable: a copy-paste-ready TypeScript class implementing CliCommandFactory.Interface with real imports, the exact registration JSX (`<Cli.Command src={"/extensions/MyCustomCommand.ts"} />`), and the run command `yarn webiny my-custom-command "World"`. No pseudocode; nothing is left abstract.

5 / 5

Workflow Clarity

The define → export → register → run sequence is coherent and in the right order, and the critical .ts-extension pitfall is explicitly flagged as a build-failure risk. It sits at 4 rather than 5 because there are no validation checkpoints (e.g., run `yarn webiny --help` or execute the command to confirm registration) — the flow ends at 'Run it' without verifying the command registered correctly.

4 / 5

Progressive Disclosure

The single-file body is well organized with clear sections (TL;DR, pattern, property tables, Ui service, use cases, quick reference, related skills), no nested references, and appropriate single-level pointers to sibling skills. It is not 5 because everything lives inline in SKILL.md — at ~115 lines, the full code example and the two API tables could arguably live in reference files, and no bundle structure exists to offload them — but structure and navigation are solid, matching the score-4 anchor.

4 / 5

Total

17

/

20

Passed

Description

88%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.

A strong description: it states concrete capabilities in third-person voice, enumerates explicit 'use when' triggers, and anchors itself firmly in the Webiny CLI niche with specific API names. Its only weaknesses are a few missing natural synonyms (like 'yarn webiny' or 'scaffold') and slight overlap potential with sibling Webiny extension skills.

Suggestions

Add a couple of natural user phrasings/synonyms such as 'yarn webiny' or 'scaffold a CLI command' to the trigger list to strengthen trigger_term_quality toward 5.

Sharpen the 'when' clause with a boundary (e.g., 'Use for CLI-only commands; for full-stack extensions including API/Admin, use webiny-full-stack-architect') to reduce overlap with sibling Webiny skills.

DimensionReasoningScore

Specificity

The description names the domain and multiple concrete actions: "create a custom CLI command, add a data migration script, build a code generator, create deployment scripts, export CMS content, or add health check commands", plus concrete technical specifics ("CliCommandFactory.Interface", "the Ui service for terminal output", "registration via <Cli.Command>"). This matches the score-5 anchor of multiple specific concrete actions with comprehensive coverage; nothing is generic fluff.

5 / 5

Completeness

It explicitly answers both questions: what ("Adding custom commands to the Webiny CLI using CliCommandFactory", with a "Covers..." enumeration) and when ("Use this skill when the developer wants to..." followed by concrete trigger cases). This is a direct match for the score-5 anchor; not 4 because the 'when' clause is explicit and enumerates concrete triggers rather than being merely adequate.

5 / 5

Trigger Term Quality

Natural trigger phrases like "custom CLI command", "data migration", "code generator", "deployment scripts", "export CMS content", and "health check" cover the likely user phrasings well. It falls just below the score-5 anchor because a few natural synonyms and concrete invocations are missing (e.g., "yarn webiny", "scaffold", "seed data", "terminal command").

4 / 5

Distinctiveness Conflict Risk

"Webiny CLI" and "CliCommandFactory" peg it to a clear, narrow niche with low conflict risk against generic skills. It stays at 4 rather than 5 because the body references sibling Webiny skills (e.g., webiny-full-stack-architect, which "may include CLI commands"), so a user asking broadly to "add a Webiny extension" could plausibly trigger the wrong sibling — minor overlap risk with closely related skills, matching the score-4 anchor.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

webiny/webiny-js

Path

skills/user-skills/cli-extensions/SKILL.md

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.