agentleFS
badgidsbadgids/comfyui-development-skills/skills/comfyui-packaging-and-registry/SKILL.md

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.

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
  1. Distinctive:

    Read current official publishing requirements.

    line 29
  2. Distinctive:

    Run current registry/CLI validation or dry-run tooling if available.

    line 34
  3. Distinctive:

    Never publish, tag, or push a release unless the user explicitly requested that action.

    line 35
  4. Distinctive:

    Do not write Registry tokens/API keys into committed files or logs.

    line 39
  5. Distinctive:

    Before calling a package release-ready:

    line 47
  6. Very specific:

    verify current Registry/Manager/package requirements from official sources.

    line 49
  7. Distinctive:

    keep version and package metadata consistent.

    line 50
  8. Very specific:

    run build/import/install smoke checks that fit the package.

    line 51
  9. Distinctive:

    check that published node metadata still matches the runtime interface.

    line 53
  10. Distinctive:

    document any publication step that was not actually executed.

    line 54

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-backend when backend behavior matters;
  • Comfy-Org/ComfyUI-Manager for Manager behavior;
  • Comfy-Org/pyisolate only 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

  1. Inspect the existing project's package metadata and release process.
  2. Read current official publishing requirements.
  3. Compare with the current official scaffold.
  4. Make the smallest metadata/build changes required.
  5. Validate package build/install in a clean environment where practical.
  6. Confirm node import/registration after installation.
  7. Run current registry/CLI validation or dry-run tooling if available.
  8. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.