`bullpen skill validate`¶

Last updated: July 13, 2026

Validate installed Bullpen skill files against this CLI's embedded bundle

Usage¶

bullpen skill validate [OPTIONS]

Live Help¶

Validate installed Bullpen skill files against this CLI's embedded bundle

Usage: bullpen skill validate [OPTIONS]

Options:
      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --project
          Validate project-local directory

      --env <ENV>
          Target environment to connect to (overrides config.toml)

          [env: BULLPEN_ENV=]
          [possible values: staging, production]

      --path <PATH>
          Validate a custom directory path

      --claude
          Target Claude Code only

      --config <CONFIG>
          Path to a custom config.toml file (overrides $BULLPEN_CONFIG and the default location).

          Explicit --config and BULLPEN_CONFIG paths fail closed: if the file is missing, the CLI exits validation instead of silently loading defaults. Credentials still resolve via BULLPEN_HOME, so set BULLPEN_HOME too when isolating a session.

      --openclaw
          Target OpenClaw only

      --codex
          Target Codex (OpenAI) only

      --gemini
          Target Gemini only

      --read-only
          Enable read-only mode: blocks all mutating commands

      --non-interactive
          Suppress interactive prompts; does NOT imply --yes for money-moving commands

          [env: BULLPEN_NON_INTERACTIVE=]

  -h, --help
          Print help (see a summary with '-h')

EXAMPLES:
  # Validate the Codex skill install
  bullpen skill validate --codex

  # Validate a custom skill path as JSON
  bullpen skill validate --path /tmp/bullpen-cli-skill --output json

Example Commands¶

bullpen skill validate --codex
bullpen skill validate --path /tmp/bullpen-cli-skill --output json
bullpen skill validate --codex --output json

JSON Output¶

Contract: JSON Output Contract.

Successful output is a single JSON document. The shape below is representative for this command family; commands may add fields without breaking the shared contract.

Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.

Top-level Keys¶

key	type	nullable	notes
`status`	string	no	`ok`, `needs_update`, or `no_platforms`
`checked`	integer	no	Total embedded skill files checked across target locations
`missing`	integer	no	Number of expected files missing from target locations
`stale`	integer	no	Number of files that differ from the embedded bundle
`locations`	array	yes	Per-target validation rows with `label`, `path`, `checked`, `missing`, and `stale`
`message`	string	yes	Human-readable detail for `no_platforms` responses

Example¶

bullpen skill validate --codex --output json

{
  "status": "ok",
  "checked": 36,
  "missing": 0,
  "stale": 0,
  "locations": [
    {
      "label": "Codex",
      "path": "/Users/alice/.codex/skills/bullpen-cli",
      "checked": 36,
      "missing": 0,
      "stale": 0
    }
  ]
}

Stability¶

Patch releases may add nullable or optional fields. Minor releases may add required fields or increment schema_version. Major releases may remove or rename fields.

bullpen skill validate¶