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

—

Does it follow best practices?

Impact

94%

1.64x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is a highly actionable, well-structured pattern catalog with strong executable examples, but it is over-long for SKILL.md with redundant tables, lacks validation feedback loops for destructive operations, and references bundle files that are not present.

Suggestions

Create the referenced references/json-schemas.md and references/implementation.md files and move the detailed JSON schema patterns and Typer/httpx implementation templates out of SKILL.md to reduce the inline body length.

Consolidate the overlapping Exit Codes and Error Codes tables into one authoritative table to remove redundancy.

Add an explicit validate-then-proceed feedback loop for destructive actions (e.g. confirm/test before delete) so workflow clarity can reach level 3.

Dimension	Reasoning	Score
Conciseness	The ~611-line body is mostly a dense, on-topic pattern catalog rather than padded concept explanation, but it carries redundancy (exit codes and error-code tables overlap, design axioms restate the principles table) and could be tightened, so it sits at level 2 rather than the lean level-3 anchor.	2 / 3
Actionability	It provides copy-paste-ready, executable guidance throughout — exit-code constants, the `_error` implementation, `is_interactive()` detection, the help template, and concrete CLI invocations — matching the level-3 anchor for fully executable code and specific examples.	3 / 3
Workflow Clarity	Patterns and a Must-Have checklist are well organized, but the skill describes destructive/batch operations (delete, create) with no explicit validate-then-proceed feedback loop, which caps workflow clarity at 2 per the rubric's feedback-loop guidance.	2 / 3
Progressive Disclosure	References to references/json-schemas.md and references/implementation.md are clearly signaled one level deep, but the referenced bundle files do not exist (no references/ directory) and large amounts of material that belongs in those files remain inline in a 611-line body, fitting the level-2 anchor.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 is third-person, distinct, and includes an explicit Triggers clause that covers natural user terms well. Its only weakness is that the capability statement names a domain and qualities rather than enumerating multiple concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain ('building production-quality CLI tools') and attributes ('predictable behavior, parseable output, agentic workflows') but lists only one action ('building') rather than multiple concrete actions like 'extract, fill, merge', so it falls short of the level-3 anchor.	2 / 3
Completeness	It answers both 'what' (patterns for building production-quality CLI tools with predictable/parseable/agentic behavior) and 'when' via an explicit 'Triggers:' clause, satisfying the level-3 requirement for explicit trigger guidance.	3 / 3
Trigger Term Quality	The explicit 'Triggers:' list covers natural terms users would say — 'cli tool', 'command line tool', 'build cli', 'typer cli', 'click cli' — giving good coverage of common variations, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The niche is clear — CLI design patterns for agentic workflows — and the distinctive triggers ('typer cli', 'click cli', 'agentic cli') make it unlikely to fire for unrelated skills, matching the level-3 anchor.	3 / 3
	Total	11 / 12 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
Commit: 26d37ce

Reviewed: 4 days 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.