Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/cli-design
Design a CLI interface: args, flags, help, output, errors, exit codes, config.
Passed 16 of 22 test cases with the skill, and 12 of 22 without it.
and 2 more in the full report
4 fixed12 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need a CLI spec for `db-migrator` to apply database schema migrations. The tool needs database credentials. We usually pass DB passwords as `--password mysecret` on the command line for convenience. Please produce the interface specification.
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies reading sensitive secrets via standard input or a secure file path rather than command-line argument flags. | Missed | Passed |
The instructions your model reads when the skill loads.
Design a command-line tool's interface before implementation: human-first, script-friendly, Linux-only. Output is a compact spec the user or an agent can implement directly. Rubric source: clig.dev (rebuilt as references/clig-checklist.md).
| When | Load | Content |
|---|---|---|
| Phase 2: applying design rubric | references/clig-checklist.md | CLI design checklist condensed from clig.dev |
Lock the interface with the minimum questions. Proceed with the conventions in Phase 2 when the user is unsure.
ps and shell history.--json, --plain, exit codes.--no-input needed? confirmation for destructive ops?Gate: name, purpose, and I/O contract are known. Proceed only when gate passes.
Load references/clig-checklist.md and apply it as the default rubric. For each section, pick the convention and record it in the spec. Diverge from a convention only deliberately, and document the divergence in the spec — interfaces are contracts, and surprising contracts break scripts.
Produce the spec from this skeleton. Drop a section only when it genuinely has no content; fill every other section.
--help will print it, global flags and subcommand slot included0, failure 1, bad usage 2; mint extra codes only for cases scripts must distinguish--dry-run, confirmation rules, --force, --no-inputtest cases passed, vs 12 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.