CtrlK
BlogDocsLog inGet started
Tessl Logo

create-cli

Design command-line interface parameters and UX: arguments, flags, subcommands, help text, output formats, error messages, exit codes, prompts, config/env precedence, and safe/dry-run behavior. Use when you’re designing a CLI spec (before implementation) or refactoring an existing CLI’s surface area for consistency, composability, and discoverability.

75

Quality

93%

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

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

A tight, highly actionable skill body that delegates bulk reference material to a single clearly-signaled reference file and provides concrete templates and conventions. The only minor gap is the absence of an explicit verification checkpoint for the produced spec.

Suggestions

Add an explicit validation step after 'Deliverables' instructing Claude to re-check the generated spec against references/cli-guidelines.md and the user's clarified constraints before finalizing.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; assumes Claude knows CLI basics, with no padding or over-explanation, and every section (Do This First, Clarify, Deliverables, Default Conventions, Templates) earns its place.

5 / 5

Actionability

Provides concrete clarify-questions, an explicit deliverables checklist, default conventions, and a copy-paste-ready CLI spec skeleton template covering the common design cases.

5 / 5

Workflow Clarity

Clear sequence (Do This First -> Clarify -> Deliverables -> Templates) with defined steps, but lacks an explicit validation/review checkpoint confirming the produced spec against the guidelines before delivery.

4 / 5

Progressive Disclosure

SKILL.md is an overview that delegates detailed rubric content to references/cli-guidelines.md (a real bundle file), one level deep and clearly signaled, with well-organized sections for easy navigation.

5 / 5

Total

19

/

20

Passed

Description

92%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 well-crafted description that clearly communicates both the capability (designing CLI parameters and UX) and the trigger conditions (designing or refactoring a CLI spec). Comprehensive action coverage and clear niche, with only minor gaps in trigger-term synonyms.

DimensionReasoningScore

Specificity

Enumerates many concrete CLI actions (arguments, flags, subcommands, help text, output formats, error messages, exit codes, prompts, config/env precedence, safe/dry-run), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly states what ('Design command-line interface parameters and UX...') and when ('Use when you're designing a CLI spec (before implementation) or refactoring...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural terms ('CLI spec', 'arguments, flags, subcommands', 'help text', 'exit codes') but missing common synonyms like 'command line tool', 'shell command', or 'flag parsing'; good but not exhaustive.

4 / 5

Distinctiveness Conflict Risk

Clear niche of CLI surface-area design with distinct triggers ('designing a CLI spec', 'refactoring an existing CLI's surface area'); minimal overlap with other skills.

5 / 5

Total

19

/

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
ollygarden/ollygarden-cli
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.