CtrlK
BlogDocsLog inGet started
Tessl Logo

alonso-skills/cli-building

Skill for building TypeScript CLIs using citty, @clack/prompts, and @bomb.sh/tab

76

Quality

95%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

87%

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 balances conciseness with actionability. The quick start is immediately executable, critical rules are specific and memorable, and progressive disclosure is exemplary with clear references to detailed guides. The main weakness is the workflow section, which could benefit from more explicit validation checkpoints and error recovery guidance, particularly around the build and release steps.

Suggestions

Add a validation/feedback loop to the workflow, e.g., after step 5 (sidecar setup): 'If bin entry fails, check package.json `bin` field and rebuild' — and after step 7 (release): 'Verify published package with `npx <pkg> --help`'.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It assumes Claude knows TypeScript, CLI concepts, and npm. Every section earns its place — no unnecessary explanations of what CLIs are or how libraries work. The critical rules are terse and actionable.

3 / 3

Actionability

Provides a fully executable minimal command example with real imports and runnable code. Critical rules are specific and concrete (e.g., 'check isCancel() after every @clack/prompts call'). The install command is copy-paste ready.

3 / 3

Workflow Clarity

The workflow lists clear sequential steps with references, and includes a verification step (run with --help). However, the verification is minimal — there's no feedback loop for error recovery, no validation of tab completion wiring, and no checkpoint after the build/release step. For a multi-step process involving build and release, this could be stronger.

2 / 3

Progressive Disclosure

Excellent structure with a concise overview in SKILL.md and well-signaled one-level-deep references to 8 specific reference files. The references section provides clear navigation with descriptive labels. Architecture is explicitly opt-in, preventing unnecessary complexity.

3 / 3

Total

11

/

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 an excellent skill description that clearly defines its niche (TypeScript CLI development), lists specific concrete actions and tools, and opens with an explicit 'Use when' trigger clause. It covers both the development phase (command structure, prompts, tab completion) and the shipping phase (CI, versioning, release), giving comprehensive coverage without being verbose.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: command structure, interactive prompts, tab completion, CI gates, versioning (with named tools), and release strategies (npm or single-binary). Very concrete and actionable.

3 / 3

Completeness

Explicitly answers both what ('Guides command structure, interactive prompts, tab completion... CI gates, versioning, and release') and when ('Use when building TypeScript CLIs') with a clear trigger clause at the start.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'TypeScript CLIs', 'command structure', 'interactive prompts', 'tab completion', 'CI gates', 'versioning', 'Changesets', 'release-please', 'npm', 'single-binary release'. Also names specific libraries (citty, @clack/prompts, @bomb.sh/tab) which are excellent triggers.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche: TypeScript CLI development with specific libraries (citty, @clack/prompts, @bomb.sh/tab) and specific release tooling (Changesets, release-please). 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