python-cli-patterns

CLI application patterns for Python. Triggers on: cli, command line, typer, click, argparse, terminal, rich, console, terminal ui.

5.10x

Quality

68%

Does it follow best practices?

Impact

97%

5.10x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xdarkmatter/claude-mods/python-cli-patterns/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a lean, mostly executable patterns catalog with clear sectioning, but it lacks explicit multi-step workflows with validation and, critically, advertises reference and asset files that are absent from the bundle. Fixing the missing files and adding the missing imports would materially raise the score.

Suggestions

Create the referenced bundle files (references/typer-patterns.md, references/rich-output.md, references/configuration.md, assets/cli-template.py) or remove the dangling references.

Make each code block self-contained: add `import os` to the error-handling example and define or stub do_something() and process_file() so examples run as-is.

For destructive or batch CLI operations, add an explicit validate-then-proceed step so workflow_clarity can exceed 3.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with minimal prose ("Modern CLI development with Typer and Rich." plus short section headers), assuming Claude's competence, though the Quick Reference tables partially restate code and the See Also section adds minor redundancy.	4 / 5
Actionability	Examples are mostly executable and copy-paste ready, but minor gaps remain: process() calls undefined do_something(), the error-handling example uses os and process_file without importing them, and @app.command() decorators rely on app defined in earlier sections.	4 / 5
Workflow Clarity	Sections follow a sensible basic-to-advanced progression (Basic Typer App, Command Groups, Rich Output, Error Handling, Quick Reference), but there is no multi-step workflow with explicit validation checkpoints, so it fits the sequence-present-but-checkpoints-missing anchor.	3 / 5
Progressive Disclosure	The body is well structured and the Additional Resources / Assets references are clearly signaled one level deep, but the referenced files (./references/*.md, ./assets/cli-template.py) do not exist in the bundle, so the promised navigation is broken and disclosure is undermined.	3 / 5
	Total	14 / 20 Passed

Description

72%Weight 40%Scale 1-5

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, explicit trigger guidance and good distinctiveness via named libraries, but its capability statement is a generic category rather than concrete actions. Adding one or two specific verbs would lift specificity and completeness.

Suggestions

Replace the generic "CLI application patterns for Python" with concrete actions, e.g. "Build typed command-line apps with Typer and format rich terminal output."

Keep the strong explicit "Triggers on:" clause but consider also framing it as a "Use when..." sentence for a clearer when-clause.

Dimension	Reasoning	Score
Specificity	The phrase "CLI application patterns for Python" names the domain clearly but states a category ("patterns") rather than concrete actions like building apps, defining typed commands, or formatting terminal output, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It states both the what ("CLI application patterns for Python") and an explicit when ("Triggers on: ..."), but the what is generic rather than a list of concrete actions, so it sits just below the clearly-concrete anchor 5.	4 / 5
Trigger Term Quality	The trigger list "cli, command line, typer, click, argparse, terminal, rich, console, terminal ui" gives comprehensive coverage of natural user terms plus library synonyms and variations, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Specific library names (typer, click, argparse, rich) carve a clear niche with minimal conflict risk, though generic terms like "cli" and "terminal" create minor overlap with adjacent skills, fitting the mostly-distinct anchor.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Path: data/skills-md/0xdarkmatter/claude-mods/python-cli-patterns/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.