installer-packs

Featured

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 — importantly — to invite the user to contribute new packs back upstream.

AI & Automation 450 stars 76 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Installer Packs `comfyui-mcp` ships **installer packs** under [`packs/`](../../packs) — one-command setups for a model family: custom nodes + model weights + a ready workflow. Each pack is driven by a single `manifest.yaml` (a `ComfyManifest`, the same shape the `apply_manifest` tool consumes), so one source of truth drives both an MCP-native install and 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` (requires `COMFYUI_PATH`). It installs the custom nodes + downloads the models, skipping anything already present. - **One-click for non-MCP users:** run `packs/<name>/install-windows.bat` (or `install-runpod.sh`) from a ComfyUI root. Then load the pack's `workflow.json`. - After install, check the pack's `pack.yaml` `notes`/`post_install` for 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: 1. **An upstream installer** (`*-MODELS-NODES_INSTALL.bat` / `.sh`) — parse its download lines (`curl`/`wget`/`:grab`...

Details

Author: artokun
Repository: artokun/comfyui-mcp
Created: 5 months ago
Last Updated: today
Language: TypeScript
License: MIT

Integrates with

Model Context Protocol · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

propose-catalogue-pack

Use to justify and scaffold a NEW pack area for this catalogue — test that it is additive and fits the catalogue's declared coverage model plus the four charter principles, then scaffold the pack shell and emit an RFC with a per-primitive inventory, or reject it as non-additive. Triggers on "should we add a pack for <area>", "propose a new pack", "justify a <vendor/domain> pack". Do NOT use to ingest units (use assimilate-primitive or assimilate-repo).

14 Updated today

eugenelim

Data & Documents Listed

scaffold-pack-author

Author an in-tree scaffold-toolkit template pack for the repo you are in — any language, any architecture. Asks whether the repo intends to migrate toward a different target architecture (author a second, additive pack if so) and splits out external/infra packages (cloud SDKs, message brokers, secret managers) into their own packs. Study the repo's recurring pattern, turn one real instance into a versioned pack (Handlebars templates + descriptor + AI_IMPLEMENTATION markers + registry injections + test_data + a real build-check), wire the markers into the existing brownfield files, and point `.scaffold/config.json` at it so the pack lives in the repo's own git tree and the team maintains its coding standards there. Use when the user says "author/create a scaffold pack", "make a pack for this repo", "cut a new pack version", or "wire scaffold into this codebase". This is the producer side; the `scaffold` skill is the consumer side that runs `generate`.

1 Updated yesterday

MohanTn

AI & Automation Listed

agentpack

Route normal development through AgentPack's work, learn, finish, and doctor loop.

21 Updated 3 days ago

vishal2612200