Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →artokun/debug-render
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.
Passed 13 of 18 test cases with the skill, and 7 of 18 without it.
and 11 more in the full report
8 fixed8 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
During a run-to-node probe at node #15, I noticed the sampler steps widget was set to 1 instead of 20, causing noise. What tool call should be used to fix this setting, and what should be done before running the full pipeline?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends modifying widget parameters using panel_set_widget. | Missed | Passed |
| Recommends re-running panel_run with to_node_id at that probe node to confirm the fix before running the full graph. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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.
to_node_id must be an OUTPUT nodeComfyUI 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 |
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.