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, 命令行, 终端应用, 参数解析
69
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/domain-cli/SKILL.mdQuality
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 relies heavily on keyword stuffing rather than explaining what the skill actually does. While the trigger terms are comprehensive and well-chosen, the complete absence of concrete actions (what does this skill help Claude do?) makes it difficult to understand the skill's value proposition. The description needs to articulate specific capabilities like 'parse command-line arguments', 'build interactive terminal UIs', or 'add progress indicators'.
Suggestions
Add concrete actions describing what the skill does: e.g., 'Builds command-line applications with argument parsing, interactive TUIs, progress bars, and colored output using clap, ratatui, and crossterm.'
Restructure to lead with capabilities before the 'Use when' clause: describe the specific tasks Claude can help with (parsing args, creating subcommands, generating shell completions) rather than just listing library names.
Convert the keyword list into natural prose that explains functionality, keeping only the most essential trigger terms as explicit keywords.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Use when building CLI tools' without describing any concrete actions. It lists keywords/technologies but doesn't explain what the skill actually does (e.g., 'parse arguments', 'create progress bars', 'generate shell completions'). | 1 / 3 |
Completeness | While it has a 'Use when' clause, the 'what' is essentially missing - it only says 'building CLI tools' without explaining what capabilities or actions the skill provides. The keywords list doesn't substitute for describing actual functionality. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'CLI', 'command line', 'terminal', 'argument parsing', 'progress bar', 'colored output', plus specific library names (clap, ratatui) and even Chinese translations for international users. | 3 / 3 |
Distinctiveness Conflict Risk | The CLI/terminal focus provides some distinctiveness, but 'building CLI tools' is broad and could overlap with general Rust development skills or other language-specific CLI skills. The specific library names (clap, ratatui) help but aren't in the main description. | 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. It provides excellent reference material with executable code, clear crate recommendations, and common mistake patterns. The main weakness is the lack of explicit workflow guidance for building a CLI from scratch, though this may be intentional given its role as a domain constraints reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for quick reference, minimal prose, and assumes Claude knows Rust and CLI concepts. Every section adds value without explaining basics. | 3 / 3 |
Actionability | Provides complete, executable code example with clap derive macros. Includes specific crate recommendations, concrete patterns, and copy-paste ready CLI structure with proper error handling. | 3 / 3 |
Workflow Clarity | The 'Trace Down' section shows conceptual flow but lacks explicit step-by-step workflow for building a CLI. No validation checkpoints for the build process. The content is more reference-oriented than workflow-oriented. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, tables for quick scanning, and explicit 'Related Skills' section pointing to other modules. Content is appropriately structured for a domain skill file. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- actionbook/rust-skills
- Commit
1f4becd
- 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.