How this skill is triggered — by the user, by Claude, or both
Slash command
/comfy:progressThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Show progress for a specific ComfyUI job. Prompt ID: "$ARGUMENTS".
Show progress for a specific ComfyUI job. Prompt ID: "$ARGUMENTS".
Get the prompt_id. Extract it from "$ARGUMENTS". If "$ARGUMENTS" is empty or contains no recognizable id, suggest the user run /comfy:status first to find active job IDs, or /comfy:history for recent completions, and stop here.
Fetch progress. Call comfyui_get_progress with the prompt_id. Do not pre-validate the id format — the tool returns status="unknown" if the job is not found, which step 3 surfaces to the user.
Format the response. The response is a dict. Format it to include the following fields:
current_node field)step X of total_steps Y (percentage)queued, running, completed, error, interrupted (mapped from the unified /api/jobs/{id} endpoint), or unknown if the job is not foundnpx claudepluginhub hybridindie/comfyui_mcpBuilds a throwaway prototype to answer a design question about UI appearance or state/logic behavior. Guides you through two branches: interactive terminal app for logic validation, or multiple UI variations for visual exploration.