Skip to content
Skills Library
AI & agents · Analysis

debug-comfy-workflow

/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.

Repository
VibeComfy ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author 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.

How it works

  1. First Pass
  2. Missing Nodes Or Models
  3. Discipline
Original SKILL.md headings · 61 lines, 282 words
SKILL.md preview
---
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

```bash
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:

```bash
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:

```bash
vibecomfy runtime doctor
vibecomfy logs tail
vibecomfy watchdog list
```

## Missing Nodes Or Models

```bash
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.

Versions

The database has no other skills named debug-comfy-workflow.

Database snapshot: 13.11.2026 · package version 23385ab438f2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100run-comfy-workflow
    Execute an existing VibeComfy/ComfyUI workflow, ready template, recipe, or scratchpad and collect outputs. Use when the user asks to run, queue, execute, generate, render, smoke test, use a local/remote ComfyUI runtime, or run on RunPod.
  • 95vibecomfy
    Drive the VibeComfy package to discover ComfyUI workflows, load ready Python templates, edit and compose them in a `VibeWorkflow` IR, validate, and execute either embedded locally, against an existing ComfyUI server, or on RunPod. Use whenever the user wants to generate…
  • 96comfy-workflow-authoring
    Use when building or changing a saved ComfyUI workflow.
  • 100comfy-run-on-cloud
    Use when someone wants a workflow from their local ComfyUI running on Comfy Cloud, clicked Run on Cloud, or pasted a Run on Cloud prompt. Checks the workflow against Comfy Cloud, uses an existing build or a node swap where Cloud lacks something, runs one real job, saves the…
  • 95comfy-cli-skills
    Installs comfy-cli's bundled agent skills into any harness and sets the zero-cost validate gate and credit audit for paid ComfyUI runs. Use when setting up comfy-cli, when comfy skills are missing, or before a workflow run that bills partner-node credits.
  • 100comfy-cli
    The `comfy` CLI for ComfyUI: install/update/bisect custom nodes, snapshot/restore state, publish to the registry, run workflows headlessly. Use when the user runs `comfy`, `comfy node`, or `comfy run`.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.