使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/comfy-org/comfy-cli --skill comfy-custom-nodes-packaging开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Packaging fallback
Registry metadata lives in the pack's pyproject.toml. comfy node init refuses to overwrite an existing file, so edit in place. [project] carries name, description, version, license, dependencies and urls.Repository; [tool.comfy] carries PublisherId, DisplayName, Icon and includes.
The two compatibility ranges come from different places. [tool.comfy].requires-comfyui states the ComfyUI range; the frontend range is a comfyui-frontend-package entry in [project].dependencies, which is stripped from the published dependency list rather than installed. Declare operating systems and accelerators as [project].classifiers.
Run comfy node validate before comfy node publish --token <token>; it runs the publishing checks without uploading. An empty project.version fails, and a dynamic version needs [tool.comfy.version].path.
What the archive contains depends on git, and the two cases fail in opposite directions. In a git checkout it is git-tracked files, minus .comfyignore matches, plus every [tool.comfy].includes path — includes overrides .comfyignore, so an untracked asset that is not listed ships missing. Outside a git checkout, or with no usable git, the whole tree is archived minus .comfyignore matches, so an untracked secret or local weight ships. Read the archive's file list before publishing instead of reasoning from the tree.
