ComfyUI Skills for OpenClaw

Agent-friendly ComfyUI workflow skills for OpenClaw, Hermes Agent, Codex, Claude Code, and other agents.

Use this project to turn ComfyUI workflows into callable skills with an agent-friendly CLI as the primary interface, plus a visual Web UI for easier configuration and testing.

🎬 Demo Video · 📘 Docs · 🧭 Quick Start · ⌨️ CLI · 🖥️ Web UI · 🛰️ Multi-Server

English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Español

Overview

ComfyUI Skills for OpenClaw is an agent-friendly bridge that turns ComfyUI workflows into callable skills for AI agents.

Instead of asking an agent to manipulate raw ComfyUI graphs, this project gives each workflow a clean, controlled interface through a CLI and schema-based parameter mapping. It works with OpenClaw, Hermes Agent, Codex, Claude Code, and any agent that can run shell commands. Compatible with the agentskills.io open standard.

Use it when you want to import existing ComfyUI workflows, expose only the parameters that matter, run them from chat or agent tasks, and manage everything through one consistent workflow layer.

Features

Quick Start

Get ComfyUI Skills running in a few minutes.

Before you start, make sure you have:

• Python 3.10+
• A running ComfyUI server
• An exported workflow in ComfyUI API format if you want to test execution right away

1. Clone the project

Choose the directory that matches your agent environment.

cd ~/.openclaw/workspace/skills
git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill-openclaw
cd comfyui-skill-openclaw

cd ~/.claude/skills
git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill
cd comfyui-skill

cd ~/.codex/skills
git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill
cd comfyui-skill

cd ~/.hermes/skills/creative
git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill-openclaw
cd comfyui-skill-openclaw

hermes skills install comfyui-skill-openclaw

2. Create your local config

cp config.example.json config.json

3. Install the CLI

pipx install comfyui-skill-cli

Or:

pip install comfyui-skill-cli

If you already have the CLI installed, upgrade it with:

# If you installed it with pipx
pipx upgrade comfyui-skill-cli

# If you installed it with pip
python3 -m pip install -U comfyui-skill-cli

4. Verify the setup

comfyui-skill server status
comfyui-skill list

5. Import and run your first workflow

comfyui-skill workflow import /absolute/path/to/my-workflow.json
comfyui-skill deps check local/my-workflow
comfyui-skill run local/my-workflow --args '{"prompt": "a white cat"}'

For manual CLI imports, the recommended approach is to pass the workflow JSON as an absolute path. That avoids path ambiguity and keeps the storage model simple.

For example:

comfyui-skill workflow import /Users/yourname/Downloads/my-workflow.json

After import, the CLI stores the normalized workflow and schema under data/<server_id>/<workflow_id>/, for example data/local/my-workflow/workflow.json and data/local/my-workflow/schema.json.

This is also the formal layout used by the Web UI and by Agent/OpenClaw-driven imports:

data/<server_id>/<workflow_id>/
  workflow.json
  schema.json
  history/

At this point, the CLI will read your local config.json, discover available workflows, and execute them through your ComfyUI server.

If you prefer a visual setup and testing flow, see the Web UI section below.

Setup Options

Choose the path that matches how you want to use the project.

OpenClaw

Use this path if you want OpenClaw to discover and execute ComfyUI workflows as skills.

• Clone the repository into ~/.openclaw/workspace/skills
• Install comfyui-skill-cli
• Configure config.json
• Import workflows and expose agent-safe parameters

Codex or Claude Code

Use this path if you want coding agents to call ComfyUI workflows through shell commands.

• Clone the repository into your agent skills directory
• Install the CLI
• Verify with comfyui-skill list
• Execute workflows with structured --args

Web UI

Use this path if you want a visual interface for configuration, inspection, and testing. See the Web UI section below for launch instructions and details.

Manual Setup

Use this path if you want direct control over config.json, workflow.json, and schema.json.

{
  "servers": [
    {
      "id": "local",
      "name": "Local",
      "url": "http://127.0.0.1:8188",
      "enabled": true,
      "output_dir": "./outputs"
    }
  ],
  "default_server": "local"
}

data/local/my-workflow/
  workflow.json  # ComfyUI API-format export
  schema.json    # Parameter mapping

{
  "description": "My workflow",
  "enabled": true,
  "parameters": {
    "prompt": {
      "node_id": 10,
      "field": "prompt",
      "required": true,
      "type": "string",
      "description": "Prompt text"
    }
  }
}

Common Commands

Beyond the commands shown in Quick Start, here are additional operations you may need:

Inspect a workflow

comfyui-skill info local/txt2img

Submit a workflow asynchronously

comfyui-skill submit local/txt2img --args '{"prompt": "a white cat"}'
comfyui-skill status <prompt_id>

Manage servers

comfyui-skill server list
comfyui-skill server add --id remote --url http://10.0.0.1:8188

For the full CLI reference, run comfyui-skill --help or see ComfyUI Skill CLI.

Workflow Requirements

To work reliably with this project, each workflow should meet these requirements.

• The workflow must be exported from ComfyUI in API format.
• The workflow should include an output node such as Save Image.
• The workflow needs a schema.json mapping so the agent can work with a clean parameter interface.
• The target ComfyUI server must have the required custom nodes and models installed.

If you use comfyui-skill workflow import, the CLI can help generate the required mapping and check dependencies before execution.

Multi-Server Management

This project is designed to work with more than one ComfyUI server.

You can keep multiple local or remote ComfyUI instances under one configuration and route workflows by namespace. This is useful when different machines serve different purposes, such as lightweight local testing, larger GPU jobs, or model-specific environments.

Examples:

comfyui-skill server add --id local --url http://127.0.0.1:8188
comfyui-skill server add --id remote-a100 --url http://10.0.0.20:8188
comfyui-skill server list

Workflows are addressed with the format:

<server_id>/<workflow_id>

For example:

local/txt2img
remote-a100/sdxl-base

Both servers and workflows support enable and disable switches, so agents only see workflows that are currently available.

You can also move settings between machines with:

comfyui-skill config export --output ./backup.json
comfyui-skill config import ./backup.json --dry-run
comfyui-skill config import ./backup.json

Web UI

A local web interface is available for visual configuration and testing. It is optional, and it exists to make setup, inspection, and validation easier. The skill itself is still designed for agents to use through the CLI.

Launch

./ui/run_ui.sh                    # macOS/Linux
# or: ui\run_ui.bat               # Windows

The launch scripts create a project .venv when needed and install UI dependencies into that virtual environment. No global Web UI dependency install is required.

Visit http://localhost:18189.

What you can do in the Web UI

• Upload workflows exported from ComfyUI
• Configure parameter mappings with a visual editor
• Manage multiple servers and workflows in one place
• Search, reorder, and inspect workflow definitions
• Test and validate workflow configuration before handing it off to agents
• Use the interface in English, Simplified Chinese, or Traditional Chinese

Everything the Web UI configures maps back to the same underlying CLI-driven workflow. It is a visual companion for setup and testing, not a separate execution model.

Frontend source lives in a separate repository.

Common Issues

HTTP 400 on /prompt

The workflow payload or one of the injected parameter values is invalid.

Check:

• Whether the workflow was exported in API format
• Whether the schema mapping points to the correct node and field
• Whether the provided argument types match the schema

No images returned

The workflow may be missing a valid output node such as Save Image.

Connection failed

Check that:

• The ComfyUI server is running
• The server URL in config.json is correct
• The selected server is enabled

Missing nodes or models

Run:

comfyui-skill deps check <workflow_id>

Then install supported dependencies if needed.

Changelog

Recent highlights:

• v0.4.0: Migrated to CLI-first architecture — all workflow operations (run, submit, status, import, deps) now go through a standalone CLI tool; legacy Python scripts have been removed.
• v0.3.1: Added ComfyUI API Key support for cloud API nodes such as Kling, Sora, and Nano Banana.
• v0.3.0: Added dependency check and install, non-blocking submit and status, image upload, import preview, and execution history.

See CHANGELOG.md for the full release history.

Contributing

Contributions are welcome! Please read CONTRIBUTING.md before submitting a PR.

Resources

• English README
• 简体中文 README
• 繁體中文 README
• 日本語 README
• 한국어 README
• Español README
• ComfyUI Skill CLI
• Frontend Repository
• Hermes Agent — compatible AI agent platform
• agentskills.io — open skill format standard