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.
76
93%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly communicates its specific niche (agent-friendly CLI design), lists concrete capabilities, and provides explicit trigger guidance. It uses proper third-person voice and includes natural keywords that users would actually say. The description is concise yet comprehensive, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and features: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Also specifies both designing and reviewing CLIs. | 3 / 3 |
Completeness | Clearly answers both 'what' (designs/reviews CLIs with specific features for agent reliability) and 'when' (explicit 'Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'CLI', 'commands', '--help', 'agents', 'terminals', 'automation-friendly', 'coding agents', 'pipelines', 'dry-run'. Good coverage of terms a user building agent-friendly CLIs would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche: CLI design specifically for coding agents and automation. The focus on agent-friendly, non-interactive, automation patterns distinguishes it from general CLI or general coding skills. | 3 / 3 |
Total | 12 / 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 high-quality skill that efficiently communicates CLI design patterns for agent-friendly interfaces. Its greatest strengths are conciseness and actionability—every section delivers concrete examples without unnecessary explanation. The only notable weakness is that the review/workflow aspect could benefit from a more structured sequence with explicit validation checkpoints rather than a flat checklist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what CLIs are or how agents work—concepts Claude already knows. Every section delivers a specific, actionable pattern without padding. The brief 'Bad/Good' comparisons are particularly token-efficient. | 3 / 3 |
Actionability | The skill provides concrete, copy-paste-ready examples for every pattern: flag syntax, --help output format, error message format, success output format, stdin/pipeline chaining. These are specific enough to directly apply when building or reviewing a CLI. | 3 / 3 |
Workflow Clarity | The skill covers many important design principles clearly, but it reads more as a checklist of design patterns than a sequenced workflow. The 'When reviewing an existing CLI' section is a flat checklist without validation steps or feedback loops. For a design/review skill involving potentially destructive operations (deploy, --force), the lack of explicit verification steps is a minor gap. | 2 / 3 |
Progressive Disclosure | For a standalone skill under 100 lines with no need for external references, the content is well-organized into clearly labeled, scannable sections. Each section is self-contained and appropriately sized. No monolithic walls of text or unnecessary nesting. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- cursor/plugins
- Commit
b8f2564
- 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.