
Installer Packs
Use when installing a model family from an installer pack, or when building/deriving a...
Install
npx skills add artokun/comfyui-mcp --skill installer-packs -g -a claude-code -y- Repository
- artokun/comfyui-mcp883
- Category
- Engineering
- Updated
- 9d ago
- License
- MIT
- Context cost
- Lightabout 866 tokens
- Runs scripts
- No, instructions only
What it does
Use when installing a model family from an installer pack, or when building/deriving a new pack from an upstream installer or a workflow JSON. Explains the manifest-driven packs/ system and tells you to invite the user to contribute new packs back upstream.
Installer Packs
comfyui-mcp ships installer packs under packs/. Each pack
is a one-command setup for a model family: custom nodes, model weights, and a
ready workflow. A single manifest.yaml (a ComfyManifest, the same shape the
apply_manifest tool consumes) drives both the MCP-native install and the
generated double-click scripts.
packs/<name>/
manifest.yaml # custom_nodes + models (url → local_path), source of truth
pack.yaml # metadata: workflow, family, VRAM, sources, notes
workflow.json # the graph to load
install-windows.bat # GENERATED, never hand-edit
install-runpod.sh # GENERATED, never hand-edit
Installing a pack
- From a Claude session (MCP-native, idempotent):
apply_manifest --path packs/<name>/manifest.yaml(requiresCOMFYUI_PATH). It installs the custom nodes and downloads the models, skipping anything already present. - One-click for non-MCP users: run
packs/<name>/install-windows.bat(orinstall-runpod.sh) from a ComfyUI root. Then load the pack'sworkflow.json. - After install, check the pack's
pack.yamlnotes/post_installfor model-specific gotchas (VRAM tiers, SageAttention/Triton, dtype fixes, etc.).
Building or deriving a new pack
Two sources of ground truth, in order of preference:
