python-cli-patterns
CLI application patterns for Python. Triggers on: cli, command line, typer, click, argparse, terminal, rich, console, terminal ui.
84
77%
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 relevant library names and user-facing keywords, but is very weak on specificity—it doesn't describe what concrete actions or patterns the skill teaches. The 'what' portion is essentially just a category label ('CLI application patterns for Python') rather than a list of capabilities. Adding concrete actions and a proper 'Use when...' clause would significantly improve this description.
Suggestions
Add specific concrete actions such as 'Build CLI apps with argument parsing, subcommands, help text generation, input validation, and rich terminal output'.
Replace 'Triggers on:' with a proper 'Use when...' clause, e.g., 'Use when the user wants to build a Python command-line application, parse arguments, create interactive terminal UIs, or work with libraries like typer, click, argparse, or rich.'
Narrow broad terms like 'terminal' and 'console' by qualifying them, e.g., 'Python terminal applications' to reduce conflict risk with shell or system administration skills.
| 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', 'generate help text', or 'build interactive prompts'. | 1 / 3 |
Completeness | The 'what' is weak (just 'CLI application patterns for Python') and the 'when' is partially addressed via 'Triggers on:' which serves as a proxy for 'Use when...' but lacks explicit guidance on when Claude should select this skill. The trigger list partially compensates but there's no explicit 'Use when...' clause. | 2 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'cli', 'command line', 'typer', 'click', 'argparse', 'terminal', 'rich', 'console', 'terminal ui'. These are terms users would naturally use when asking about building CLI apps in Python. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of Python CLI-specific tools (typer, click, argparse, rich) helps distinguish it, but 'terminal', 'console', and 'command line' are broad terms that could overlap with shell scripting skills, terminal emulator skills, or general Python development skills. | 2 / 3 |
Total | 8 / 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 excellent CLI patterns skill that is concise, actionable, and well-structured. It provides executable code examples covering the most common CLI development scenarios without unnecessary explanation. The progressive disclosure is well-handled with clear references to additional resources for advanced topics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It jumps straight into executable code examples without explaining what CLIs are, what Typer is, or other concepts Claude already knows. Every section delivers concrete patterns without padding. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready. The quick reference tables provide concrete syntax for common patterns. Usage comments show exact CLI invocations. | 3 / 3 |
Workflow Clarity | This is a pattern/reference skill rather than a multi-step destructive workflow, so explicit validation checkpoints aren't required. The sections are logically sequenced from basic app → command groups → rich output → error handling, forming a clear progression. | 3 / 3 |
Progressive Disclosure | The main file provides a concise overview with working examples, then clearly signals one-level-deep references for advanced patterns (typer-patterns.md, rich-output.md, configuration.md), assets, and related skills. Navigation is well-organized. | 3 / 3 |
Total | 12 / 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
9f4534c
- 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.