python-cli-patterns
CLI application patterns for Python. Triggers on: cli, command line, typer, click, argparse, terminal, rich, console, terminal ui.
73
59%
Does it follow best practices?
Impact
97%
5.10xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/python-cli-patterns/SKILL.mdQuality
Discovery
54%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has strong trigger term coverage with specific library names and natural user phrases, but it severely lacks specificity about what the skill actually does — 'CLI application patterns' is too vague. Adding concrete actions (e.g., 'build CLI apps with argument parsing, subcommands, help text, and rich terminal output') would significantly improve it.
Suggestions
Replace 'CLI application patterns for Python' with specific actions like 'Build Python CLI applications with argument parsing, subcommands, help text generation, and rich terminal output'.
Add a 'Use when...' clause that explicitly states when to select this skill, e.g., 'Use when the user wants to create or modify a command-line interface in Python'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'CLI application patterns for Python' which is vague and abstract. It does not list any concrete actions like 'parse arguments', 'create subcommands', 'display progress bars', or 'build interactive menus'. | 1 / 3 |
Completeness | The 'when' is partially addressed via 'Triggers on:' with a list of keywords, but the 'what' is extremely weak — 'CLI application patterns' doesn't explain what the skill actually does. The trigger clause is present but the what-component is insufficient for a score of 3. | 2 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms: 'cli', 'command line', 'typer', 'click', 'argparse', 'terminal', 'rich', 'console', 'terminal ui'. These cover common library names and natural phrases users would say. | 3 / 3 |
Distinctiveness Conflict Risk | The Python + CLI niche is somewhat specific, and the library names (typer, click, argparse, rich) help distinguish it. However, 'terminal', 'console', and 'command line' are broad terms that could overlap with shell scripting or other terminal-related skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid CLI patterns skill with excellent actionability — all code examples are concrete, executable, and cover the key aspects of Typer + Rich development. The main weaknesses are the lack of a clear development workflow or sequencing guidance, and the inability to verify referenced bundle files. Conciseness is good but could be tightened slightly by trimming some example boilerplate.
Suggestions
Add a brief workflow section showing the typical sequence for building a CLI app (e.g., 1. Create app skeleton → 2. Add commands → 3. Add rich output → 4. Test with --help → 5. Package)
Provide the referenced bundle files (typer-patterns.md, rich-output.md, configuration.md, cli-template.py) or remove the references to avoid dead links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but some sections like the Rich Output example include slightly more boilerplate than necessary (e.g., the full users list example). The quick reference tables are well-condensed. Minor verbosity in docstrings and comments that Claude would naturally produce. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready. The examples cover basic app setup, command groups, Rich output, and error handling with concrete, working Python code. The quick reference tables provide specific syntax patterns. | 3 / 3 |
Workflow Clarity | The skill presents patterns/recipes rather than a multi-step workflow, which is appropriate for a patterns skill. However, there's no guidance on the typical development sequence (e.g., scaffold → add commands → add rich output → package), and no validation steps like testing CLI output or verifying help text generation. | 2 / 3 |
Progressive Disclosure | The skill references external files (references/typer-patterns.md, references/rich-output.md, etc.) and assets, which is good structure. However, no bundle files were provided, so these references are unverifiable. The main content itself is well-sectioned but includes substantial inline content that could potentially be split into the referenced files for better organization. | 2 / 3 |
Total | 9 / 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
- NeverSight/skills_feed
- Commit
2d09b29
- 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.