Skip to content
cccskills
FreePublished on GitHub

cc-workflow-ai-editor

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). Use when the user wants to create a new workflow, modify an existing workflow, or edit the workflow canvas in CC Workflow Studio via the built-in MCP server.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

  1. Call get_workflow_schema via cc-workflow-studio MCP server
  2. Call get_current_workflow via cc-workflow-studio MCP server
  3. Ask the user what to create or modify
  4. 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.
  5. 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
  6. 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)

Example

{
  "nodes": [
    {
      "id": "group-1",
      "type": "group",
      "name": "",
      "position": { "x": 100, "y": 100 },
      "style": { "width": 400, "height": 300 },
      "data": { "label": "Data Processing" }
    },
    {
      "id": "node-1",
      "type": "subAgent",
      "name": "fetch-data",
      "parentId": "group-1",
      "position": { "x": 50, "y": 50 },
      "data": { "description": "Fetch data from API", "outputPorts": 1 }
    }
  ]
}

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。

The English summary is being prepared. Showing the original description.

breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

Run one unattended IDEATION iteration of the autonomous value-creation loop — invent improvements a user of cc-wf-studio would notice, judge them against the value bar, and file the winners as locked `idea` issues. Never implements anything; the next-task skill builds from the queue this skill fills. Use when the user says "アイデア出して", "next idea", or wants proposals without implementation.

The English summary is being prepared. Showing the original description.

breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

Run one unattended iteration of the QUALITY-ASSURANCE loop — steward any in-flight QA PR, then build ONE queued `qa` issue (test infrastructure, unit tests, regression tests for known bugs) on a branch off auto-qa and open a PR that squash-merges on green CI. Adds tests and tooling only; never edits product source. Use when the user says "QAタスク", "next qa", "テストを進めて", or wants autonomous progress on the quality track.

The English summary is being prepared. Showing the original description.

breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

Run one unattended IDEATION iteration of the quality-assurance loop — find the highest-value untested behavior in the codebase, judge it against the QA value bar, and file ONE locked `qa` issue specifying the test to write. Never writes code or tests; the next-qa skill builds from the queue this skill fills. Use when the user says "QAアイデア", "next qa idea", or wants the QA backlog refilled without implementation.

The English summary is being prepared. Showing the original description.

breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

Run one unattended IMPLEMENTATION iteration of the autonomous value-creation loop — steward any in-flight PR, fix interrupts (red CI / security / human bugs), or else build ONE queued `idea` issue on a branch off auto-dev and open a PR that squash-merges on green CI. Ideation lives in the next-idea skill; this skill consumes its queue. Use when the user says "次のタスク", "next task", "続きをやって", or wants autonomous progress without specifying what to do.

The English summary is being prepared. Showing the original description.

breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

See all skills by breaking-brake

Report a problem with this skill