comfyui-packaging-and-registry
Skill4 starsChanged 44 days agoMITView on GitHub
Use when creating or editing custom-node package metadata, pyproject configuration, Registry publication, comfy-cli publishing, Manager compatibility, release automation, node-pack scaffolding, or distribution documentation.
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-performanceSkill
- comfyui-self-maintenanceSkill
- comfyui-subgraphsSkill
- comfyui-testing-and-qaSkill
- comfyui-upstream-developmentSkill
- comfyui-workflowsSkill
- comfyui-workflow-validationSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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
- could be automatic: a setting could enforce it
- Distinctive: line 29
Read current official publishing requirements.
- Distinctive: line 34
Run current registry/CLI validation or dry-run tooling if available.
- Distinctive: line 35
Never publish, tag, or push a release unless the user explicitly requested that action.
- Distinctive: line 39
Do not write Registry tokens/API keys into committed files or logs.
- Distinctive: line 47
Before calling a package release-ready:
- Very specific: line 49
verify current Registry/Manager/package requirements from official sources.
- Distinctive: line 50
keep version and package metadata consistent.
- Very specific: line 51
run build/import/install smoke checks that fit the package.
- Distinctive: line 53
check that published node metadata still matches the runtime interface.
- Distinctive: line 54
document any publication step that was not actually executed.
≈ “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 Packaging and Registry
Packaging requirements evolve. Do not hardcode remembered metadata fields.
Sources
Use current:
- Registry/publishing docs in
Comfy-Org/docs; Comfy-Org/cookiecutter-comfy-extension;Comfy-Org/comfy-cli;Comfy-Org/registry-backendwhen backend behavior matters;Comfy-Org/ComfyUI-Managerfor Manager behavior;Comfy-Org/pyisolateonly when packaging/runtime isolation or conflicting extension dependencies are part of the actual target design.
Current CLI guidance
When publishing or building through comfy-cli, inspect the installed/version-matched CLI help and its current bundled skills rather than freezing command flags or build/deploy behavior here. Use CLI skills for the current operational procedure, then verify Registry/package contracts against official docs and the target package.
Procedure
- Inspect the existing project's package metadata and release process.
- Read current official publishing requirements.
- Compare with the current official scaffold.
- Make the smallest metadata/build changes required.
- Validate package build/install in a clean environment where practical.
- Confirm node import/registration after installation.
- Run current registry/CLI validation or dry-run tooling if available.
- Never publish, tag, or push a release unless the user explicitly requested that action.
Secrets
Do not write Registry tokens/API keys into committed files or logs. Follow the current official secret-management mechanism for the chosen publishing path.
Compatibility
Registry acceptance does not prove runtime compatibility. Keep package validation and runtime tests as separate gates.
Acceptance gate
Before calling a package release-ready:
- verify current Registry/Manager/package requirements from official sources;
- keep version and package metadata consistent;
- run build/import/install smoke checks that fit the package;
- confirm no credentials, developer-only paths, caches, or generated junk are in the release artifact;
- check that published node metadata still matches the runtime interface;
- document any publication step that was not actually executed.
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.

