Clip Skip Slider

This node does exactly one thing: it hands you an INT between -24 and -1, defaulting to -1. That's it - no CLIP input, no model, nothing gets skipped by this node itself. What it's really for is giving CLIP skip its own labeled control on the canvas instead of leaving it buried as a bare widget on a CLIPSetLastLayer node, or worse, hard-typing a number you'll forget the meaning of in a month.

Why this range, specifically

The -24 to -1 bounds aren't arbitrary - they're lifted straight from ComfyUI's own CLIPSetLastLayer node, whose stop_at_clip_layer input is an INT that defaults to -1 with that exact -24 to -1 range. So this slider isn't inventing a new convention, it's a standalone copy of the real control, useful anywhere you want to drive that value from a separate, clearly-labeled node - say, feeding the same skip value into two CLIP loaders at once, or parking it somewhere visible in a busy graph instead of hunting for the small widget on a loader node.

If you're coming from Automatic1111 or a checkpoint's model card, the sign and counting convention is the part that trips people up. A1111 counts CLIP skip 1 through 12, going up as you skip more layers. ComfyUI counts down from -1, so A1111's "CLIP skip 2" is ComfyUI's -2. There's a third convention too - InvokeAI counts 0 to 12 - so if a model card just says "CLIP skip 2" without naming the software, assume it means -2 here.

What it actually changes

CLIP skip stops the text encoder a layer or two before its final one, conditioning the image on a slightly more general read of your prompt. It's a real, load-bearing setting on SD 1.5 anime checkpoints (Pony, Illustrious, and NoobAI's whole lineage inherited the convention 2 / -2 from NovelAI's original choice back in 2022), and it's part of why a LoRA trained at CLIP skip 2 can look wrong if you run it at the default. But here's the part worth knowing before you obsess over the slider: SDXL already initializes both of its text encoders at the penultimate layer by default, meaning an SDXL checkpoint is effectively already running at -2 before you touch anything. Setting -1 (no skip) on Pony V6 is what turns it to noise; setting -2 doesn't improve on the default, it just matches it. So the advice on SDXL-family models is really "don't set -1," not "tune this dial."

Wiring it in

Output is a single value (INT). Feed it into the stop_at_clip_layer input of a CLIPSetLastLayer node, upstream of your CLIP Text Encode nodes. That's the whole job - this node is a value source, the actual skipping happens on the node it feeds.

How to install it

ComfyUI Manager: search DemonAlone-nodes-ComfyUI, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/DemonAlone/DemonAlone-nodes-ComfyUI

then restart. No extra pip installs or model downloads - this is a pure utility pack, and once it's in, all its nodes (this one included) show up together.

Common issues & troubleshooting

I set it and nothing changed. If you're on an SDXL-family checkpoint, this is often expected - see above. Confirm the value is actually reaching a CLIPSetLastLayer node and not just sitting unconnected on the canvas.

My LoRA looks off. CLIP skip mismatch is a standard entry on the LoRA-not-working checklist, right alongside wrong base model and a missing trigger word. If the LoRA's card says CLIP skip 2, dial this to -2.

The model card doesn't say which convention it's using. Assume A1111's 1-12 numbering unless it explicitly names ComfyUI, then negate and subtract one to get this node's value (A1111 2 → -2 here).

Do I even need to touch this on a non-anime model. Mostly no. CLIP skip is a Danbooru-lineage convention; on realistic SD 1.5 checkpoints leave it at -1, and on 2026-era models built on Qwen or Mistral text encoders there's no CLIP to skip at all - the setting simply doesn't apply.