ClawHub

AI-CLI Design

v1.0.0

Design CLI tools as local APIs for AI agents. TTY detection, --json output, stderr/stdout separation, exit codes. | 为 AI 设计 CLI 工具的规范：TTY 检测、JSON 输出、stderr/s...

⭐ 0· 57·0 current·0 all-time
by@dongsheng123132
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description claim to be a design spec for AI-friendly CLIs and the SKILL.md contains detailed, relevant guidance (TTY detection, stdout/stderr separation, --json contract, exit codes). References to Go snippets and a template are consistent with a docs/spec artifact.
ℹ
Instruction Scope
The instructions stay within scope of CLI design. Minor notes: the document references a Go import (golang.org/x/term) and a templates/tty.go.tmpl which are not included in the skill — that's expected for a spec but users should know the skill does not provide runnable code. Example usage shows piping stderr to /dev/null; that's a client-side choice and can hide diagnostics if used blindly.
✓
Install Mechanism
No install specification or code is present (instruction-only), so nothing will be downloaded or written to disk by the skill itself — this is the lowest-risk install profile.
✓
Credentials
The skill does not request environment variables, credentials, or config paths. The guidance about separating logs from machine-readable output is appropriate; implementers should still avoid emitting secrets on stdout/stderr.
✓
Persistence & Privilege
The skill is user-invocable and not marked always:true. It does not request persistent presence or modify other skills/configurations.
Assessment
This is a documentation/spec skill for building AI-friendly CLI tools — it does not request credentials or install code and appears coherent and safe. If you expected runnable templates or binaries, note they are not included here; verify any third-party templates or implementations before using. When implementing the spec, ensure your program never prints secrets to stdout/stderr and test both TTY and non-TTY modes. Be cautious when piping stderr to /dev/null in production because it discards diagnostic information.

Like a lobster shell, security has layers — review code before you run it.

latestvk977k2z42qmht48c3xsxg4jb9183v979

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments