executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
comfyuiInstall and operate the MAGI-1 ComfyUI custom node and bundled workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a user wants to install, recognize, run, adapt, or troubleshoot the MAGI-1 ComfyUI custom node and its example workflows.
Do not use this sub-skill for source-code CLI inference commands or direct MagiPipeline API usage; route those questions to the MAGI-1 inference sub-skill. ComfyUI itself is an external host application dependency; this skill captures MAGI node behavior and workflow adaptation, not a verified ComfyUI host import.
comfy node registry-install MAGI-1.ComfyUI/custom_nodes/MAGI-1 and installing MAGI-1 runtime dependencies into the same Python environment used by ComfyUI.__init__.py: move or copy the repository's comfyui/__init__.py to the MAGI-1 plugin root if it is not already there. The plugin root must still contain the comfyui/, inference/, and example/assets/ subtrees expected by that initializer.load, t5_pretrained, and vae_pretrained. Use absolute paths for the ComfyUI node's config_path, T5 path, input media, and save path fields.comfy launch or python main.py from the ComfyUI directory.MagiProcess node sets single-node/single-GPU distributed environment variables internally before inference.