domain-cli
Use when building CLI tools. Keywords: CLI, command line, terminal, clap, structopt, argument parsing, subcommand, interactive, TUI, ratatui, crossterm, indicatif, progress bar, colored output, shell completion, config file, environment variable, 命令行, 终端应用, 参数解析
72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
37%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 with excellent keyword density including library names and multilingual terms, but critically fails to explain what the skill actually does. It reads more like a keyword list than a functional description, leaving Claude unable to understand the skill's capabilities beyond the general domain of CLI development.
Suggestions
Add specific actions the skill enables, e.g., 'Guides creation of CLI applications with argument parsing, interactive prompts, progress indicators, and colored output'
Restructure to lead with capabilities before the 'Use when' clause, following the pattern: '[What it does]. Use when [triggers].'
Consolidate the keyword list into natural prose that describes features rather than just listing library names
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions entirely. It only states 'Use when building CLI tools' without describing what the skill actually does - no verbs like 'parse', 'generate', 'create', or specific capabilities are mentioned. | 1 / 3 |
Completeness | While it has a 'Use when' clause, the 'what does this do' component is completely missing. The description never explains what capabilities or actions the skill provides - only when to use it and related keywords. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural keywords including common terms (CLI, command line, terminal), specific libraries (clap, structopt, ratatui, crossterm, indicatif), features (argument parsing, subcommand, progress bar, shell completion), and even multilingual terms (命令行, 终端应用, 参数解析). | 3 / 3 |
Distinctiveness Conflict Risk | The specific library names (clap, ratatui, crossterm) and CLI-specific terms provide some distinctiveness, but 'building CLI tools' is broad and could overlap with general Rust development or other programming skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
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 high-quality CLI domain skill that excels at conciseness and actionability through effective use of tables and a complete code example. The document efficiently maps domain constraints to Rust implementations. The main weakness is the lack of explicit workflow sequences with validation steps for multi-step CLI development tasks.
Suggestions
Add a workflow section showing the step-by-step process for building a CLI app (e.g., 1. Define args struct → 2. Add subcommands → 3. Implement handlers → 4. Test with --help → 5. Verify exit codes)
Include validation checkpoints for config layering setup (e.g., how to verify each layer is being read correctly)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for dense information delivery, minimal prose, and assumes Claude understands Rust and CLI concepts. Every section earns its place with no redundant explanations. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code example with clap derive macros. Includes concrete crate recommendations, specific patterns with implementation details, and clear fix recommendations in the mistakes table. | 3 / 3 |
Workflow Clarity | The 'Trace Down' section shows conceptual flow but lacks explicit step-by-step workflows with validation checkpoints. For CLI development involving config layering or error handling, there are no explicit verification steps or feedback loops. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, tables for quick reference, and explicit 'Related Skills' section pointing to other modules. Content is appropriately structured for a domain constraints document without unnecessary nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.