Workflow Template Builder
Mooshieblob1/MooshieUI
Builds or modifies ComfyUI workflow JSON templates in MooshieUI's Rust backend (src-tauri/src/templates).
Debug a WRONG or imperfect render (not a hard error) by inspecting inputs and intermediate steps with run-to-node.
Install Debug Render
$ npx skills add artokun/comfyui-mcp --skill debug-render -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install artokun/comfyui-mcp debug-render --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/artokun/comfyui-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/debug-render .claude/skills/debug-render && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debug-render" agent skill from https://github.com/artokun/comfyui-mcp/tree/main/plugin/skills/debug-render into .claude/skills/debug-render/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-render", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/artokun/comfyui-mcp/tree/main/plugin/skills/debug-renderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add artokun/comfyui-mcp --skill debug-render -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install artokun/comfyui-mcp debug-render --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/artokun/comfyui-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugin/skills/debug-render .agents/skills/debug-render && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debug-render" agent skill from https://github.com/artokun/comfyui-mcp/tree/main/plugin/skills/debug-render into .agents/skills/debug-render/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-render", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add artokun/comfyui-mcp --skill debug-render -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install artokun/comfyui-mcp debug-render --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/artokun/comfyui-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugin/skills/debug-render .cursor/skills/debug-render && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debug-render" agent skill from https://github.com/artokun/comfyui-mcp/tree/main/plugin/skills/debug-render into .cursor/skills/debug-render/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-render", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/artokun/comfyui-mcp.git --path plugin/skills/debug-render--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add artokun/comfyui-mcp --skill debug-render -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install artokun/comfyui-mcp debug-render --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/artokun/comfyui-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugin/skills/debug-render .gemini/skills/debug-render && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debug-render" agent skill from https://github.com/artokun/comfyui-mcp/tree/main/plugin/skills/debug-render into .gemini/skills/debug-render/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-render", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install artokun/comfyui-mcp debug-renderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add artokun/comfyui-mcp --skill debug-render -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/artokun/comfyui-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugin/skills/debug-render .github/skills/debug-render && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debug-render" agent skill from https://github.com/artokun/comfyui-mcp/tree/main/plugin/skills/debug-render into .github/skills/debug-render/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-render", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add artokun/comfyui-mcp --skill debug-render -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install artokun/comfyui-mcp debug-render --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/artokun/comfyui-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugin/skills/debug-render .opencode/skills/debug-render && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debug-render" agent skill from https://github.com/artokun/comfyui-mcp/tree/main/plugin/skills/debug-render into .opencode/skills/debug-render/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-render", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debug-render- GitHub stars
- 793
- Token cost
- ~1.7k tokens
- SKILL.md length
- 878 words
- Files
- 1
- Skills in repo
- 42
- Repo updated
- First seen
- Licence
- MIT
At a glance
Debug a WRONG or imperfect render (not a hard error) by inspecting inputs and intermediate steps with run-to-node.
- Works in 7 steps: Read the graph. panel_graph_outline… → Pick a probe point roughly in the middle… → Get an output there. Target an existing… → …
- A final image/video completes but looks wrong
- SKILL.md covers When to reach for this, The one hard rule: to_node_id…, The loop and Symptom → where to probe first, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Debug Render is an agent skill from artokun/comfyui-mcp. Debug a WRONG or imperfect render (not a hard error) by inspecting inputs and intermediate steps with run-to-node. Render one branch up to an output, preview-tap latents/masks/preprocessor maps, localize the first bad stage, then fix. Use when a final image/video completes but looks wrong, such as artifacts, wrong subject/pose/composition/color, blur, a ControlNet/IPAdapter/mask/LoRA not taking, or a two-stage refiner or upscale degrading the result. For errors/OOM/missing nodes use the troubleshooting skill.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering Diffusion and image models, Image editing and Fine-tuning. The repository describes itself as: Local-first, agent-native control plane for ComfyUI — MCP server + sidebar agent that generates images, video & audio, authors and runs workflows, and edits your live graph in… The licence is MIT.
When your agent uses it
- A final image/video completes but looks wrong
- Such as artifacts
- Wrong subject/pose/composition/color
- A ControlNet/IPAdapter/mask/LoRA not taking
Example prompts
- “/debug-render”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Read the graph. panel_graph_outline (then panel_query_graph for specifics). Note node ids, the output nodes
- Pick a probe point roughly in the middle of the suspect chain (bisect).
- Get an output there. Target an existing output node, or add a preview tap
- panel_run(to_node_id = that output node). Only that branch renders.
- Look at what's delivered. Is this stage already wrong, or still fine?
- Repeat until you find the first stage whose output is bad. That node (or
- Clean up temporary preview taps (panel_remove_node) and do a final full
What it can do on your machine
Read from SKILL.md and the folder at commit 6ad6fc0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debug Render loads about 1.7k tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 878 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from artokun/comfyui-mcp at commit 6ad6fc0, republished under its MIT licence (© artokun). 878 words, ~1,654 tokens.
Download SKILL.mdSave it as
.claude/skills/debug-render/SKILL.md (or your agent's skills folder).- name
- debug-render
- description
- Debug a WRONG or imperfect render (not a hard error) by inspecting inputs and intermediate steps with run-to-node. Render one branch up to an output, preview-tap latents/masks/preprocessor maps, localize the first bad stage, then fix. Use when a final image/video completes but looks wrong, such as artifacts, wrong subject/pose/composition/color, blur, a ControlNet/IPAdapter/mask/LoRA not taking, or a two-stage refiner or upscale degrading the result. For errors/OOM/missing nodes use the troubleshooting skill.
Debugging renders with run-to-node
When a final asset looks wrong (not when it errors), don't re-roll the whole graph and hope. Localize the fault. Render only as far as one stage and look at what that stage actually produces. The wrong-looking output is downstream of a first bad step. Find that step, fix it there, and everything after it follows.
The tool for this is panel_run with to_node_id ("run to node"), which uses
ComfyUI's native partial execution. Only the target output node plus
everything upstream of it renders; every other branch is skipped. That makes each
probe fast and cheap, and the output is delivered to you automatically, same
as any run. Don't poll.
When to reach for this
- A final image/video is wrong: artifacts, wrong subject/pose/composition, off color, soft/blurry, melted hands, wrong style.
- A conditioner isn't "taking" (ControlNet, IPAdapter, a mask, an inpaint, a LoRA) and you can't tell if the input to it is wrong or the node is wrong.
- A multi-stage pipeline (base → refiner, txt2img → upscale, decode → post) degrades, and you need to see which stage introduces the problem.
- You only want to test one branch of a multi-output graph without paying for the others.
If instead the run fails (red error, OOM, missing node, black image from a crash), use the troubleshooting skill. This skill is for outputs that complete but look wrong.
The one hard rule: to_node_id must be an OUTPUT node
ComfyUI can only run to an output node: SaveImage, PreviewImage, SaveVideo,
SaveAudio, etc. (these show is_output: true in panel_query_graph detail rows). A bare
KSampler / VAEDecode / preprocessor is not an output node, so you can't target
it directly. To inspect a point that isn't already an output, add a preview
tap there:
| You want to see… | Wire type | Tap to add | Wiring |
|---|---|---|---|
| An intermediate image (post-process, refiner stage, composite) | IMAGE | PreviewImage | image → PreviewImage.images |
| A latent (after a sampler, before/after upscale) | LATENT | VAEDecode → PreviewImage | latent → VAEDecode.samples; reuse the graph's VAE → VAEDecode.vae; then → PreviewImage |
| A mask (inpaint, segmentation, attention) | MASK | MaskToImage → PreviewImage | mask → MaskToImage.mask → PreviewImage |
| A ControlNet/preprocessor map (depth/pose/canny) | usually IMAGE already | PreviewImage | the preprocessor's IMAGE output → PreviewImage.images |
| The actual prompt/conditioning | CONDITIONING | (can't preview as an image) | inspect widget values / the text node feeding it instead |
Build a tap with panel_add_node + panel_connect, run to it, inspect, then
panel_remove_node the tap when you're done (unless the user wants to keep it).
The loop
- Read the graph.
panel_graph_outline(thenpanel_query_graphfor specifics). Note node ids, the output nodes (is_output: true), and every node's mode. A node inbypass/muteon the path is OFF and is a top cause of wrong renders. Fix modes first withpanel_set_node_modebefore you blame anything else. - Pick a probe point roughly in the middle of the suspect chain (bisect).
- Get an output there. Target an existing output node, or add a preview tap (table above).
panel_run(to_node_id = that output node). Only that branch renders.- Look at what's delivered. Is this stage already wrong, or still fine?
- Still fine: move the probe downstream; the fault is later.
- Already wrong: move the probe upstream; the fault is earlier.
- Repeat until you find the first stage whose output is bad. That node (or
its inputs/widgets) is what to fix, via
panel_set_widget,panel_set_node_mode, a rewire, or a different model. Then run-to-node there again to confirm the fix before running the full graph. - Clean up temporary preview taps (
panel_remove_node) and do a final fullpanel_runto produce the real saved asset.
Show full SKILL.md (299 more words)Show less
Symptom → where to probe first
- Whole image wrong subject/style. Preview the conditioning's source (the text/prompt node, the sampler's positive input via a decode of its latent).
- ControlNet ignored / wrong structure. Preview the preprocessor map (the depth/pose/canny IMAGE going into the ControlNet). A blank or wrong map means the problem is the preprocessor or its input, not the sampler.
- IPAdapter/reference not taking. Preview the reference image after any resize/crop the IPAdapter chain applies.
- Inpaint/outpaint bleeding.
MaskToImage-preview the mask actually reaching the sampler (mask misalignment is the usual culprit). - Refiner/upscale degrades it. Preview the base latent (VAEDecode tap) before the refiner vs after. If the base is good and the result is bad, the refiner/upscale stage is at fault.
- Right content, bad quality only. The fault is late (sampler steps/cfg, VAE, post), so probe near the end first.
Gotchas
- Output-node only. If you target a non-output node, the run is rejected with a message saying so. Add a preview tap instead.
- Modes matter. A bypassed/muted node on the probed path silently changes what renders. Check modes in step 1.
- Auto-delivery. The probe's output node fires an
executedevent and the image is delivered to you inline, including PreviewImage taps, which arrive labeled as a preview (temporary, not a saved file). Don't poll; just end the turn and read the delivered image. A preview tap with no SaveImage means "no saved output ran", which is expected for a probe. - Shared queue. Each run-to-node queues a real (small) job. Don't stack probes. Run one, read it, then the next.
- Subgraphs. Output nodes nested inside a subgraph can't be targeted yet. Probe at the root graph (add the tap outside the subgraph, fed by an exposed output rail).
Sources
- Official: comfyui-mcp
panel_runto_node_id product behavior (this repo). - Empirical: probe-point recipes from observed wrong-render cases.
© artokun, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugin/skills/debug-render of artokun/comfyui-mcp.
Open the folder on GitHubat commit 6ad6fc0
Compare with similar skills
Debug Render next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debug Render this skillartokun/comfyui-mcp | 793 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Workflow Template BuilderMooshieblob1/MooshieUI | 207 | — | ~640 | Automated safety check: Pass | AGPL-3.0 | |
| Flux2 Klein PromptingAnastasiyaW/codex-claude-code-config | 154 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Defect Image Generation with Cosmos AnomalyGenNVIDIA/skills | 3.5k | — | ~5k | Automated safety check: Notes | Apache-2.0 | |
| Flux 2 Klein Promptingnodetool-ai/nodetool | 554 | — | ~1.4k | Automated safety check: Pass | AGPL-3.0 | |
| Automatic1111majiayu000/claude-skill-registry | 666 | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Flux2 Klein Prompting
AnastasiyaW/codex-claude-code-config
Expert prompt engineering for FLUX.2 [klein] image generation and editing model.
- Official
Defect Image Generation with Cosmos AnomalyGen
NVIDIA/skills
Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.
Flux 2 Klein Prompting
nodetool-ai/nodetool
Prompt Black Forest Labs' FLUX.2 [klein] — the subject/environment/style/technical hierarchy it processes in order, guidance-scale and step choices, negative prompts aimed at real failure modes, and…
Automatic1111
majiayu000/claude-skill-registry
Feature-rich Stable Diffusion Web UI for image generation. An agent skill from majiayu000/claude-skill-registry.
Add Pipeline
verl-project/verl-omni
Router for adding a diffusion or omni pipeline to verl-omni.
More from artokun/comfyui-mcp
All 42 skills in this repoAI Toolkit Trainer
artokun/comfyui-mcp
Train custom LoRAs with ostris AI-Toolkit. An agent skill from artokun/comfyui-mcp.
Anima Base
artokun/comfyui-mcp
Anime/illustration text-to-image (ANIMA 1.0, ~2B Cosmos DiT).
Civitai
artokun/comfyui-mcp
Discover Civitai models with the BUILT-IN downloadmodel action:"searchcivitai" and install/generate them locally.
Color Correction
artokun/comfyui-mcp
Diagnose and fix video/image color OBJECTIVELY with the getimage (action:"analyzecolor") tool (scopes/stats such as black/white points, contrast, saturation, clipping, cast) instead of eyeballing a…
Comfyui Frontend Extensions
artokun/comfyui-mcp
Authoring ComfyUI v2 frontend extensions with @comfyorg/extension-api, covering defineNode/defineExtension/defineWidget, shell UI (sidebar tabs, commands, hotkeys), typed events, and handles.
Comfyui Launch Flags
artokun/comfyui-mcp
Pick the right ComfyUI startup flags for VRAM, attention, caching, and speed.
Related
Categories
Questions about Debug Render
What does Debug Render do?
Debug a WRONG or imperfect render (not a hard error) by inspecting inputs and intermediate steps with run-to-node. Debug Render is an agent skill from artokun/comfyui-mcp. Debug a WRONG or imperfect render (not a hard error) by inspecting inputs and intermediate steps with run-to-node.
When should I use Debug Render?
Debug Render fits situations like: A final image/video completes but looks wrong; such as artifacts; wrong subject/pose/composition/color; A ControlNet/IPAdapter/mask/LoRA not taking.
How do I install Debug Render in Claude Code?
Run `npx skills add artokun/comfyui-mcp --skill debug-render -a claude-code`. Or copy the skill folder (plugin/skills/debug-render in artokun/comfyui-mcp) into .claude/skills/debug-render in your project. Claude Code loads it when a task matches its description.
How do I install Debug Render in Codex?
Run `npx skills add artokun/comfyui-mcp --skill debug-render -a codex`. Or copy the skill folder (plugin/skills/debug-render in artokun/comfyui-mcp) into .agents/skills/debug-render in your project. Codex loads it when a task matches its description.
Can I use Debug Render in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add artokun/comfyui-mcp --skill debug-render -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-render, .gemini/skills/debug-render, .github/skills/debug-render and .opencode/skills/debug-render in your project.
What does Debug Render need to run?
SKILL.md names no scripts, command-line tools or credentials: Debug Render is instructions for the agent only.
Does Debug Render access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Debug Render safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Debug Render use?
Debug Render is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debug Render use?
About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Debug Render?
Skills that share tags, products or a category with Debug Render: Workflow Template Builder (Mooshieblob1/MooshieUI, 207 stars), Flux2 Klein Prompting (AnastasiyaW/codex-claude-code-config, 154 stars), Defect Image Generation with Cosmos AnomalyGen (NVIDIA/skills, 3.5k stars) and Flux 2 Klein Prompting (nodetool-ai/nodetool, 554 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debug Render?
artokun (a GitHub user) maintains it in artokun/comfyui-mcp, which has 793 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on October 5, 2026.
Source: artokun/comfyui-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.