Claude Code Command Builder

The documentation recommends allowed-tools restrictions, input validation, failure handling, and user confirmation, and warns against destructive operations. However, several examples use Bash(*), deployment scripts, rm, credentials, and external services without systematic data-flow disclosure, sensitive-data guidance, rollback boundaries, or confirmation requirements. No malware, credential theft, covert exfiltration, or other red-line risk is evident.

Core concepts, arguments, file references, validation, and error handling are covered with many reusable examples. Reliability is reduced because some examples use pseudocode-like conditionals, potentially ambiguous shell interpolation and execution semantics, and dependencies on scripts or reference files not supplied in this material. No verifiable execution or test evidence is present, so the static ceiling applies.

The frontmatter provides precise trigger phrases covering command creation, arguments, references, Bash, interaction, and best practices, and the documentation distinguishes project, personal, and plugin scope. Non-fit boundaries, runtime version requirements, and Chinese-language guidance are limited. Examples depend on Bash, npm, gh, kubectl, or remote services whose availability, including from mainland China, is not addressed.

The structure is reasonably progressive: SKILL.md, README, references, and examples provide layered guidance, troubleshooting, maintenance notes, version information, and update advice. However, frontmatter version 0.2.0 conflicts with the README's v0.1.0 history; the README's inventory does not fully match the supplied material; license and maintenance provenance are supplied mainly as metadata rather than clearly documented in the skill; and in-progress items lack a concrete update path.

The skill covers command structure, common frontmatter, dynamic arguments, file references, plugin-root usage, validation, and workflow patterns. The examples are directly reusable as templates and support the core task. It is not full-score evidence because examples were not executed, some syntax or tool behavior may require correction, and complex deployment patterns depend on external scripts, permissions, and environment-specific setup.

The supplied material includes auditable primary documentation, examples, checklists, and maintenance statements supporting the main claims. It lacks committed test suites, CI results, versioned behavior comparisons, or third-party execution evidence, and some referenced files are absent from the supplied evidence, so only limited static verifiability is justified.