Agent skill · Workflow & Productivity

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.

breaking-brakegithub.com/breaking-brakeGitHub ↗
claude-coderead-onlyNOASSERTION
Install
npx skills add breaking-brake/cc-wf-studio --skill ccwf-cli --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Allowed tools: Bash(ccwf:*)Bash(npx@cc-wf-studio/cli:*)
Path: packages/cli/skills/ccwf-cli/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 5,342
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. Prerequisites
  2. Core workflow
  3. Subcommand reference
  4. ccwf render <file>
  5. Mapping user phrasing to subcommands
  6. Tips & gotchas
  7. Related interfaces
Commands it runs
ccwf --version
ccwf render ./.vscode/workflows/my-workflow.json             # Markdown (default)
ccwf render ./.vscode/workflows/my-workflow.json -f mermaid  #
More from cc-wf-studio
All skills →
About this skill
What does the ccwf-cli skill do?

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.

How do I install it?

Run `npx skills add breaking-brake/cc-wf-studio --skill ccwf-cli --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From breaking-brake/cc-wf-studio, a repository with 5,342 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going