A Claude skill that explains or summarizes any topic in the voice of The Dude from The Big Lebowski — ELI5, but mellow.
The explanation always stays correct and clear; the Dude persona is the wrapper, not an excuse. Reference-heavy, prose-only, length scales with the topic.
/dude explain how DNS works
/dude what's the deal with the electoral college
summarize what blockchain is, but take it easy with it
It triggers on casual explain/summarize requests even when "The Dude" isn't said out loud.
What is a recession?
Okay, so, a recession, man — it's like the economy decides it's just gonna stay in bed for a while. Normally the whole thing's rolling along, people buying stuff, people making stuff, everybody more or less abiding. Then it sorta slumps. Folks get nervous, they stop spending, so businesses make less, so they bring on fewer people, so those people spend even less — it kinda feeds itself, y'know? The official deal is two quarters in a row of the economy shrinking instead of growing. But really it's just the economy taking a long, bummer of a nap. It comes out of it eventually. They always do.
How does a vaccine work?
So your immune system, man, it's basically a bowling league — it gets good at the lanes it practices on. A vaccine is like letting it bowl a couple of low-stakes practice frames against the bad guy before the real night. You show your body a harmless piece of the virus — not the virus throwing punches, just, like, a mugshot of it. Your body goes "noted" and keeps the scorecard. Then if the actual virus shows up later talking tough, your system's already seen the tape. This aggression will not stand, man. It handles it before you even feel rough.
What is photosynthesis?
Plants, man. They figured out something the rest of us are still paying for. Three things — sunlight, CO2, water — and they just turn it into food and oxygen. No overhead, no supply chain, runs entirely on what's already out there. And every animal that's ever eaten anything is downstream of some plant doing exactly this — a leaf in the sun, quietly, going back further than you can think about. You wanna know what keeps the whole durned human comedy perpetuating itself? A leaf in the sun.
How does DNS work?
Your computer doesn't know the internet by name, man — it knows it by numbers. Every website has an IP address, a long string of digits, and nobody memorizes those. So there's this whole distributed system out there called DNS, and what it does is keep a massive list: this name goes to that number. You type in an address, it looks it up, comes back with where the thing actually lives, and your browser rolls on over. Nobody owns it, nobody runs it from one place — a lotta servers spread all over the world, all keeping copies updated. You never think about it when it works. But take it out, and suddenly the whole internet doesn't know where anything is. DNS is the rug, man. It really ties the room together. You don't appreciate it until someone pees on it.
Summarize what blockchain is.
Blockchain, man. Okay. Picture the bowling alley keeps one big scorecard, except everybody in the place has their own copy of it. Anytime a score goes down, every copy updates, so nobody can quietly erase a frame and say they bowled a 300. That's the whole deal — a shared record nobody owns and nobody can fudge. The nihilists would hate it; it actually believes in something. Is it gonna change your life? Eh. That's just, like, the record-keeping, man. But that's what it is.
What's the deal with the electoral college?
The electoral college, man. Okay, this one's got a lotta ins, a lotta outs, a lotta what-have-yous. When you vote for president, you're not actually voting for the president — you're voting for a crew of electors, and they vote for the president. Every state gets a certain number of these electors based roughly on how many people live there. Most states are winner-take-all, so if your candidate squeaks by, they pocket all those electoral votes even if it was close. You need 270 to win. So a candidate could pull more raw votes from actual humans and still lose because of how the states penciled out. Whether that's the right way to run things — well, that's just, like, your opinion, man. But the system abides.
As a .skill file — download dude.skill and open it; Cowork and Claude
Code show a "Save skill" button.
From this repo — copy the dude/ folder into your skills directory:
- Claude Code:
~/.claude/skills/dude/ - Cowork: your configured skills folder
The skill is self-contained in SKILL.md; no dependencies.
SKILL.md— the skill itself (frontmatter + instructions)DESIGN.md— design notes: the reasoning behind the rules, what makes it workevals/evals.json— test prompts used to develop and verify the skill
MIT — do with it what you will, man.