comfyui-workflow-validation
Skill4 starsChanged 44 days agoMITView on GitHub
Use when a ComfyUI workflow fails to load, validate, queue, execute, or produce expected outputs, or when checking node availability, links, inputs, models, workflow JSON, frontend/API representation, or compatibility before execution.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- comfyui-api-and-sdkSkill
- comfyui-core-runtimeSkill
- comfyui-custom-node-backendSkill
- comfyui-developmentSkill
- comfyui-frontend-extensionSkill
- comfyui-packaging-and-registrySkill
- comfyui-performanceSkill
- comfyui-self-maintenanceSkill
- comfyui-subgraphsSkill
- comfyui-testing-and-qaSkill
- comfyui-upstream-developmentSkill
- comfyui-workflowsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
If validation is happening because a comfy-cli job failed, inspect the current/version-matched CLI debugging guidance in addition to this …
- Distinctive: line 29
Prefer the running target's node definitions over a bundled/static catalog.
- Very specific: line 35
When comfy-cli, comfy-mcp, or the official test framework is installed, inspect its current help/docs and use the relevant validation …
- Distinctive: line 45
Check whether custom-node imports failed at startup.
- Distinctive: line 46
Check resource/model names against target choices.
- Distinctive: line 60
Before calling a workflow fixed or valid:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ComfyUI Workflow Validation
Validation layers
Validate in this order where applicable:
- JSON parse and representation detection;
- current/version-matched workflow schema;
- live node existence;
- input names and required values;
- output/link compatibility;
- enum/model/resource values exposed by the target;
- custom-node-specific constraints;
- official validator/test framework when available;
- representative execution only after preflight passes.
CLI failure guidance
If validation is happening because a comfy-cli job failed, inspect the current/version-matched CLI debugging guidance in addition to this structural validation skill. Use the CLI guidance for its error envelope and remediation flow; use the target schema/node catalog for workflow correctness.
Live catalog
Prefer the running target's node definitions over a bundled/static catalog. A static catalog cannot prove that the user's installed custom nodes match it.
If the comfyui-development skill is available, use its conservative workflow-preflight helper as a fallback. Activate that skill through the harness rather than assuming its files are reachable from this skill directory. The fallback is not a substitute for a stronger current official validator when one is available.
Official tooling
When comfy-cli, comfy-mcp, or the official test framework is installed, inspect its current help/docs and use the relevant validation command. Do not assume command syntax from an old version.
A command invocation succeeding is not the same as a valid workflow. Read the returned verdict/errors.
Debugging procedure
- Preserve the failing workflow before edits.
- Capture exact error text and server/browser logs.
- Determine frontend vs API representation.
- Compare failing node definitions with live target data.
- Check whether custom-node imports failed at startup.
- Check resource/model names against target choices.
- Reduce to a minimal failing graph if the cause remains unclear.
- Make one causal fix at a time.
- Revalidate.
Do not
- randomly rewire sockets until the error disappears;
- replace missing nodes with unrelated alternatives without explaining the semantic change;
- clear queues/history or delete user data as a diagnostic shortcut;
- upgrade the user's installation unless the task is specifically an upgrade.
Acceptance gate
Before calling a workflow fixed or valid:
- preserve the original failing workflow;
- capture the exact failure evidence;
- identify the workflow representation;
- resolve all deterministic validation errors found by the strongest available validator;
- re-run validation after the fix;
- report any live/runtime gate that could not be completed instead of treating it as a pass.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

