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 specific library names and natural user phrases, but it severely lacks specificity about what the skill actually does — 'CLI application patterns' is too abstract. 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, or mentions libraries like typer, click, or argparse'.
| 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. There's no explicit 'Use when...' clause, but the 'Triggers on:' serves a similar function, so it narrowly avoids a 1. | 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 enough to potentially overlap with shell scripting or general terminal usage 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 a well-crafted skill that efficiently covers Python CLI patterns with Typer and Rich. It provides executable, copy-paste-ready code examples organized in a logical progression from basic to advanced, with clean reference tables and well-signaled pointers to deeper resources. The content respects Claude's intelligence by avoiding unnecessary explanations while remaining highly actionable.
| 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 → output → error handling, forming a clear progression for building a CLI app. | 3 / 3 |
Progressive Disclosure | The main file provides a concise overview with working examples, then clearly signals one-level-deep references for advanced topics (typer-patterns.md, rich-output.md, configuration.md). Related and complementary skills are well-organized in a 'See Also' section. | 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
f772de4
- 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.