comfyui-api-and-sdk
Skill4 starsChanged 44 days agoMITView on GitHub
Use for ComfyUI HTTP APIs, WebSockets, job submission, object/node discovery, uploads/downloads, Python/TypeScript/Swift SDKs, comfy-cli, comfy-api-proxy, comfy-mcp, Cloud versus self-hosted integration, and external applications that drive ComfyUI.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 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
- comfyui-workflow-validationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 20
Do not merge route/payload assumptions across these surfaces.
- Very specific: line 24
Use the matching official SDK/tool repository, Comfy-Org/docs, and the target/current core server source.
- Distinctive: line 29
Prefer the official SDK for that language when it supports the required operation.
- Distinctive: line 31
If direct HTTP/WebSocket access is required, inspect current official server routes/messages for the target.
- Distinctive: line 33
Treat node discovery as target-specific data.
- Distinctive: line 34
Avoid embedding secrets in workflow JSON, logs, or source.
- Distinctive: line 35
Add a small integration test against a controlled target when practical.
- Distinctive: line 39
If supporting both Cloud and self-hosted, keep differences explicit behind an adapter rather than pretending the endpoints are identical.
- Distinctive: line 43
Treat MCP as an integration layer, not as specification authority for ComfyUI internals.
- Distinctive: line 47
Before calling an integration complete:
- Distinctive: line 50
verify current routes or SDK signatures from the matching official source.
- Distinctive: line 51
test timeout and error handling, not only the successful response.
- Distinctive: line 52
keep credentials out of source, workflow files, and logs.
- Distinctive: line 53
run a controlled integration test when practical.
≈ “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 API and SDK
First classify the target
Identify whether the client talks to:
- self-hosted ComfyUI server;
- Comfy Cloud;
comfy-api-proxy;- an SDK abstraction;
- MCP;
- CLI.
Do not merge route/payload assumptions across these surfaces.
Sources
Use the matching official SDK/tool repository, Comfy-Org/docs, and the target/current core server source.
Procedure
- Determine target service and version.
- Prefer the official SDK for that language when it supports the required operation.
- Inspect current SDK signatures and examples instead of recalling them.
- If direct HTTP/WebSocket access is required, inspect current official server routes/messages for the target.
- Implement timeouts, connection failures, execution errors, and output retrieval explicitly.
- Treat node discovery as target-specific data.
- Avoid embedding secrets in workflow JSON, logs, or source.
- Add a small integration test against a controlled target when practical.
Compatibility
If supporting both Cloud and self-hosted, keep differences explicit behind an adapter rather than pretending the endpoints are identical.
MCP
Treat MCP as an integration layer, not as specification authority for ComfyUI internals. Verify underlying behavior against the target/core when needed.
Acceptance gate
Before calling an integration complete:
- identify the exact service surface: self-hosted, Cloud, proxy, SDK, MCP, or CLI;
- verify current routes or SDK signatures from the matching official source;
- test timeout and error handling, not only the successful response;
- keep credentials out of source, workflow files, and logs;
- run a controlled integration test when practical;
- report untested network/service paths explicitly.
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.

