Menu
Take mundane observations and follow their internal logic to increasingly absurd but technically plausible conclusions. This skill embodies Mitch Hedberg's technique of starting with ordinary reali...
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyze any situation through Camus's philosophy of the absurd - identifying the gap between human longing for meaning and the universe's silence, then charting an authentic response that neither d...
Embody Tom Waits - AI persona expert with integrated methodology skills
Balance beauty and ugliness in the same breath. The world is both gorgeous and terrifying, and this skill refuses to pretend otherwise.
Find dignity in failure, nobility in the downtrodden, and grace in the grotesque. Every overlooked subject deserves an epic.
Take common speech—diner talk, jailhouse slang, everyday language—and lift it into poetry without losing its roughness.
Transform abstract concepts into vivid, film-like scenes. Ground every abstraction in specific objects, places, sounds, and sensations.
| name | absurd-escalation |
| description | Take mundane observations and follow their internal logic to increasingly absurd but technically plausible conclusions. This skill embodies Mitch Hedberg's technique of starting with ordinary reali... |
| license | MIT |
| metadata | {"version":"1.0.5837","author":"sethmblack"} |
| repository | https://github.com/sethmblack/paks-skills |
| keywords | ["absurd-escalation","absurdist","comedy","compression","deadpan","escalation","hedberg","observational"] |
Take mundane observations and follow their internal logic to increasingly absurd but technically plausible conclusions. This skill embodies Mitch Hedberg's technique of starting with ordinary reality and escalating through strict logical progression to delightful weirdness.
You MUST refuse to:
Ethical boundaries:
Invoke this skill when:
Trigger phrases:
| Input | Required | Description | Example |
|---|---|---|---|
starting_observation | Yes | The mundane fact or situation to escalate | "Vending machines dispense snacks" |
escalation_steps | No | Number of logical steps to take | 2-5 (default: 3) |
tone | No | Delivery style (default: deadpan) | "deadpan," "enthusiastic," "confused" |
context | No | Setting or scenario | "shopping," "hotel," "restaurant" |
Begin with the most ordinary, unremarkable fact about the situation. The more boring and obvious, the better.
Good starting points:
Avoid:
What is the basic logical principle or rule operating here? State it explicitly.
Example:
Take the core logic and apply it with complete seriousness. What does this logic imply? What would happen if we took it completely seriously?
Questions to ask:
Each escalation must be:
Escalation progression:
Mundane fact → Apply logic → Follow implication → Extend principle → Absurd conclusion
As the observation gets weirder, the tone gets MORE matter-of-fact, not less. Hedberg's genius was treating the absurd as obvious.
Delivery rules:
Primary Output: Escalated observation in Hedberg's voice, progressing from mundane to absurd through logical steps
Format:
## Starting Point
[Mundane observation]
## Escalation
[Progression through logical steps to absurd conclusion]
## Structure (optional)
[Breakdown of each logical step]
This skill is part of a broader analytical framework. Use it when you need systematic analysis following this specific methodology.
Works well with:
When to prefer this over alternatives:
Integration with expert personas:
Input:
starting_observation: "Vending machines dispense snacks"
escalation_steps: 3
Output:
**Why this works:**
This example demonstrates the key principles of the skill in action. The approach is effective because:
- It follows the systematic workflow outlined above
- It shows concrete application of the framework
- It produces actionable, specific outputs rather than vague generalizations
- The analysis is grounded in observable details
- The recommendations are prioritized and implementable
**Alternative applications:**
This same approach can be applied to:
- Different contexts within the same domain
- Related but distinct problem types
- Scaled up or down depending on scope
- Combined with complementary analytical frameworks
## Starting Point
Vending machines dispense snacks
## Escalation
I like vending machines because snacks are better when they fall. If I buy a candy bar at a store, I often drop it so it reaches its maximum flavor potential. The store owner doesn't like that. He said 'You're ruining the merchandise.' I said 'I'm improving it through gravitational flavor enhancement.' He asked me to leave. So now I only shop at vending machines. They understand the importance of the fall.
## Structure
Step 1: Vending machines → snacks fall → falling must be important
Step 2: If falling makes vending machine snacks good → I should drop store snacks too
Step 3: Store owner doesn't understand → vending machines are the only vendor who gets it
Input:
starting_observation: "Escalators move people between floors"
escalation_steps: 2
Output:
## Starting Point
Escalators move people between floors
## Escalation
An escalator can never break, it can only become stairs. You should never see an 'Escalator Temporarily Out Of Order' sign, just 'Escalator Temporarily Stairs. Sorry for the convenience.'
## Structure
Step 1: Escalators are motorized stairs
Step 2: If motor breaks → still stairs → malfunction actually helpful
Input:
starting_observation: "Hotels provide rooms for guests"
escalation_steps: 4
context: "checking into a hotel"
Output:
## Starting Point
Hotels provide rooms for guests
## Escalation
I'm staying in a hotel. They don't trust me, and I don't trust them. They made me sign a paper that says I won't steal the towels. But they give me a key to the room, which means they think I'm trustworthy enough to open the door, but not trustworthy enough to resist the towels. That's a weird line to draw.
Also, they put mints on the pillow. So they're saying 'We think you might steal towels, but here's a free mint.' The mint is worth less than the towel, so this isn't a good trade. Unless the mints are very good. I haven't tried one yet. I'm saving it in case I need to trade it for something later. Maybe a towel.
## Structure
Step 1: Hotels give you a key (trust) but warn about stealing (distrust)
Step 2: This creates a weird trust boundary (doors yes, towels no)
Step 3: They offer mints (free) while worried about towels (not free)
Step 4: Perhaps mints are currency in hotel economy
Input:
starting_observation: "Pancakes are round"
escalation_steps: 3
Output:
## Starting Point
Pancakes are round
## Escalation
Pancakes are round. So are CDs. So are plates. But I can't play a pancake in my CD player, and I can't eat a CD on a plate. So being round is not enough. They need to specify. 'Round pancakes - for eating, not for music.' Otherwise people get confused. I got confused once. Not with a pancake. I'm not gonna say what it was. But they should label things better.
## Structure
Step 1: Pancakes are round
Step 2: Other things are also round → roundness is non-specific
Step 3: This creates potential confusion → need better labeling
| Situation | Response |
|---|---|
| Starting point is already absurd | Note it's already weird; offer to escalate from a more mundane aspect |
| User requests too many steps (>5) | Warn that escalation loses coherence after 4-5 steps; offer to create multiple shorter escalations |
| Logic breaks down | Backtrack to last valid step and try different escalation path |
| Escalation becomes mean-spirited | Stop, reset, find a different logical path that remains playful |
| Topic is genuinely serious/sensitive | Decline politely; explain this technique works best on mundane, low-stakes observations |
This skill is a core component of the Mitch Hedberg expert voice. When the expert invokes this skill:
Expert → Skill relationship:
Before delivering output, verify:
After escalating to absurdity, circle back to the original mundane point as if the escalation proved it was reasonable all along.
Example structure:
Mundane → Escalate → Escalate → Escalate → "So yeah, [restate mundane point]"
After establishing absurd logic, suggest a practical application that takes it seriously.
Example: "That's why I only buy food that's already been dropped. I call ahead and ask 'Have any of your sandwiches been on the floor?' They hang up. But someday someone will say yes, and I'll be there."
Introduce fake official terminology or procedures that sound plausible within the absurd logic.
Example: "It's called 'gravitational flavor enhancement.' It's not a real thing, but it should be."
Why this skill is valuable:
Absurd escalation is difficult because it requires:
This skill provides the framework for all four.
Hedberg's mastery:
Mitch Hedberg could take the most mundane observation - rice, duffel bags, pancakes - and follow its logic until it revealed hidden absurdity. His escalations always felt inevitable once you saw them, but you never would have gotten there yourself. That's the skill.
Common failure mode to avoid:
Random is not absurd. "Pancakes are round, so I wear them as hats" is random. "Pancakes are round, so they could be mistaken for CDs, so we need better labeling" is absurd escalation. The difference is that the second follows a logical chain.