Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →breaking-brake/ccwf-cli
Use the `ccwf` CLI (from @cc-wf-studio/cli) to render, validate, preview, export, or run cc-wf-studio workflow JSON files from the terminal. Apply whenever the user mentions viewing, visualizing, checking, executing, or converting a workflow under `.vscode/workflows/` (or any `*workflow*.json`), wants a Mermaid diagram of a workflow, asks to "see" / "preview" / "open" a workflow, or wants to run a workflow as a Claude Code Skill without opening VSCode.
Passed 19 of 22 test cases with the skill, and 4 of 22 without it.
and 17 more in the full report
18 fixed4 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to re-export .vscode/workflows/sync.json into Claude Code skill files, replacing any pre-existing generated files.
| Checked | Without skill | With skill |
|---|---|---|
| Includes the --overwrite flag when running ccwf export | Missed | Passed |
The instructions your model reads when the skill loads.
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.
Confirm ccwf is available before running any other subcommand:
ccwf --version
If ccwf is not on PATH:
npm install -g @cc-wf-studio/clinpx @cc-wf-studio/cli (e.g. npx @cc-wf-studio/cli render <file>)pnpm add -D @cc-wf-studio/cli and run via pnpm exec ccwfIf the user has a VSCode workspace and you can't find a workflow file, search .vscode/workflows/*.json first; that's the canonical location.
The natural flow when the user has a workflow file in hand:
ccwf validate <file> — schema-check it. Exit 0 = clean, exit 1 = errors. Run this first whenever you receive a workflow from elsewhere.ccwf preview <file> — opens a read-only viewer (Mermaid + per-node Markdown) in the browser. Use this when the user says "show me" / "what's in this workflow?" / "見せて".ccwf export <file> or ccwf run <file> — materialises the workflow as Claude Code (or another agent's) Skill files. Use run when the user wants the next step to be actually executing the workflow with claude.If a step fails, stop and surface the exact error to the user before moving on.
ccwf render <file>Print a Markdown bundle (Mermaid flowchart + per-node execution instructions) to stdout. Use when piping to another tool or pasting into a PR / chat message.
ccwf render ./.vscode/workflows/my-workflow.json # Markdown (default)
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.