Back to Skills

comfyui-workflow-builder

Generate, build, create, or design ComfyUI workflow JSON from natural language descriptions. Produces valid node graphs with correct class_types, connections, output indices, and model-appropriate settings. Handles txt2img, img2img, inpainting, ControlNet, LoRA stacking, upscaling, and face detailing pipelines. Does NOT cover ComfyUI installation, custom node development, Python scripting, model training, hardware advice, or architectural explanations.

86stars24forksUpdated 8/14/2026

Security Assessment

Safe(95/100)
Security Score95/100

About comfyui-workflow-builder

This skill translates natural-language image and video generation requests into valid, executable ComfyUI workflow JSON. It addresses a common failure mode when models try to hand-author ComfyUI graphs: hallucinated node names, wrong output indices, dangling connections, and model settings that do not match the chosen checkpoint. By encoding the correct node-graph format, connection conventions, and model-specific rules, it produces graphs that ComfyUI can actually run.

The documented workflow is a six-step process: parse the request into output type, source material, identity method, and quality level; check a cached inventory of available checkpoints, identity models, ControlNet models, custom nodes, and VRAM; select a pipeline pattern from a table covering text-to-image, identity-preserved image, LoRA character, image-to-video (Wan and AnimateDiff), talking head, upscale, and inpainting; generate the JSON; validate every class_type and model filename against the inventory plus connection and resolution checks; and output by either queuing through the companion comfyui-api skill (online) or saving to disk (offline). It ships concrete templates (for example a full FLUX text-to-image graph), a VRAM estimation table by component, and a list of common mistakes to avoid such as wrong output indices and CFG values that are too high for InstantID.

It targets generative-media practitioners, ComfyUI power users, and agent builders who want to go from a prompt to a runnable pipeline. It explicitly excludes ComfyUI installation, custom node development, Python scripting, model training, and hardware advice, keeping its scope to workflow construction. An eval harness (test cases, benchmark, trigger tests) accompanies the skill.

FAQ

What kinds of pipelines can it build?

Text-to-image, image-to-image, inpainting, ControlNet, LoRA stacking, upscaling, face detailing, identity-preserved image (InstantID/PuLID/IP-Adapter), and image-to-video via Wan or AnimateDiff, among others.

How does it avoid inventing nonexistent nodes or models?

Before presenting a workflow it validates that every class_type exists in the inventory's node list and every model filename exists in the inventory's model list, and checks for dangling inputs and model-appropriate resolution.

Does it run the workflow?

Not directly. In online mode it hands the generated JSON to the comfyui-api skill to queue; in offline mode it saves the JSON to the project's workflows directory.

What is explicitly out of scope?

ComfyUI installation, custom node development, Python scripting, model training, hardware advice, and architectural explanations.

How does it size settings to the hardware?

It reads available VRAM from the inventory and uses a per-component VRAM estimation table (for example FLUX FP16 ~16GB, SDXL ~6GB) so estimates do not exceed the available budget.

All Files

8 files
eval/run-eval.sh16.6 KB
View
SKILL.md5.9 KB
View
eval/results/.gitignore0.1 KB
View
eval/results/.gitkeep0.0 KB
View
eval/benchmark.yaml1.4 KB
View
eval/test-cases.yaml7.0 KB
View
eval/EVAL.md2.3 KB
View
eval/trigger-tests.yaml1.7 KB
View

Install comfyui-workflow-builder

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill