Engineer cli tools
Skill ImYourBoyRoy/agent-continuity-stack/skills/engineer-cli-tools
Repository-centered instructions, skills, memory conventions, client adapters, and lifecycle safeguards for consistent work across AI coding agents.
npx -y skills add ImYourBoyRoy/agent-continuity-stack --skill engineer-cli-toolsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 10 days oldThe repository was created 10 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Design, implement, package, or review cross-platform CLI tools. Use for command contracts, configuration precedence, structured output, exit codes, logging, resumability, packaging, and CLI tests—not incidental shell commands.
SKILL.md
2.8 KB, 496 tokens by cl100k_base, as published. Nobody here has run it
Engineer CLI Tools
Design the command contract before choosing internal architecture.
Establish the contract
Define:
- users and execution environments
- commands, arguments, flags, stdin, stdout, and stderr
- exit-code semantics
- interactive versus non-interactive behavior
- configuration sources and precedence
- machine-readable output and stability promises
- destructive actions, confirmation, and dry-run behavior
- cancellation, retries, idempotency, and resumability
Preserve existing behavior unless a breaking change is approved.
Configuration precedence
Use one documented hierarchy appropriate to the project, normally:
explicit CLI flag
environment variable
project configuration
user configuration
built-in default
Do not print secrets or include them in command history. Validate configuration early and identify the source of invalid values without exposing the values.
Architecture
- Keep argument parsing thin.
- Put business behavior behind testable functions or interfaces.
- Separate filesystem, network, process, and UI adapters.
- Use typed configuration where supported.
- Make repeated operations idempotent when possible.
- Write partial state atomically.
- Bound concurrency and retries.
- Preserve useful diagnostics while keeping normal stdout stable.
- Provide
--jsonor equivalent only when consumers benefit from a stable schema.
Read the applicable language guide:
references/python.mdreferences/node-typescript.mdreferences/rust.mdreferences/powershell.md
Cross-platform behavior
- Use platform path libraries rather than concatenating separators.
- Do not assume a POSIX shell, administrator privileges, or executable bits.
- Quote child-process arguments through structured APIs.
- Handle Unicode, spaces, long paths, signals, and terminal absence.
- Discover tools through configuration or PATH and report exact missing prerequisites.
- Keep install and uninstall operations reversible and narrowly scoped.
Test the contract
Test:
- help and version output
- valid and invalid arguments
- exit codes and stderr separation
- precedence conflicts
- paths with spaces and Unicode
- missing tools, files, credentials, and network
- interruption and retry behavior
- JSON schema when provided
- destructive-operation gates
Use the repository's approved validation path. Report untested platforms explicitly; do not infer cross-platform success from one host.
Output
Document the command contract, compatibility or breaking changes, configuration precedence, packaging impact, tests, and remaining platform uncertainty.