platform-cli
Design and implementation patterns for building command-line tools with modern UX. Use when designing a CLI, reviewing CLI UX, defining commands and flags, or implementing error handling and signal handling.
86
81%
Does it follow best practices?
Impact
96%
1.15xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 a solid skill description with explicit 'Use when' guidance and good trigger term coverage for CLI-related tasks. The main weakness is that the capabilities section uses somewhat abstract language ('design and implementation patterns') rather than listing specific concrete actions the skill enables.
Suggestions
Replace 'Design and implementation patterns' with specific actions like 'Define command structures, parse arguments, generate help text, handle errors gracefully'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CLI tools) and mentions several areas (commands, flags, error handling, signal handling), but doesn't list concrete actions like 'parse arguments', 'generate help text', or 'validate input'. The phrase 'design and implementation patterns' is somewhat abstract. | 2 / 3 |
Completeness | Clearly answers both what ('Design and implementation patterns for building command-line tools with modern UX') and when ('Use when designing a CLI, reviewing CLI UX, defining commands and flags, or implementing error handling and signal handling') with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'CLI', 'command-line', 'commands', 'flags', 'error handling', 'signal handling', 'UX'. These cover common variations of how users would describe CLI-related work. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on CLI/command-line tools with specific mentions of commands, flags, and signal handling creates a clear niche. Unlikely to conflict with general coding skills or other document-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates strong organization and token efficiency, serving as an effective index to CLI development patterns. However, it functions more as a navigation document than actionable guidance - the actual executable patterns and concrete examples are deferred to referenced files rather than provided inline. The troubleshooting section is generic and could apply to any skill.
Suggestions
Add at least one concrete, executable code example inline (e.g., a complete flag parsing snippet or signal handler implementation) to improve actionability
Include a validation checkpoint in the workflow, such as 'Verify exit codes match documented conventions' or 'Test Ctrl-C handling before deployment'
Replace the generic troubleshooting section with CLI-specific issues (e.g., 'Flag conflicts with existing conventions', 'Exit code doesn't match error type')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bullet points and brief descriptions without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides good structural guidance and references but lacks concrete, executable code examples. The rules are listed as summaries rather than copy-paste ready implementations, and actual patterns are deferred to referenced files. | 2 / 3 |
Workflow Clarity | The workflow section provides a 3-step process but lacks validation checkpoints or feedback loops. For a skill covering error handling and signal handling, explicit validation steps would strengthen the guidance. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview pointing to one-level-deep references (rules/_sections.md and references/cli-patterns.md). Content is appropriately split with well-signaled navigation to detailed materials. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- ravnhq/ai-toolkit
- Commit
7b466be
- 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.