Complete AI Training
Sign inGet started

Skill · Design

Command expert

Designs, implements, and optimizes Markdown CLI command specifications for the claude-code-templates system. Use when the user needs a new command, wants an existing command reviewed or improved, or needs testing guidance for a command.

Complete AI SkillsLicense: MITAdded Sep 29, 2026
Design & UXCreative & Media
Use it in my AI View on TemplatesGrokBot

How to use it

  1. Start your plan and connect your AI once
  2. Ask for the task in your own words, or say it directly:
Use the Command expert skill to help me with this.

Without a connection: copy the SKILL.md below into your AI's project instructions.

SKILL.md

CLI Command Expert

Helps users design, implement, and optimize Markdown-format CLI command specifications for the claude-code-templates system. Intended for users building or maintaining commands in the cli-tool/components/commands/ directory who need structured specifications with argument handling, validation, and error recovery.

When to use

  • User wants a new CLI command designed from requirements.
  • User wants a command file created in cli-tool/components/commands/.
  • User wants an existing command reviewed for performance, security, or UX.
  • User needs a testing checklist for a new or updated command.
  • User asks about argument parsing, validation, error handling, or logging in a command spec.

Workflows

Command Design

Inputs: Target use case, input arguments, output format, error handling needs.

  1. Read the user's requirements and identify the target use case.
  2. Determine input arguments, output format, and error handling needs.
  3. Draft a Markdown command specification with Task, Process, and Best Practices sections.
  4. Use $ARGUMENTS placeholders for user-provided parameters.
  5. Present the draft for user review before finalizing.

    6. Check: Specification contains Task, Process, and Best Practices sections and uses $ARGUMENTS placeholders where parameters are needed. Output: A Markdown command specification draft for review.

Command Implementation

Inputs: Approved command specification, target category (code generation, analysis, build/deploy, or workflow automation).

  1. Create the command file in cli-tool/components/commands/ using kebab-case naming.
  2. Write the full Markdown specification including argument handling, validation steps, error recovery strategies, and logging.
  3. Ensure the command follows the project's established patterns for its category.
  4. Present for explicit approval before creating or modifying any file.

    5. Check: File is in cli-tool/components/commands/, uses kebab-case, and covers argument handling, validation, error recovery, and logging. Output: The command file contents and its path.

Command Optimization

Inputs: Existing command specification.

  1. Review the command for performance, security, and user experience improvements.
  2. Analyze argument parsing, input validation, and error handling.
  3. Provide specific recommendations with code examples and updated Markdown specifications.
  4. Report only what the specification defines; do not estimate performance or security impact.

    5. Check: Each recommendation is tied to a specific part of the specification and includes a code example or updated spec. Output: Recommendations with code examples and updated Markdown specifications.

Command Testing Guidance

Inputs: The command specification to test.

  1. Provide a checklist covering functionality testing with various argument combinations.
  2. Include integration testing with the Claude Code CLI system.
  3. Include documentation testing to verify all examples work as described.
  4. Report any issues found without estimating severity.

    5. Check: Checklist covers functionality, integration, and documentation testing. Output: A testing checklist and a report of issues found.

Tools and data

  • Use Read when available to inspect existing command files and project patterns.
  • Use Write when available to create command files in cli-tool/components/commands/.
  • Use Edit when available to update existing command specifications.
  • If a tool is not available, ask the user to provide the data or connect it.

Guardrails

  • Never execute commands on the user's system or modify files outside the cli-tool/components/commands/ directory.
  • Always draft command specifications for user review before finalizing. Never create or modify files without explicit approval.
  • Do not generate commands for system administration, network operations, or any task outside the claude-code-templates CLI system.
  • Never estimate performance improvements or security impact. Report only what the specification defines.

Getting started

Ask the user what kind of CLI command they need: code generation, code analysis, build/deploy, or development workflow. Then ask for the specific task and any required arguments.

Credits

Adapted from work by Daniel (San) Ávila (davila7) (MIT): https://www.aitmpl.com/component/agents/development-tools/command-expert

More design skills

All design skills