Error Handling
affaan-m/ECC
Patterns for robust error handling across TypeScript, Python, and Go.
Design a CLI interface: args, flags, help, output, errors, exit codes, config.
MITAuto-check: notes
Install CLI Design
$ npx skills add notque/vexjoy-agent --skill cli-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install notque/vexjoy-agent cli-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/engineering/cli-design .claude/skills/cli-design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cli-design" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/engineering/cli-design into .claude/skills/cli-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/notque/vexjoy-agent/tree/main/skills/engineering/cli-designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add notque/vexjoy-agent --skill cli-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install notque/vexjoy-agent cli-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/engineering/cli-design .agents/skills/cli-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cli-design" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/engineering/cli-design into .agents/skills/cli-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add notque/vexjoy-agent --skill cli-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install notque/vexjoy-agent cli-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/engineering/cli-design .cursor/skills/cli-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cli-design" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/engineering/cli-design into .cursor/skills/cli-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/notque/vexjoy-agent.git --path skills/engineering/cli-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add notque/vexjoy-agent --skill cli-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install notque/vexjoy-agent cli-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/engineering/cli-design .gemini/skills/cli-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cli-design" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/engineering/cli-design into .gemini/skills/cli-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install notque/vexjoy-agent cli-designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add notque/vexjoy-agent --skill cli-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/engineering/cli-design .github/skills/cli-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cli-design" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/engineering/cli-design into .github/skills/cli-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add notque/vexjoy-agent --skill cli-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install notque/vexjoy-agent cli-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/engineering/cli-design .opencode/skills/cli-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cli-design" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/engineering/cli-design into .opencode/skills/cli-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cli-design- GitHub stars
- 435
- Token cost
- ~946 tokens
- SKILL.md length
- 462 words
- Files
- 2 (incl. references)
- Skills in repo
- 61
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design a CLI interface: args, flags, help, output, errors, exit codes, config.
- Works in 3 steps: SCOPE → DESIGN → DELIVER
- SKILL.md covers Deep References, Workflow, Constraints and Error handling
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
CLI Design is an agent skill from notque/vexjoy-agent. Design a CLI interface: args, flags, help, output, errors, exit codes, config.
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/clig-checklist.md`).
The repository describes itself as: VexJoy AI Agent with Jev Intelligent Routing - /do routes plain-English requests to the right specialist agent and gates the work with reviews, tests, and a learning loop. The licence is MIT.
Example prompts
- “/cli-design”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Grep, Glob, Bash
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5218674. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteGrepGlobBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
CLI Design loads about 946 tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 22 tokens; SKILL.md has 462 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Grep, Glob, Bash
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from notque/vexjoy-agent at commit 5218674, republished under its MIT licence (© notque). 462 words, ~946 tokens.
Download SKILL.mdSave it as
.claude/skills/cli-design/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- cli-design
- description
- Design a CLI interface: args, flags, help, output, errors, exit codes, config.
- allowed-tools
- Read, Write, Grep, Glob, Bash
- user_invocable
- false
- routing.triggers
- design a CLI, CLI interface, command line tool design, CLI flags, CLI spec, argument parsing design, exit codes
- routing.category
- engineering
- routing.pairs_with
- testing, code-quality
CLI Design
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).
Deep References
| When | Load | Content |
|---|---|---|
| Phase 2: applying design rubric | references/clig-checklist.md | CLI design checklist condensed from clig.dev |
Workflow
Phase 1: SCOPE
Lock the interface with the minimum questions. Proceed with the conventions in Phase 2 when the user is unsure.
- Command name and one-sentence purpose.
- Primary user: humans, scripts, or both.
- Input sources: args vs stdin; files vs URLs. Secrets travel via file or stdin, because flags leak through
psand shell history. - Output contract: human text,
--json,--plain, exit codes. - Interactivity: prompts allowed?
--no-inputneeded? confirmation for destructive ops? - Config model: flags, env, config file; precedence.
Gate: name, purpose, and I/O contract are known. Proceed only when gate passes.
Phase 2: DESIGN
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.
Phase 3: DELIVER
Produce the spec from this skeleton. Drop a section only when it genuinely has no content; fill every other section.
- Name and one-liner: command name plus a single sentence of purpose
- Usage line: the synopsis as
--helpwill print it, global flags and subcommand slot included - Subcommands: purpose of each, whether it mutates state, whether re-running it is safe
- Args/flags table: columns for name, type, default, required?, example
- I/O contract: primary data and machine-readable output on stdout; everything else (errors, progress, logs) on stderr
- Exit codes: map each failure mode to a code — success
0, failure1, bad usage2; mint extra codes only for cases scripts must distinguish - Safety:
--dry-run, confirmation rules,--force,--no-input - Env/config: env vars; config file path; precedence order with flags highest, then env, project config, user config, system
- Examples: enough invocations to cover the common flows; show at least one pipeline or stdin use
Show full SKILL.md (115 more words)Show less
Gate: every flag used in the examples appears in the flags table, and every failure mode shown maps to an exit code.
Constraints
- Stay at spec altitude: when the request is "design the interface," deliver the spec and stop. Implementation is a separate task.
- Keep the spec language-agnostic. Recommend a parsing library only when asked.
- Target Linux. Skip Windows/macOS path, signal, and packaging concerns.
Error handling
Request mixes design and implementation
Cause: user says "design and build." Solution: deliver the spec first, get confirmation, then implement against it.
Spec balloons past one page
Cause: subcommand sprawl or speculative flags. Solution: cut flags that lack a named user need; defaults should serve most users without aliases.
© notque, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/engineering/cli-design of notque/vexjoy-agent.
- SKILL.md
- references/clig-checklist.md
Open the folder on GitHubat commit 5218674
Compare with similar skills
CLI Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CLI Design this skillnotque/vexjoy-agent | 435 | — | ~946 | Automated safety check: Notes | MIT | |
| Error Handlingaffaan-m/ECC | 274k | 1 repos | ~2.7k | Automated safety check: Pass | MIT | |
| Error Handlingthedaviddias/Front-End-Checklist | 74k | — | ~416 | Automated safety check: Pass | MIT | |
| Error Handlingaffaan-m/ECC | 274k | — | ~2.4k | Automated safety check: Pass | MIT | |
| N8n Error Handlingsickn33/agentic-awesome-skills | 47k | 1 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Network Interface Healthaffaan-m/ECC | 274k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Error Handling
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling.
Error Handling
affaan-m/ECC
TypeScript、Python、Goにわたる堅牢なエラー処理のパターン。型付きエラー、エラー境界、リトライ、サーキットブレーカー、ユーザー向けエラーメッセージをカバーします。
N8n Error Handling
sickn33/agentic-awesome-skills
Design visible, structured, recoverable n8n failures using error outputs, retries, Error Trigger workflows, and HTTP error responses.
Network Interface Health
affaan-m/ECC
Diagnose interface errors, drops, CRCs, duplex mismatches, flapping, speed negotiation issues, and counter trends on routers, switches, and Linux hosts.
Error Handling Patterns
wshobson/agents
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications.
More from notque/vexjoy-agent
All 61 skills in this repoGame Asset Generator
notque/vexjoy-agent
Deterministic palette/matrix pixel art (not AI). An agent skill from notque/vexjoy-agent.
PR Workflow
notque/vexjoy-agent
Pull request lifecycle: commit, codex review, sync, review, fix, status, cleanup, and PR mining.
Architecture Deepening
notque/vexjoy-agent
Improve architecture across modules by deepening interfaces.
Code Quality
notque/vexjoy-agent
Code quality: cleanup, linting, formatting, quality gates. An agent skill from notque/vexjoy-agent.
Codebase Analyzer
notque/vexjoy-agent
Statistical rule discovery from Go codebase patterns. An agent skill from notque/vexjoy-agent.
Comment Quality
notque/vexjoy-agent
Review and fix temporal references in code comments. An agent skill from notque/vexjoy-agent.
Questions about CLI Design
What does CLI Design do?
Design a CLI interface: args, flags, help, output, errors, exit codes, config. CLI Design is an agent skill from notque/vexjoy-agent. Design a CLI interface: args, flags, help, output, errors, exit codes, config.
How do I install CLI Design in Claude Code?
Run `npx skills add notque/vexjoy-agent --skill cli-design -a claude-code`. Or copy the skill folder (skills/engineering/cli-design in notque/vexjoy-agent) into .claude/skills/cli-design in your project. Claude Code loads it when a task matches its description.
How do I install CLI Design in Codex?
Run `npx skills add notque/vexjoy-agent --skill cli-design -a codex`. Or copy the skill folder (skills/engineering/cli-design in notque/vexjoy-agent) into .agents/skills/cli-design in your project. Codex loads it when a task matches its description.
Can I use CLI Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add notque/vexjoy-agent --skill cli-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cli-design, .gemini/skills/cli-design, .github/skills/cli-design and .opencode/skills/cli-design in your project.
What does CLI Design need to run?
SKILL.md names no scripts, command-line tools or credentials: CLI Design is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Grep, Glob, Bash.
Does CLI Design access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is CLI Design safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does CLI Design use?
CLI Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does CLI Design use?
About 946 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
What are the alternatives to CLI Design?
Skills that share tags, products or a category with CLI Design: Error Handling (affaan-m/ECC, 274k stars), Error Handling (thedaviddias/Front-End-Checklist, 74k stars), Error Handling (affaan-m/ECC, 274k stars) and N8n Error Handling (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CLI Design?
notque (a GitHub user) maintains it in notque/vexjoy-agent, which has 435 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on October 3, 2026.
Source: notque/vexjoy-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.