Yesterday a clever little build landed in r/PromptEngineering, and the second thing it does is the real twist.
It’s called /null, and it does something most AI tools never bother with: it shuts Claude up.
A Redditor going by u/Pitiful_Bat8731 built it after getting tired of Claude filling in every gap before they’d even finished a thought. Instead of writing the code by hand, the creator described the skill and had Codex build it. The repo sits on GitHub, MIT licensed, free for anyone to fork or copy.
Here’s what /null actually does. You type “/null” and Claude flips into a different mode. You think out loud, question by question, decision by decision. Claude replies with one word: “Received.” No suggestions, no “here’s what I’d try,” no filling in the blanks you haven’t gotten to yet. It only answers when you directly ask it something. Type “null off” and the mode ends, and Claude goes back to normal.
Now the twist. The skill ships with disable-model-invocation: true, so Claude can never flip this on by itself. You have to ask for it, every single time. That one line is what separates this from just telling a model “be quiet” in a system prompt. This is deliberate, opt-in silence, not a personality trait Claude might drop the moment it thinks jumping in would help.
There’s also a companion prompt built for a fresh subagent thread. On runtimes that support it, you can hand the subagent only the text you’ve selected. Cleaner separation between “I’m still thinking” and “now give me your take.”
Here’s the mini-workflow if you want to try it yourself:
- 🧠 Type “/null” before you start dumping raw thoughts into the chat.
- ✍️ Think out loud, one question or decision at a time. Claude just says “Received” and waits.
- ❓ Ask directly for anything you actually want answered. That’s the only thing that breaks the silence.
- 🔚 Type “null off” when you’re done, and Claude returns to its usual self.
Getting it running takes about two minutes. Clone the repo, drop the skill file into your setup the same way you’d add any other Claude skill, and it’s live right away. No extra dependencies, no config beyond the trigger phrase itself.
Compare that to the usual workaround people use: telling Claude in a system prompt to hold back until asked. That approach drifts fast. The model forgets the instruction a few turns in, or decides your question implies you want more than you actually asked for. /null solves the drift problem by making the mode explicit, easy to toggle, and impossible for Claude to switch on for you.
One commenter on the thread compared it to rubber duck debugging, except the duck eventually talks back. Another admitted they’d been running a janky version of this for a while, just telling Claude to shut up until a keyword. Having it packaged as an actual skill, instead of a one-off instruction you retype every session, is the real upgrade.
Worth staying honest about the limits here, same as the creator was upfront about in the original writeup. The skill can’t erase context Claude already has, and it can’t guarantee neutrality the moment you do ask for input. The testing behind it is thin too. Nine of twenty written behavioral cases got run once, against an earlier revision of the skill. There’s no measured success rate. The only evidence is one dictation session the creator wrote up and compared against two edited versions on their own blog.
I like tools that force restraint instead of adding more automation on top of automation. Most of what gets built for Claude tries to make it say more, faster. This one just asks it to wait.
Pro tip: use /null right when an idea is still messy, before you’ve decided anything. That’s the whole point of the tool. Once you already know what you think, just ask Claude directly, the silence isn’t buying you anything anymore.
Pro tip: pair it with the subagent version if your setup supports it. Selected text only, no bleed from earlier context, especially handy if you’re dictating something long like a full article.
If you’re the type who talks to Claude the way other people talk to a whiteboard, this is worth five minutes of your time. Grab the skill, or read the writeup showing the original dictation next to both edited versions. Then decide: a model that jumps in immediately, or one that waits until you’re actually ready. 🏴☠
Frequently Asked Questions
Q: How is /null different from rubber duck debugging?
/null is rubber duck debugging with a twist, the duck talks back. With traditional rubber duck debugging, you explain your thoughts to an inanimate object and gain clarity through the act of explaining. With /null, you get that same forced-clarity benefit of thinking out loud, but once you’re ready, you can ask Claude for feedback on your finished thoughts. It’s the best of both worlds: silent thinking space plus the power of AI suggestions when you ask for them.
Q: What’s the advantage over just asking Claude to “stay quiet”?
Users have been DIY-ing this by giving manual instructions to shut up, but /null bakes it into the system as a proper mode, much more reliable. It uses `disable-model-invocation: true` under the hood, which actually prevents Claude from filling in gaps while you think. Toggling it with `/null` and `null off` is also faster and cleaner than rewording the same workaround every time.
Q: When should I actually use /null instead of asking Claude directly?
Use it when you’re exploring new ideas, brainstorming before you’ve landed on a direction, or organizing your thoughts in real time (like dictating an article). The creator found it especially useful for forcing more coherent thinking during voice dictation. If you already know what you’re asking for, direct questions are faster. If you’re discovering your thoughts as you go, /null gives you the space to finish that discovery first.
Q: Does /null guarantee neutral or unbiased thinking?
No, the creator is transparent about this. /null doesn’t erase your existing context or guarantee neutrality. What it does is give you quiet space to develop your own ideas before Claude weighs in, which often leads to more complete thoughts naturally. Think of it as a clarity tool, not a bias eliminator.
/null: a skill for thinking out loud before asking Claude for input
by u/Pitiful_Bat8731 in PromptEngineering