dce CLI

Use this skill when a user asks you to operate dce, inspect its API commands, or find the right generated command for an API task.

Workflow

1. Search for candidates with dce search "<intent>" --json; use --limit when needed. Search is only candidate discovery.
2. Inspect the exact command with dce commands show <path...> --json before executing an unfamiliar command.
3. If the command detail has auth.required=true, run dce auth status -o json before execution and read hostname and source. Host resolution order: --hostname > $DCE_HOST > the selected host (dce auth use <host>) > http.default_hostname > the single host in hosts.yml. If none applies, stop and ask the user to authenticate or select a host.
4. Execute only after flags, body, auth, HTTP path, mutation, dry_run, and output hints are clear from commands show. When mutation is not read, preview with --<dry_run.flag> if dry_run.mode is http_preview; if preview is unavailable, obtain explicit user confirmation before execution.

General Commands

• dce commands --json: full generated command catalog.
• dce commands --include-hidden --json: include hidden generated commands.
• dce commands show <path...> --json: source of truth for one command.
• dce commands schema --json: catalog schema version, surfaces, and dry-run result shape.
• dce search "<intent>" --json: ranked candidate commands.
• dce auth status -o json: resolved hostname, its source, the selected host, and every logged-in host.