cli-patterns

Patterns for building production-quality CLI tools with predictable behavior, parseable output, and agentic workflows. Triggers: cli tool, command line tool, build cli, cli patterns, agentic cli, cli design, typer cli, click cli.

1.64x

Quality

73%

Does it follow best practices?

Impact

94%

1.64x

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/cli-patterns/SKILL.md

Quality

Content

61%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.

Highly actionable and well-structured, but overly long with redundant restatements and a progressive-disclosure failure: it references two bundle files that are not present and inlines the content that should live in them.

Suggestions

Add the missing references/implementation.md and references/json-schemas.md files (or remove the dangling links) so the body's 'See [references/...]' navigation actually resolves.

Consolidate the exit-code material (Exit Codes table, Error Codes table, Quick Reference checklist) into a single source of truth to reduce redundancy and shrink the body.

Move the full Python implementation templates and complete JSON response patterns into the reference files, keeping SKILL.md as a lean overview that links out to them.

Dimension	Reasoning	Score
Conciseness	The body largely assumes Claude's competence (no basic-concept padding) and is dense with tables and code, but at ~620 lines it has noticeable redundancy — exit codes recur in three places, the Core Principles and Design Axioms overlap, and the Quick Reference checklist restates earlier sections — so it could be tightened.	3 / 5
Actionability	It provides copy-paste-ready Python (is_interactive, the _error helper, exit-code constants, Typer skeleton), concrete flag/exit-code tables, a help-format template, and executable bash examples covering the common cases.	5 / 5
Workflow Clarity	This is a patterns catalog organized by topic rather than a sequenced build workflow; the Must-Have checklist gives a loose sequence, but there are no explicit validation/feedback checkpoints for the destructive (delete) and batch operations the skill describes.	3 / 5
Progressive Disclosure	The body is a 620-line monolithic reference that inlines implementation templates and JSON-schema detail while pointing to references/implementation.md and references/json-schemas.md — yet no references/ directory exists in the bundle, so those navigation links are broken.	2 / 5
	Total	13 / 20 Passed

Description

86%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.

A strong description with explicit trigger guidance and good keyword coverage; its main weakness is that the 'what' frames qualities rather than enumerating concrete actions. It is well-targeted with only minor overlap risk.

Dimension	Reasoning	Score
Specificity	The description names the domain ('building production-quality CLI tools') and a couple of attributes ('predictable behavior, parseable output, and agentic workflows'), but these are qualities rather than multiple discrete concrete actions, so it does not reach the 'several specific actions' anchor.	3 / 5
Completeness	It clearly states what the skill does ('Patterns for building production-quality CLI tools...') and provides explicit, concrete trigger guidance via the 'Triggers:' clause, satisfying both 'what' and 'when'.	5 / 5
Trigger Term Quality	The explicit 'Triggers:' list gives comprehensive natural coverage with synonyms ('cli tool', 'command line tool'), intent phrases ('build cli', 'cli design'), and framework names ('typer cli', 'click cli') that users would naturally say.	5 / 5
Distinctiveness Conflict Risk	The focus on production CLI design with Typer/Click and agentic workflows is a clear niche, but broad terms like 'cli tool' and 'command line tool' create minor overlap risk with closely related Python/CLI skills.	4 / 5
	Total	17 / 20 Passed

Validation

68%

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 — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (633 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing	Warning
referenced_paths_exist	Referenced path issues: 6 missing	Warning

	Total	11 / 16 Passed

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

Reviewed: about 22 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.