cli-developer
tessl i github:jeffallan/claude-skills --skill cli-developerUse when building CLI tools, implementing argument parsing, or adding interactive prompts. Invoke for CLI design, argument parsing, interactive prompts, progress indicators, shell completions.
Review Score
67%
Validation Score
12/16
Implementation Score
42%
Activation Score
90%
Generated
Validation
Total
12/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
body_examples | No examples detected (no code fences and no 'Example' wording) |
Implementation
Suggestions 4
Score
42%Overall Assessment
This skill has excellent structure and progressive disclosure with a well-organized reference table, but critically lacks actionable content. It reads more like a job description than executable guidance - telling Claude what a CLI developer does rather than showing how to implement CLI features. The constraints sections (MUST DO/MUST NOT DO) are valuable but would benefit from concrete examples.
Suggestions
- Add at least one executable code example per language ecosystem (Node.js, Python, Go) showing basic CLI setup with argument parsing
- Replace the 'Role Definition' section with a quick-start example showing a minimal working CLI tool
- Add validation checkpoints to the Core Workflow, such as 'Verify startup time with `time ./cli --version`' after the Implement step
- Include concrete examples for key constraints like 'Handle SIGINT gracefully' with actual signal handling code
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill includes some unnecessary framing ('Senior CLI developer with 10+ years of experience') and role-playing context that Claude doesn't need. The reference table and constraints are efficient, but the 'Role Definition' section is verbose padding. |
Actionability | 1/3 | The skill provides no executable code examples, no concrete commands, and no copy-paste ready snippets. It describes what to do ('Build with appropriate CLI framework') but never shows how. The reference files are mentioned but the skill itself lacks any concrete implementation guidance. |
Workflow Clarity | 2/3 | The 5-step 'Core Workflow' provides a clear sequence but lacks validation checkpoints or feedback loops. For CLI development involving cross-platform testing and performance benchmarks, there's no explicit verification step or criteria for success at each stage. |
Progressive Disclosure | 3/3 | The reference table is well-structured with clear 'Load When' guidance, providing one-level-deep references to detailed materials. The organization separates concerns appropriately (design patterns, language-specific guides, UX patterns). |
Activation
Suggestions 1
Score
90%Overall Assessment
This is a solid skill description with excellent trigger term coverage and clear 'Use when' guidance. The main weakness is that the capabilities listed are somewhat categorical rather than describing specific concrete actions. The description effectively distinguishes itself from other skills through CLI-specific terminology.
Suggestions
- Add more specific concrete actions like 'parse command-line flags and options', 'generate shell completion scripts for bash/zsh', or 'implement colored terminal output' to improve specificity.
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (CLI tools) and lists several actions (argument parsing, interactive prompts, progress indicators, shell completions), but these are more categories than concrete specific actions like 'parse command-line flags' or 'generate bash completion scripts'. |
Completeness | 3/3 | Explicitly answers both what (CLI tools, argument parsing, interactive prompts, progress indicators, shell completions) and when ('Use when building CLI tools, implementing argument parsing, or adding interactive prompts') with clear trigger guidance. |
Trigger Term Quality | 3/3 | Good coverage of natural terms users would say: 'CLI tools', 'argument parsing', 'interactive prompts', 'progress indicators', 'shell completions' are all terms developers naturally use when seeking help with command-line interfaces. |
Distinctiveness Conflict Risk | 3/3 | Clear niche focused specifically on CLI development with distinct triggers like 'argument parsing', 'shell completions', and 'progress indicators' that are unlikely to conflict with general coding or other skills. |