AI workflow editor for CC Workflow Studio. Create and edit visual AI agent workflows through interactive conversation using MCP tools (get_workflow_schema, get_current_workflow, apply_workflow, update_nodes).
NewMaintained
Automatic
◆AI Engineer pack
Last verified 8/11/2026
What it changes
3 of 23 test cases passed with the skill.
Pass-rate lift
—
Tokens
-23%
Agent turns
0%
Response time
-47%
Model gemini-3.6-flashMeasured 8/11/2026v13 of 23 cases passed with skill · 4 comparable
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 4 comparable cases; this report requires 8.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
Before making any modifications or prompting for user edits on a cc-workflow-studio session, what are the first two tool calls that must be executed?
What was checked, without and with the skill
Checked
Without skill
With skill
Calls get_workflow_schema before making modifications.
Missed
Passed
Calls get_current_workflow before making modifications.
Missed
Passed
case-14 · gemini-3.6-flash · 8/11/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md45 linessingle file
Call get_workflow_schema via cc-workflow-studio MCP server
Call get_current_workflow via cc-workflow-studio MCP server
Ask the user what to create or modify
Generate workflow JSON: use built-in sub-agents (builtInType: explore/plan/general-purpose) by default. Only call list_available_agents when the user explicitly asks to use an existing custom sub-agent.
Apply changes via cc-workflow-studio MCP server:
New workflow or structural changes (add/remove nodes/connections): use apply_workflow
Partial updates to existing nodes (change name, position, or data): use update_nodes (more token-efficient)
Fix errors if any
Ask for feedback, repeat from step 4
Group Node
Group nodes are visual containers for organizing related nodes on the canvas. They do NOT affect workflow execution.
Rules
Group nodes have type: "group" and require data.label (display name)
Group nodes must have style: { width, height } to define their visual area
Group nodes CANNOT have connections (no edges to/from group nodes)
To place a node inside a group, set the child node's parentId to the group's id
Child node position is relative to the group's top-left corner (not the canvas origin)
The name field on group nodes is not validated (can be empty or omitted)