comfyui-skill-openclaw
Run registered ComfyUI workflows through the fast comfyui-skill CLI, and use the official local Comfy MCP for live template, node, model, validation, and orchestration capabilities. **Use this Skill when:** (1) The user requests to "generate an image", "draw a picture", or "execute a ComfyUI workflow". (2) The user has specific stylistic, character, or scene requirements for image generation. (3) The user asks you to import, register, sync, or configure saved ComfyUI workflows for later reuse.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
Its scripts were only partly scanned.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/huangyuchuh--comfyui-skills-openclaw)HTML
<a href="/listings/huangyuchuh--comfyui-skills-openclaw"><img src="/api/listings/huangyuchuh--comfyui-skills-openclaw/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
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.
<details> <summary><strong>For OpenClaw</strong></summary>
cd ~/.openclaw/workspace/skills git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill-openclaw cd comfyui-skill-openclaw
</details>
<details> <summary><strong>For Claude Code</strong></summary>
cd ~/.claude/skills git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill cd comfyui-skill
</details>
<details> <summary><strong>For Codex</strong></summary>
cd ~/.codex/skills git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill cd comfyui-skill
</details>
<details> <summary><strong>For Hermes Agent</strong></summary>
cd ~/.hermes/skills/creative git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill-openclaw cd comfyui-skill-openclaw
Or install via Hermes CLI (once the PR is merged):
hermes skills install comfyui-skill-openclaw
</details>
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](#web-ui) section below.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 213 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- ---
- name: comfyui-skill-openclaw
- description: |
- Run registered ComfyUI workflows through the fast comfyui-skill CLI, and use the official
- local Comfy MCP for live template, node, model, validation, and orchestration capabilities.
- **Use this Skill when:**
- (1) The user requests to "generate an image", "draw a picture", or "execute a ComfyUI workflow".
- (2) The user has specific stylistic, character, or scene requirements for image generation.
- (3) The user asks you to import, register, sync, or configure saved ComfyUI workflows for later reuse.
- license: Apache-2.0
- metadata:
- version: "1.1.0"
- platforms: [macos, linux, windows]
- prerequisites:
- commands: ["comfyui-skill"]
- env_vars: []
- requires:
- bins: ["comfyui-skill"]
- cliHelp: "comfyui-skill --help"
- hermes:
- tags: [image-generation, comfyui, ai-art, workflow, stable-diffusion, flux]
- related_skills: []
- ---
- # ComfyUI Agent SKILL
- > **Prerequisites**: Install the CLI: `pip install -U comfyui-skill-cli`. The official local Comfy MCP is optional and should be connected using the [official guide](https://docs.comfy.org/agent-tools/mcp#local-comfy-mcp-connection) when MCP capabilities are needed. All shell commands must run from this project's root directory (where this `SKILL.md` is located).
- >
- > [!IMPORTANT]
- > **Directory Sensitivity**: The CLI reads `config.json` and `data/` from the current directory.
- > You **MUST** `cd` into the project root before running any command.
- > **Symptom**: `list` returns `[]` or `server status` reports not found → you are in the wrong directory.
- ## Quick Decision
- - A matching registered workflow exists → use the **CLI Execution Flow (Step 1-4)**. This is the default for repeated, batch, and latency-sensitive work.
- - The request has no matching workflow, or requires live template/model/node discovery → use the **official local Comfy MCP**.
- - The user supplies a raw workflow that needs real environment validation → use MCP `validate_workflow`; use CLI `run --validate` for a registered workflow.
- - The user asks to install nodes, download models, restart, update, or switch versions → use MCP only after explaining the effect and getting confirmation.
- - User says "generate image / draw a picture" → first inspect registered workflows; if none fit, discover a current MCP template instead of guessing a model name.
- - User says "import workflow / add workflow" → `comfyui-skill --json workflow import <path>`
- - User says "img2img / use this image" → first `comfyui-skill --json upload <image>`, then execute
- - User says "inpainting / mask this area" → `comfyui-skill --json upload <mask> --mask`, then execute
- - User says "show previous results" → `comfyui-skill --json history list <id>`
- - User says "what failed / check job status" → `comfyui-skill --json jobs list --status failed`
- - User says "which server has more VRAM" → `comfyui-skill --json server stats --all`
- - User says "what nodes are available" → use MCP `nodes` for live ecosystem discovery; use `comfyui-skill --json nodes list` when only the CLI inventory is needed.
- - User says "dry run / test without executing" → `comfyui-skill --json run <id> --validate`
- - User says "open management UI" → `python3 ./ui/open_ui.py`
- ## Core Concepts
- - **Skill ID**: `<server_id>/<workflow_id>` (e.g., `local/txt2img`). If server is omitted, the default server is used.
- - **Schema**: Each workflow has a `schema.json` that maps business parameter names (e.g., `prompt`, `seed`) to internal ComfyUI node fields. Never expose node IDs to the user.
- - **Server**: One or more ComfyUI instances configured in `config.json`. Check health with `server status`.
- - **Two interfaces, one Skill**: CLI is the efficient execution path for known workflows. Official MCP is the adaptive path for discovering and orchestrating the current ComfyUI ecosystem. They share the same business intent and must not submit the same job twice.
- ## Official Local Comfy MCP
- When the Agent host exposes the official Comfy MCP tools, call those tools directly. Start every MCP flow with `server_info` and use the live tool schemas instead of assuming parameters or tool availability.
- When the host does not expose MCP tools but can run shell commands, use the included stdio bridge:
- ```bash
- python ./scripts/comfy_mcp.py probe
- python ./scripts/comfy_mcp.py tools
- python ./scripts/comfy_mcp.py call search_templates --arguments '{"query":"background removal"}'
- ```
- The bridge reads `mcp_command`, `mcp_args`, `mcp_python`, `mcp_cwd`, and `mcp_env` from the selected server in `config.json`. `probe` and `tools` are read-only. A `call` has the side effects of the named official tool.
- Read [references/comfy-mcp.md](./references/comfy-mcp.md) when the request needs MCP discovery, raw-workflow validation, template adaptation, job management, installation, lifecycle control, or partner models.
- Routing invariants:
- - Prefer CLI for a known `<server_id>/<workflow_id>`; MCP is not a mandatory extra hop.
- - Prefer MCP when the answer depends on the currently installed templates, nodes, models, hardware, or official tool contract.
- - For long MCP runs: `run_workflow(wait=false)` or `run_template(wait=false)` -> `job(action="wait"|"status")` -> `fetch_outputs`.
- - Once either path returns a `prompt_id`, continue polling that path. Never fall back by submitting again.
- - Never set `confirm_spend=true` without the user's explicit approval for that paid call.
- ## Command Reference
- | Command | Purpose |
- |---------|---------|
- | `comfyui-skill --json server status` | Check if ComfyUI server is online |
- | `comfyui-skill --json server stats` | Show VRAM, RAM, GPU, versions (`--all` for multi-server) |
- | `comfyui-skill --json list` | List all available workflows and parameters |
- | `comfyui-skill --json info <id>` | Show workflow details and parameter schema |
- | `comfyui-skill --json submit <id> --args '{...}'` | Submit a workflow (non-blocking) |
- | `comfyui-skill --json status <prompt_id>` | Check execution status |
- | `comfyui-skill --json run <id> --args '{...}'` | Execute a workflow (blocking, real-time streaming) |
- | `comfyui-skill --json run <id> --validate` | Validate workflow without executing |
- | `comfyui-skill --json upload <path>` | Upload image to ComfyUI (for img2img workflows) |
- | `comfyui-skill --json upload <path> --mask` | Upload mask image (for inpainting workflows) |
- | `comfyui-skill --json nodes list` | List all available ComfyUI nodes |
- | `comfyui-skill --json jobs list` | List server-side job history (`--status failed` to filter) |
- | `comfyui-skill --json deps check <id>` | Check missing dependencies |
- | `comfyui-skill --json deps install <id> --repos '[...]'` | Install missing custom nodes |
- | `comfyui-skill --json workflow import <path>` | Import workflow (auto-detect, warns about deprecated nodes) |
- | `comfyui-skill --json history list <id>` | List execution history for a workflow |
- ---
- ## Execution Flow
- ### Step 1: Query Available Workflows
- ```bash
- comfyui-skill --json list
- ```
- Returns a JSON array of all enabled workflows with their parameters.
- - `required: true` parameters → **ask the user** if not provided.
- - `required: false` parameters → infer from context (e.g., `seed` = random number), or omit.
- - Never expose node IDs; only use business parameter names (e.g., prompt, style).
- - If multiple workflows match, pick the most relevant one or list candidates.
- ### Step 2: Parameter Assembly
- Assemble parameters into a JSON string. Example:
- ```
- {"prompt": "A beautiful landscape, high quality, masterpiece", "seed": 40128491}
- ```
- If critical parameters are missing, ask the user (e.g., "What visual style would you like?").
- ### Step 3: Pre-flight Dependency Check
- **Always** run before first execution of a workflow:
- ```bash
- comfyui-skill --json deps check <server_id>/<workflow_id>
- ```
- - If `is_ready` is `true` → proceed to Step 4.
- - If `is_ready` is `false`:
- 1. Present missing nodes and models to the user.
- 2. If user agrees to install, run:
- ```bash
- comfyui-skill --json deps install <id> --repos '["https://github.com/repo1"]'
- ```
- Use `source_repo` URLs from the check report as `--repos` values.
- 3. If `needs_restart` is `true`, inform the user to restart ComfyUI, then re-check.
- 4. Missing models must be downloaded manually — tell the user which folder to place them in (e.g., `checkpoints`).
- ### Step 4: Execute the Workflow
- > **Note**: JSON args must be wrapped in single quotes to prevent bash from parsing double quotes.
- Choose the execution mode based on your environment:
- #### Interactive mode: `submit` + `status` (recommended for chat)
- **Step 4a — Submit:**
- ```bash
- comfyui-skill --json submit <id> --args '{"prompt": "..."}'
- ```
- Returns: `{"status": "submitted", "prompt_id": "..."}`. Tell the user generation has started.
- **Step 4b — Poll:**
- ```bash
- comfyui-skill --json status <prompt_id>
- ```
- Status values: `queued` (with `position`) → `running` → `success` (with `outputs`) or `error`.
- **Polling pattern — critical for real-time feedback:**
- Each `status` call must be a **separate tool invocation** (a separate bash command). Do NOT write a shell loop. The correct pattern is:
- 1. Run `status` as a standalone bash command.
- 2. Read the returned JSON.
- 3. If `queued` or `running`: **send a text message to the user** with progress, then run `status` again.
- 4. If `success`: proceed to Step 5.
- 5. If `error`: report the error.
- #### Non-interactive mode: one-shot blocking (for scripts/CI)
- ```bash
- comfyui-skill --json run <id> --args '{"prompt": "..."}'
- ```
- Blocks until finished. Returns the same result format as `status` with `success`.
- ### Step 5: Present Results
- On success, the result contains an `outputs` array with file references (`filename`, `subfolder`, `type`).
- Use your native capabilities to present the files to the user (e.g., image preview, file path).
- ---
- ## Workflow Import
- When the user wants to add new workflows (not execute existing ones):
- ```bash
- comfyui-skill --json workflow import <json_path>
- ```
- - Supports both API format and editor format (auto-detected, auto-converted).
- - Automatically generates `schema.json` with smart parameter extraction.
- - After import, check dependencies before first execution.
- For bulk import from ComfyUI server or local folders, see [`references/workflow-import.md`](./references/workflow-import.md).
- ## Troubleshooting
- 1. **ComfyUI Offline**: Run `comfyui-skill --json server status`. If offline, ask the user to start ComfyUI.
- 2. **Workflow Not Found**: Run `comfyui-skill --json list` to see available workflows. If missing, the user needs to import it first.
- 3. **Parameter Format Error**: Ensure `--args` is valid JSON wrapped in single quotes.
- 4. **Cloud Node Unauthorized**: Workflow uses cloud API nodes (Kling, Sora, etc.). Guide user to: (1) Generate an API Key at https://platform.comfy.org, (2) Open Web UI → Server Settings → fill in "ComfyUI API Key".
README.md · README · 459 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <div align="center">
- <img src="./asset/banner.png" alt="ComfyUI Skills Banner">
- <h1>ComfyUI Skills for OpenClaw</h1>
- <p><strong>Agent-friendly ComfyUI workflow skills for OpenClaw, Hermes Agent, Codex, Claude Code, and other agents.</strong></p>
- <p>
- 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.
- </p>
- <p>
- <a href="https://huangyuchuh.github.io/ComfyUI_Skills_OpenClaw/"><img src="https://img.shields.io/badge/docs-GitHub_Pages-4F46E5?style=flat&logo=gitbook&logoColor=white" alt="Docs"></a>
- <a href="https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw/blob/main/LICENSE"><img src="https://img.shields.io/github/license/HuangYuChuh/ComfyUI_Skills_OpenClaw?style=flat&color=10B981&logo=data%3Aimage/svg%2Bxml%3Bbase64%2CPHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCIgZmlsbD0ibm9uZSIgc3Ryb2tlPSJ3aGl0ZSIgc3Ryb2tlLXdpZHRoPSIyIiBzdHJva2UtbGluZWNhcD0icm91bmQiIHN0cm9rZS1saW5lam9pbj0icm91bmQiPjxwYXRoIGQ9Im0xNiAxNiAzLTggMyA4Yy0uODcuNjUtMS45MiAxLTMgMXMtMi4xMy0uMzUtMy0xWiIvPjxwYXRoIGQ9Im0yIDE2IDMtOCAzIDhjLS44Ny42NS0xLjkyIDEtMyAxcy0yLjEzLS4zNS0zLTFaIi8%2BPHBhdGggZD0iTTcgMjFoMTAiLz48cGF0aCBkPSJNMTIgM3YxOCIvPjxwYXRoIGQ9Ik0zIDdoMmMyIDAgNS0xIDctMiAyIDEgNSAyIDcgMmgyIi8%2BPC9zdmc%2B" alt="License"></a>
- <a href="https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw/stargazers"><img src="https://img.shields.io/github/stars/HuangYuChuh/ComfyUI_Skills_OpenClaw?style=flat&color=EAB308&logo=github" alt="GitHub stars"></a>
- <a href="https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw/network/members"><img src="https://img.shields.io/github/forks/HuangYuChuh/ComfyUI_Skills_OpenClaw?style=flat&color=F97316&logo=github" alt="GitHub forks"></a>
- <a href="https://www.python.org/"><img src="https://img.shields.io/static/v1?label=Python&message=3.10%2B&color=3B82F6&style=flat&logo=python&logoColor=white" alt="Python 3.10+"></a>
- <a href="https://github.com/NousResearch/hermes-agent"><img src="https://img.shields.io/static/v1?label=Hermes%20Agent&message=compatible&color=8B5CF6&style=flat&logo=data%3Aimage/svg%2Bxml%3Bbase64%2CPHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCIgZmlsbD0ibm9uZSIgc3Ryb2tlPSJ3aGl0ZSIgc3Ryb2tlLXdpZHRoPSIyIj48cGF0aCBkPSJNMTIgMmExMCAxMCAwIDEgMCAwIDIwIDEwIDEwIDAgMCAwIDAtMjBaIi8%2BPHBhdGggZD0iTTggMTRzMS41IDIgNCAyczQtMiA0LTIiLz48L3N2Zz4%3D&logoColor=white" alt="Hermes Agent Compatible"></a>
- <a href="https://agentskills.io"><img src="https://img.shields.io/static/v1?label=agentskills.io&message=standard&color=06B6D4&style=flat" alt="agentskills.io standard"></a>
- </p>
- <p>
- <a href="https://www.bilibili.com/video/BV1a6cUzVEE6/">🎬 Demo Video</a> ·
- <a href="https://huangyuchuh.github.io/ComfyUI_Skills_OpenClaw/">📘 Docs</a> ·
- <a href="#quick-start">🧭 Quick Start</a> ·
- <a href="#cli">⌨️ CLI</a> ·
- <a href="#web-ui">🖥️ Web UI</a> ·
- <a href="#multi-server-management">🛰️ Multi-Server</a>
- </p>
- <p>
- <strong>English</strong> ·
- <a href="./README.zh-CN.md">简体中文</a> ·
- <a href="./README.zh-TW.md">繁體中文</a> ·
- <a href="./README.ja.md">日本語</a> ·
- <a href="./README.ko.md">한국어</a> ·
- <a href="./README.es.md">Español</a>
- </p>
- </div>
- ---
- ## 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](https://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.
- | Best for | What you get |
- |----------|--------------|
- | OpenClaw, Codex, Claude Code, and Hermes Agent users | A ComfyUI workflow layer that agents can call safely |
- | Existing ComfyUI workflow owners | A clean way to reuse exported workflows without exposing the full graph |
- | Multi-machine setups | One namespace for local and remote ComfyUI servers |
- | Users who want visual setup and testing | An optional Web UI for configuring, previewing, and validating workflows before agents use them |
- ## Features
- | Capability | Why it matters |
- |------------|----------------|
- | **Agent-friendly CLI** | Designed for agents, not just humans. It provides a cleaner and more reliable interface than working directly with raw ComfyUI graphs or lower-level ComfyUI interaction patterns. |
- | **Schema-based parameter mapping** | Expose only the fields you want the agent to control, with clear aliases, types, and descriptions. |
- | **ComfyUI workflow import** | Import workflow JSON files, auto-detect formats, and generate the mapping layer needed for agent use. |
- | **Multi-server routing** | Manage local and remote ComfyUI servers under one namespace and route jobs to the right machine. |
- | **Dependency management** | Check missing nodes and models before execution and install supported dependencies through the CLI. |
- | **Official local Comfy MCP** | Use the official runtime interface for live template, node, and model discovery, raw-workflow validation, and advanced orchestration while keeping CLI execution fast. |
- | **Optional Web UI** | A visual layer for configuration and testing. It does not replace the CLI, and agent-facing actions still map to the same CLI workflow. |
- ## CLI And Official Local Comfy MCP
- This Skill treats CLI and MCP as two tools for different jobs, not as replacements for each other:
- - Use `comfyui-skill` for registered workflows, repeated execution, batch jobs, uploads, and history.
- - Use the official local Comfy MCP when the Agent needs to discover current templates, nodes, or models, validate a raw workflow, adapt a template, or manage the local ComfyUI lifecycle.
- If the Agent host already exposes the official MCP tools, the Skill calls them directly. A shell-only host can use the included bridge:
- ```bash
- python ./scripts/comfy_mcp.py probe
- python ./scripts/comfy_mcp.py call search_templates --arguments '{"query":"upscale"}'
- ```
- See [Official Local Comfy MCP Integration](https://huangyuchuh.github.io/ComfyUI_Skills_OpenClaw/comfy-mcp-application-layer/) for setup, routing, and safety boundaries.
- <a id="quick-start"></a>
- ## 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.
- <details>
- <summary><strong>For OpenClaw</strong></summary>
- ```bash
- cd ~/.openclaw/workspace/skills
- git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill-openclaw
- cd comfyui-skill-openclaw
- ```
- </details>
- <details>
- <summary><strong>For Claude Code</strong></summary>
- ```bash
- cd ~/.claude/skills
- git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill
- cd comfyui-skill
- ```
- </details>
- <details>
- <summary><strong>For Codex</strong></summary>
- ```bash
- cd ~/.codex/skills
- git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill
- cd comfyui-skill
- ```
- </details>
- <details>
- <summary><strong>For Hermes Agent</strong></summary>
- ```bash
- cd ~/.hermes/skills/creative
- git clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw.git comfyui-skill-openclaw
- cd comfyui-skill-openclaw
- ```
- Or install via Hermes CLI (once the PR is merged):
- ```bash
- hermes skills install comfyui-skill-openclaw
- ```
- </details>
- ### 2. Create your local config
- ```bash
- cp config.example.json config.json
- ```
- ### 3. Install the CLI
- ```bash
- pipx install comfyui-skill-cli
- ```
- Or:
- ```bash
- pip install comfyui-skill-cli
- ```
- If you already have the CLI installed, upgrade it with:
- ```bash
- # 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
- ```bash
- comfyui-skill server status
- comfyui-skill list
- ```
- ### 5. Import and run your first workflow
- ```bash
- 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:
- ```bash
- 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:
- ```bash
- 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](#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](#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`.
- <details>
- <summary><strong>Expand for manual config file setup</strong></summary>
- #### 1) Edit `config.json`
- ```jsonc
- {
- "servers": [
- {
- "id": "local",
- "name": "Local",
- "url": "http://127.0.0.1:8188",
- "enabled": true,
- "output_dir": "./outputs"
- }
- ],
- "default_server": "local"
- }
- ```
- #### 2) Place workflow files
- ```text
- data/local/my-workflow/
- workflow.json # ComfyUI API-format export
- schema.json # Parameter mapping
- ```
- #### 3) Write `schema.json`
- ```jsonc
- {
- "description": "My workflow",
- "enabled": true,
- "parameters": {
- "prompt": {
- "node_id": 10,
- "field": "prompt",
- "required": true,
- "type": "string",
- "description": "Prompt text"
- }
- }
- }
- ```
- </details>
- <a id="cli"></a>
- ## Common Commands
- Beyond the commands shown in [Quick Start](#quick-start), here are additional operations you may need:
- ### Inspect a workflow
- ```bash
- comfyui-skill info local/txt2img
- ```
- ### Submit a workflow asynchronously
- ```bash
- comfyui-skill submit local/txt2img --args '{"prompt": "a white cat"}'
- comfyui-skill status <prompt_id>
- ```
- ### Manage servers
- ```bash
- 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](https://github.com/HuangYuChuh/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.
- <a id="multi-server-management"></a>
- ## 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:
- ```bash
- 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:
- ```text
- <server_id>/<workflow_id>
- ```
- For example:
- ```text
- 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:
- ```bash
- comfyui-skill config export --output ./backup.json
- comfyui-skill config import ./backup.json --dry-run
- comfyui-skill config import ./backup.json
- ```
- <a id="web-ui"></a>
- ## 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
- ```bash
- ./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](https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw-frontend).
- ## 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:
- ```bash
- comfyui-skill deps check <workflow_id>
- ```
- Then install supported dependencies if needed.
- ## Changelog
- Recent highlights:
- - **v0.4.0**: Migrated to [CLI-first architecture](https://github.com/HuangYuChuh/ComfyUI_Skill_CLI) — 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](./CHANGELOG.md) for the full release history.
- ## Contributing
- Contributions are welcome! Please read [CONTRIBUTING.md](./CONTRIBUTING.md) before submitting a PR.
- ## Resources
- - [English README](./README.md)
- - [简体中文 README](./README.zh-CN.md)
- - [繁體中文 README](./README.zh-TW.md)
- - [日本語 README](./README.ja.md)
- - [한국어 README](./README.ko.md)
- - [Español README](./README.es.md)
- - [ComfyUI Skill CLI](https://github.com/HuangYuChuh/ComfyUI_Skill_CLI)
- - [Frontend Repository](https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw-frontend)
- - [Hermes Agent](https://github.com/NousResearch/hermes-agent) — compatible AI agent platform
- - [agentskills.io](https://agentskills.io) — open skill format standard
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.