Run ComfyUI workflows as agent-callable skills
Use ComfyUI Skills for OpenClaw when an agent needs to import, parameterize, route, and run repeatable ComfyUI workflows through a controlled CLI skill layer instead of manipulating raw node graphs.
npx skills add agentskillexchange/skills --skill run-comfyui-workflows-as-agent-callable-skills
ComfyUI Skills for OpenClaw turns exported ComfyUI API workflows into callable agent skills with schema-based parameter mapping, multi-server routing, dependency checks, and repeatable CLI execution. Use it when an operator wants OpenClaw, Codex, Claude Code, Hermes Agent, or another shell-capable agent to run approved image or media generation workflows without exposing the whole ComfyUI graph.
What this skill actually does
The agent imports an existing workflow JSON, defines the small set of parameters it is allowed to change, checks server status and missing dependencies, then runs jobs through the `comfyui-skill` CLI with structured arguments and history. The optional Web UI can help configure and test workflows, but the agent-facing boundary remains the same repeatable workflow layer.
This is not a generic ComfyUI listing, raw REST API wrapper, or broad MCP server entry. The scope is registering known ComfyUI workflows as reusable skills with constrained inputs and predictable execution across local or remote ComfyUI servers.
Inputs and prerequisites: ComfyUI server, Python 3.10+, comfyui-skill-cli, exported ComfyUI API workflow JSON.
Setup notes: Clone https://github.com/HuangYuChuh/ComfyUI_Skills_OpenClaw into the target agent skills directory, copy config.example.json to config.json, install the CLI with pipx install comfyui-skill-cli or pip install comfyui-skill-cli, then verify with comfyui-skill server status and comfyui-skill list.
Source and verification boundary: use https://huangyuchuh.github.io/ComfyUI_Skills_OpenClaw/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.