python-cli-patterns
CLI application patterns for Python. Triggers on: cli, command line, typer, click, argparse, terminal, rich, console, terminal ui.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill python-cli-patternsOverall
score
83%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%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 and clear distinctiveness for Python CLI development, but lacks specificity about what concrete actions or patterns it provides. The 'Triggers on:' format partially addresses when to use it, but the capability description is too abstract to help Claude understand what this skill actually teaches.
Suggestions
Replace 'CLI application patterns' with specific actions like 'Build command-line interfaces, parse arguments, create subcommands, add progress bars and formatted output'
Convert 'Triggers on:' to a proper 'Use when...' clause that describes user intent, e.g., 'Use when building Python CLI tools, adding command-line arguments, or creating terminal interfaces'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CLI applications for Python) and mentions specific tools (typer, click, argparse, rich), but doesn't describe concrete actions like 'create commands', 'parse arguments', or 'build interactive menus'. | 2 / 3 |
Completeness | The 'when' is addressed via 'Triggers on:' with good keywords, but the 'what' is weak - 'CLI application patterns' doesn't explain what actions or capabilities the skill provides. Missing explicit 'Use when...' clause format. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'cli', 'command line', 'terminal', 'console', plus specific library names (typer, click, argparse, rich) that users familiar with Python CLI development would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Python CLI development specifically. The combination of Python context with CLI-specific tools (typer, click, argparse) and UI libraries (rich) creates a distinct trigger profile unlikely to conflict with general Python or general CLI skills. | 3 / 3 |
Total | 10 / 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 strong CLI patterns skill that provides concise, executable examples for Typer and Rich without unnecessary explanation. The progressive disclosure is excellent with clear references to advanced materials. The main weakness is the lack of explicit workflow guidance for building and testing a complete CLI application.
Suggestions
Add a brief 'Getting Started' workflow section showing the sequence: create app → add commands → test locally → handle errors
Include a validation step or testing pattern (e.g., 'Test with: python myapp.py --help' after each major addition)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing executable code examples without explaining what CLIs are or how Typer/Rich work conceptually. Every section delivers actionable patterns without padding. | 3 / 3 |
Actionability | All code examples are complete and executable, with proper imports, function definitions, and usage comments. The quick reference tables provide copy-paste ready syntax patterns. | 3 / 3 |
Workflow Clarity | The skill presents patterns clearly but lacks explicit workflow sequencing for building a CLI app from scratch. There are no validation checkpoints or feedback loops for testing CLI behavior. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, well-organized sections, and clear one-level-deep references to additional resources (typer-patterns.md, rich-output.md, etc.) and related skills. | 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 | |
- 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.