/**
 * skill Command - manage official Agent Skills from the CLI
 * Issue #1237: a thin client over the Skill APIs (#1231/#1233/#1235/#1236)
 *
 *   commandmate skill list [--json]
 *   commandmate skill info <skill-id> [--version <v>] [--json]
 *   commandmate skill plan <skill-id> --worktree <id> [--version <v>] [--json]
 *   commandmate skill update-plan <skill-id> --worktree <id> [--version <v>] [--range <r>] [--json]
 *   commandmate skill update <skill-id> --worktree <id> [--version <v>] [--dry-run] [--yes] [--ack-risk <id>@<version>] [--ack-risk-increase]
 *   commandmate skill install <skill-id> --worktree <id> --version <exact> [--dry-run] [--yes] [--ack-risk <id>@<version>] [--git current|dedicated] [--push] [--pr]
 *   commandmate skill uninstall <skill-id> --worktree <id> [--dry-run] [--yes] [--json]
 *   commandmate skill status <skill-id> --worktree <id> [--json]
 *   commandmate skill reindex [--json]
 *
 * The CLI never downloads, extracts, writes or deletes anything: it asks the
 * server for a plan, shows it, and presents the token the server issued back to
 * the server unchanged. It reconstructs no file list, no checksum and no path —
 * those inputs are rejected by the API by design (#1233), and reproducing them
 * here would create exactly the UI/CLI security drift the design forbids.
 *
 * `--json` prints the API response body verbatim, so the JSON contract is the
 * API's. Every diagnostic, prompt and error goes to stderr, so a failed `--json`
 * run leaves stdout empty rather than half-written.
 */
import { Command } from 'commander';
export declare function createSkillCommand(): Command;
//# sourceMappingURL=skill.d.ts.map