ccwf-clilisted

# ccwf CLI `ccwf` is the command-line entry into cc-wf-studio — a visual AI-agent workflow tool. It treats `.vscode/workflows/*.json` workflow files as inputs and lets you render them as Markdown, validate the schema, open them in a browser-based viewer, convert them into Agent Skills, or execute them. The same workflow JSON also drives the VSCode extension and an MCP server, so you can pick whichever interface fits the situation. This Skill teaches Claude how to recognise when `ccwf` is the right answer and which subcommand to reach for. The subcommands and flags listed here are the source of truth — if behaviour seems off, check `ccwf <subcommand> --help` first. ## Prerequisites Confirm `ccwf` is available before running any other subcommand: ```bash ccwf --version ``` If `ccwf` is not on PATH: - **Preferred**: install globally — `npm install -g @cc-wf-studio/cli` - **Without install**: prefix every command with `npx @cc-wf-studio/cli` (e.g. `npx @cc-wf-studio/cli render <file>`) - **In a project**: `pnpm add -D @cc-wf-studio/cli` and run via `pnpm exec ccwf` If the user has a VSCode workspace and you can't find a workflow file, search `.vscode/workflows/*.json` first; that's the canonical location. ## Core workflow The natural flow when the user has a workflow file in hand: 1. **`ccwf validate <file>`** — schema-check it. Exit 0 = clean, exit 1 = errors. Run this first whenever you receive a workflow from elsewhere. 2. **`ccwf preview <file>`** — opens a read-on