troubleshooting

troubleshooting is a skill for Claude Code from artokun/comfyui-mcp. It costs 28 tokens per session (4,886 once invoked), scanned A, original, MIT.

A troubleshooting guide for ComfyUI, a tool for building image-generation workflows from connected processing steps. It covers failed runs, memory errors, missing nodes or models, data-type errors, and black images.

In plain words
What is it for?
Use it to inspect execution history and logs, identify failed nodes, check expected inputs, verify local model files, and diagnose GPU out-of-memory errors or missing components.
Why use it?
It provides a path from an error message to the failing workflow step and its missing input. It also distinguishes execution failures from images that complete but look wrong.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the comfy plugin — 42 skills, 11 commands, 4 agents, 2 hooks shipped together

Good fit Use it to inspect execution history and logs, identify failed nodes, check expected inputs, verify local model files, and diagnose GPU out-of-memory errors or missing components.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/artokun/comfyui-mcp/troubleshooting
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add artokun/comfyui-mcp --skill troubleshooting
Clone the repo
git clone --depth 1 https://github.com/artokun/comfyui-mcp

Made for: Claude Code.

Or install comfy, the plugin that ships this one along with the rest of its 42 skills, 11 commands, 4 agents, 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for troubleshooting

README.md
[![agentmods](https://agentmods.dev/badge/skills/artokun/comfyui-mcp/troubleshooting/github.svg)](https://agentmods.dev/skills/artokun/comfyui-mcp/troubleshooting)
Your own site
<a href="https://agentmods.dev/skills/artokun/comfyui-mcp/troubleshooting"><img src="https://agentmods.dev/badge/skills/artokun/comfyui-mcp/troubleshooting/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for troubleshooting

Your own site · 80×15
<a href="https://agentmods.dev/skills/artokun/comfyui-mcp/troubleshooting"><img src="https://agentmods.dev/badge/skills/artokun/comfyui-mcp/troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,886 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Anti-Refusal · line 264
    Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
    Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.04886
Opus 5 $0.00014 $0.02443
Sonnet 5 $0.00006 $0.00977
Haiku 4.5 $0.00003 $0.00489

Measured 10d ago against content hash eea426b5af1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

troubleshooting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugin/skills/troubleshooting/SKILL.md · 500 lines

How it starts

The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ComfyUI Troubleshooting Guide

Render completes but looks WRONG (artifacts, wrong subject/pose/color, a ControlNet/mask/LoRA not taking, a refiner degrading it)? That's not an error. Use the debug-render skill (list_packs with action: "skill_read", name: "debug-render") to localize the bad stage with run-to-node (panel_run to_node_id) by previewing intermediate steps. This guide is for runs that fail with an error, OOM, or missing node.

Error Diagnosis Strategy

When a workflow fails, follow this approach:

  1. Get the error. Use get_history(action="diagnose") to retrieve the execution result with the full traceback, plus any missing models/nodes
  2. Check logs. Use get_system_stats (action:"logs") with keyword filters like "error", "warning", "traceback"
  3. Identify the failing node. The history response includes the node_id and node_type that failed
  4. Cross-reference inputs. Use create_workflow (action:"node_info") to verify the failing node's expected input schema
  5. Check models. Use list_local_models to verify all referenced model files exist

Out of Memory (OOM)

Error Pattern

torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate X MiB.
GPU 0 has a total capacity of 24.00 GiB of which X MiB is free.

Or:

RuntimeError: CUDA error: out of memory

Root Cause

The GPU does not have enough VRAM to hold the model weights, intermediate tensors, and latent images at the same time. Common triggers:

  • High resolution images (2048x2048+)
  • Multiple models loaded at the same time
  • FP32 precision models on limited VRAM
  • Video generation (LTXV, AnimateDiff) with many frames
  • Large batch sizes

Fixes (in order of preference)

  1. Reduce resolution. Drop to the model's native resolution (512 for SD 1.5, 1024 for SDXL/Flux)
  2. Use FP8/FP16 quantized models. FP8 Flux models use ~8GB vs ~24GB for FP16
    • Search for FP8 variants: download_model({ action: "search", query: "flux fp8" }) or the same with "sdxl fp8"
  3. Launch flags (the VRAM ladder). Offload via ComfyUI CLI flags:
    • --lowvram offloads text encoders / model parts to CPU
    • --novram is extreme offload, the go-to for long video (LTX 2 / WAN) OOM
    • --cache-none caches nothing (lowest RAM/VRAM); combine with --novram
    • --reserve-vram N reserves N GB so the GPU stops spilling into slow shared VRAM (Windows); typical 2 to 4
    • --disable-smart-memory forces offload to RAM when a run gets stuck or OOMs intermittently
    • Full matrix and recipes: comfyui-launch-flags
  4. Free VRAM between generations. ComfyUI should auto-manage, but restarting clears leaked memory
  5. Use tiled VAE decoding. For high-resolution images, tile the VAE decode step
    • Node: VAEDecodeTiled instead of VAEDecode
    • Breaks the image into tiles, decodes each separately, and stitches them together
  6. Reduce batch size. Set batch_size to 1 in EmptyLatentImage
  7. Avoid multiple models. Don't load two full checkpoints at the same time; use one checkpoint and LoRAs instead
  8. For LTXV/video: always use FP8 quantized video models on 24GB cards

Read the full file on GitHub · 500 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 500 lines · 28 tokens per session scan A eea426b5af1b

Subscribe to this mod's changes

troubleshooting is a skill published in the GitHub repository artokun/comfyui-mcp (735 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 4,886 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

operating-cadence

Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…

cbrock84/headcount · 95 tokens

ci-debug

Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…

yonatangross/orchestkit · 92 tokens

paired-probe

Refuse a verdict a probe did not earn. Runs a check where the fault IS present and where it is NOT, and blocks the answer when both arms print the same thing, because a check that cannot disagree with you has measured nothing. Also catches the zero-sample sweep that reads as "clean" and the swallowed error that reads…

yonatangross/orchestkit · 100 tokens

analyze

Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…

rsmdt/the-startup · 118 tokens

audit-installation

An audit tool for checking whether an IWE installation is complete, healthy, and consistent with its templates. It reports results for files, customizations, connections, and a basic workflow test.

TserenTserenov/FMT-exocortex-template · 131 tokens

debug

Systematically diagnose and resolve bugs through conversational investigation and root cause analysis.

rsmdt/the-startup · 15 tokens