How this skill is triggered — by the user, by Claude, or both
Slash command
/comfy:genThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate an image using ComfyUI based on the user's prompt "$ARGUMENTS".
Generate an image using ComfyUI based on the user's prompt "$ARGUMENTS".
Parse the prompt. Extract any explicit parameters (dimensions, steps, cfg, model name) from the user's request. Reject and ask for clarification only in these specific cases:
Otherwise, apply these defaults for the listed parameters (and only these) when not specified:
Select a model. If the user specified a model name, use it. Otherwise, call comfyui_list_models with folder "checkpoints", pick one from the returned items, and ask the user to confirm before proceeding (offer to swap if they want a different one).
Generate the image. Call comfyui_generate_image with the parsed parameters and wait=True so we block until completion.
Fetch the result. The response is a dict envelope with keys status (expect "completed"), prompt_id, outputs, elapsed_seconds, and optionally warnings. outputs is a list of {node_id, filename, subfolder} entries — read the first entry's filename and subfolder and call comfyui_get_image with those. (Tip: pass preview_format="webp" and preview_quality=80 to comfyui_get_image for a thumbnail instead of the full PNG — much cheaper context.)
Present the result. Show the image and a summary of the generation parameters used (prompt, model, dimensions, steps, cfg).
comfyui_get_queue to see if ComfyUI is busy or stuck./comfy:workflow instead.npx claudepluginhub hybridindie/comfyui_mcpCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.