Agent-Skills.md

Agent Skills: Debug Comfy Workflow

Diagnose a VibeComfy or ComfyUI workflow that fails validation, conversion, node/model resolution, runtime execution, or output production. Use when the user asks why a workflow does not run, has missing nodes/models, validation errors, bad wiring, failed RunPod/local runs, or confusing agent-edit failures.

UncategorizedID: peteromallet/vibecomfy/debug-comfy-workflow

Repository

peteromallet/vibecomfy
peteromalletLicense: MIT
15119

Install this agent skill to your local

pnpm dlx add-skill https://github.com/peteromallet/VibeComfy/tree/HEAD/docs/agent-skill/skills/debug-comfy-workflow

Skill Files

Browse the full folder contents for debug-comfy-workflow.

Download Skill

Loading file tree…

docs/agent-skill/skills/debug-comfy-workflow/SKILL.md

Skill Metadata

Name
debug-comfy-workflow
Description
Diagnose a VibeComfy or ComfyUI workflow that fails validation, conversion, node/model resolution, runtime execution, or output production. Use when the user asks why a workflow does not run, has missing nodes/models, validation errors, bad wiring, failed RunPod/local runs, or confusing agent-edit failures.

Debug Comfy Workflow

Debug from cheap static evidence toward expensive runtime evidence. Decide first whether the failure is the graph, dependencies, or the runtime.

First Pass

vibecomfy inspect <workflow>
vibecomfy validate <workflow>
vibecomfy doctor <workflow> --json
vibecomfy analyze info <workflow>

For source JSON or conversion failures, keep the source as import evidence and do not execute its API export directly:

vibecomfy import <workflow.json>
vibecomfy validate workflows/<source-stem> --json
vibecomfy port doctor-all <workflow.json> --json
vibecomfy port widgets <workflow.json> --json

For runtime failures:

vibecomfy runtime doctor
vibecomfy logs tail
vibecomfy watchdog list

Missing Nodes Or Models

vibecomfy nodes install-plan <workflow>
vibecomfy nodes spec <ClassType>
vibecomfy fetch <workflow> --dry-run
vibecomfy models stage --select-phase core --dry-run

Install or download only after the evidence supports it and the user agrees.

For custom Python failures, separate these cases:

  • malformed io, unknown bindings, or an invalid result shape: fix the node declaration or explicit adapter;
  • missing declared distribution: prepare the selected worker with setup tools;
  • missing snapshot member, archive/member digest mismatch, unsafe path, or absolute snapshot self-import: recapture with relative imports or use the installed-entrypoint mode;
  • source traceback: inspect the reported source entrypoint and runtime line;
  • changed bundle/source revision: reload and retry the canonical transaction.

Discipline

  • Keep graph errors separate from environment errors.
  • If embedded ComfyUI is not discoverable, use vibecomfy-setup; that is not a workflow bug.
  • Do not recommend arbitrary node packs. Require nodes install-plan, lockfile data, registry evidence, or a concrete precedent.
  • If class/schema evidence is missing, use search-comfy-workflows before patching.
  • Preserve report paths and cite the exact command output or file that supports the diagnosis.