ccwf-cli 100/100 — SaferSkills

Is ccwf-cli safe to install?

SaferSkills independently audited ccwf-cli (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.github/skills/cc-workflow-ai-editor/SKILL.md · 1 file

.github/skills/cc-workflow-ai-editor/SKILL.md2.2 KB · Markdown

name: cc-workflow-ai-editor

description: 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.

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)

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 }
    }
  ]
}

ccwf-cli— agent skill

Is ccwf-cli safe to install?

Group Node

Rules

Example

Audit the pieces. Scan the whole. Decide.