Ai Cli Architecture
v1.0.0AI CLI 产品的工程架构与迭代策略。当需要设计、开发、或迭代 AI 命令行工具类产品时使用，包括：功能模块化设计、渐进式版本规划、Feature Flag 机制、多后端适配、权限系统、Hook 系统、上下文管理、会话恢复、诊断工具、审计追责、可观测性、信任链设计、状态机思维等。触发场景：构建 AI CLI、规...
⭐ 1· 46·0 current·0 all-time
by@wuritu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe architecture and iteration patterns for AI CLI products; the package is instruction-only and requests no binaries, env vars, or installs — which is proportional to a patterns/architecture guide.
Instruction Scope
SKILL.md is a design/reference document (checklists, architecture patterns). It recommends that implementations consider workspace context (git status/branch), environment facts, and user/auth context. The skill does not itself instruct reading secrets or executing commands, but the guidance explicitly suggests accessing workspace and auth information when implementing these patterns — implementers should ensure such accesses are scoped and audited.
Install Mechanism
No install spec or code files to write/execute. Instruction-only skills are low-risk from an installation perspective.
Credentials
The skill declares no required environment variables, credentials, or config paths. Although the guidance discusses using environment facts and auth info in a product design, the skill itself does not request secrets or unrelated credentials.
Persistence & Privilege
always is false and the skill has no install-time persistence. It requests no system-level privileges or modifications; autonomous model invocation is allowed by platform default but not a red flag here.
Assessment
This skill is a patterns-and-checklist document (no code, no installs) and appears coherent with its stated purpose. Before using it as the basis for a runtime agent or installing any implementation derived from it, consider: - If you or a developer implement these patterns, be careful: the guidance recommends reading workspace context (git, files) and auth info — limit and audit any such accesses. - Do not hand over credentials or broad filesystem access to an agent implementation without least-privilege controls, explicit feature flags, and audit trails. - If someone provides a concrete implementation (code or an installer) based on this guide, review its install mechanism, network endpoints, and required env vars before enabling it in production. - Use feature flags/approval gates, run in staging first, and ensure comprehensive logging and an audit chain as the guide itself recommends.Like a lobster shell, security has layers — review code before you run it.
latestvk970v54gc2s7bvyff75massthx8419x5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.