cli-patterns
Patterns for building production-quality CLI tools with predictable behavior, parseable output, and agentic workflows. Triggers: cli tool, command line tool, build cli, cli patterns, agentic cli, cli design, typer cli, click cli.
87
Quality
86%
Does it follow best practices?
Impact
94%
1.64xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
72%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 description has strong trigger term coverage and clear distinctiveness for CLI tool development, but lacks concrete action verbs describing what the skill actually teaches. The absence of an explicit 'Use when...' clause and reliance on a 'Triggers:' list rather than natural prose weakens completeness.
Suggestions
Add specific concrete actions like 'implement argument parsing, create subcommands, design help text, structure output for machine parsing'
Convert the 'Triggers:' list into a natural 'Use when...' clause, e.g., 'Use when building command line tools, designing CLI interfaces with typer or click, or creating tools for agentic workflows'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CLI tools) and mentions some qualities (predictable behavior, parseable output, agentic workflows) but doesn't list concrete actions like 'create argument parsers', 'implement subcommands', or 'generate help text'. | 2 / 3 |
Completeness | The 'what' is partially addressed (patterns for CLI tools with certain qualities), but there's no explicit 'Use when...' clause. The 'Triggers:' list helps but doesn't fully substitute for explicit guidance on when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'cli tool', 'command line tool', 'build cli', 'typer cli', 'click cli', 'cli design', 'agentic cli'. These are terms users would naturally use when seeking CLI development help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on CLI tool development patterns with distinct triggers like 'typer cli', 'click cli', and 'agentic cli'. Unlikely to conflict with general coding or other development skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill document that demonstrates excellent CLI design patterns with comprehensive, actionable guidance. The content is well-organized with tables for quick reference, executable code examples, and clear separation between overview content and detailed references. The anti-patterns section adds significant value by showing what to avoid alongside the recommended approaches.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is dense with actionable information and avoids explaining concepts Claude already knows. Tables and code examples are efficient, and every section earns its place without unnecessary padding or explanations of basic concepts. | 3 / 3 |
Actionability | Provides fully executable code examples, specific naming conventions with valid/invalid examples, concrete flag specifications, and copy-paste ready patterns. The implementation patterns and error handling code are directly usable. | 3 / 3 |
Workflow Clarity | Clear hierarchical structure with explicit command architecture, well-defined action sequences, and validation checkpoints (exit codes, error handling patterns). The anti-patterns section provides explicit feedback on what to avoid. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to implementation.md and json-schemas.md. Content is appropriately split between the main skill and reference files, with clear navigation via inline links. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (633 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
5342bca
- 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.