CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-for-agents

Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, actionable reference that assumes Claude's competence and backs every principle with a concrete example. The only minor gap is the absence of an explicit validation feedback loop in the review workflow, which holds workflow clarity at 4.

Suggestions

In the 'When reviewing an existing CLI' section, frame the checklist as an explicit validate-and-iterate loop (e.g., 'run the command headlessly, observe the error, fix the flag/help, re-run') to add a feedback checkpoint.

Consider showing one full end-to-end worked example (invocation -> failure -> corrected invocation -> success) to make the multi-step review path concrete.

Optionally move the review checklist into a short numbered sequence so the verification order is unambiguous.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: bullet lists, tight Bad/Good contrasts, and example blocks with no padding or explanation of concepts Claude already knows; every section earns its tokens.

5 / 5

Actionability

Concrete, copy-paste-ready invocations ('mycli deploy --env staging') plus full --help, error-message, and success-output example blocks cover the common cases with specific, executable patterns.

5 / 5

Workflow Clarity

The skill is principles-based rather than a sequenced procedure, but the 'When reviewing an existing CLI' section provides a clear verification checklist; it lacks an explicit validate->fix->retry feedback loop, keeping it just below 5.

4 / 5

Progressive Disclosure

Self-contained with well-organized section headers and no nested or buried references; nothing here belongs in a separate file, so the clean single-level structure earns the top score.

5 / 5

Total

19

/

20

Passed

Description

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

An excellent description: third-person voice, concrete capability list, explicit trigger clause with natural synonyms, and a distinct niche. It hits every anchor at the top of the scale with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ('non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure') with comprehensive coverage, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both what ('Designs or reviews CLIs so coding agents can run them reliably: ...') and when ('Use when building a CLI, adding commands, writing --help...') with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

The 'Use when...' clause covers natural synonyms users would say ('building a CLI, adding commands, writing --help, agents, terminals, or automation-friendly CLIs'), giving comprehensive keyword coverage; file extensions are not applicable to this domain.

5 / 5

Distinctiveness Conflict Risk

Clear niche (CLIs optimized for coding agents to run headlessly) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
cursor/plugins
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.