CLI Spec

Create and validate implementation-grade CLI specifications when command trees, JSON contracts, dry-run plans, errors, or agent-ready behavior need a binding spec.

9 stars 4 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jscraik/Agent-Skills --skill cli-spec
Manual install
git clone --depth 1 https://github.com/jscraik/Agent-Skills.git /tmp/Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Agent-Skills/Skills/backend-platform/cli-spec ~/.claude/skills/cli-spec

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# CLI Spec

## Philosophy
- Keep the skill focused on the decision and workflow the user actually requested.
- Preserve important context through progressive disclosure instead of trimming it away.
- Prefer repo-local contracts, wrappers, and validation before generic advice.

## When To Use
- The user requests a CLI specification for a new or existing command-line interface.
- Command trees, JSON schemas, dry-run plans, errors, or safety gates need to be defined.
- Agent-ready CLI behavior needs a binding implementation contract.

## Avoid
- Implementing the CLI when the user only asked for a spec.
- Generic product requirements with no command-line surface.
- Specs that omit machine-readable output and failure behavior.

## Inputs
- CLI goal
- target users and agents
- command tree
- state-changing operations
- output and error requirements

## Outputs
- CLI implementation contract
- JSON output schemas
- dry-run behavior
- error model
- validation plan
- Schema-bound outputs include schema_version.

## Workflow
- Start with 2-3 focused surfaces before expanding scope.
- Clarify the CLI job, audiences, and state-changing operations.
- Define commands, flags, positional args, and examples.
- Specify JSON output, errors, dry-run plans, and idempotency.
- Add agent-readiness expectations for parseable output and exit codes.
- Store the spec in the repo convention and validate references.

## Constraints
Read the full skill on GitHub

Details

Skill name
cli-spec
Path
Skills/backend-platform/cli-spec/SKILL.md
License
Apache-2.0
Repo updated
16 November 2026

FAQ

What does the CLI Spec skill do?

Create and validate implementation-grade CLI specifications when command trees, JSON contracts, dry-run plans, errors, or agent-ready behavior need a binding spec.

How do I install the CLI Spec skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jscraik/Agent-Skills --skill cli-spec. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is CLI Spec popular?

It lives in jscraik/Agent-Skills, which has 9 GitHub stars and 4 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.