Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub hybridindie/comfyui_mcpHow 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".
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Breaks plans, specs, or PRDs into thin vertical-slice issues on the project issue tracker using tracer bullets. Useful for converting high-level work into grabbable implementation tickets.
Share bugs, ideas, or general feedback.
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 found