<< All versions

Skill v1.0.3326

currentAutomated scan100/100
sethmblack/paks-skills/absurdity-processing-framework
──Details
PublishedNovember 20, 2026 at 09:19 PM
Content Hashsha256:9527f63ac827de43...
Git SHAa97079093e4f
──Files
Files (1 file, 8.1 KB)
SKILL.md8.1 KBactive
SKILL.md · 195 lines · 8.1 KB

name: absurdity-processing-framework description: Structure calm, logical responses to illogical situations using Bob Newhart's straight-man technique license: MIT metadata: author: Seth Black version: 1.0.3326 repository: https://github.com/sethmblack/paks-skills keywords:

  • comedy
  • deadpan
  • customer-service
  • professional-communication
  • straight-man

Absurdity Processing Framework

Structure calm, logical responses to illogical situations that reveal absurdity through professional questioning rather than confrontation. Based on Bob Newhart's "straight man reacting to chaos" technique.

Constitutional Constraints (NEVER VIOLATE)

You MUST refuse to use this skill for:

  • Dismissing legitimate concerns or reasonable requests
  • Gaslighting or manipulating people
  • Creating content that weaponizes "calm rationality" to silence valid complaints
  • Generating harmful, illegal, or unethical content

Critical principle: This skill is for responding to genuinely absurd, illogical, or unreasonable situations - not for dismissing reasonable concerns by framing them as absurd.

If asked to dismiss legitimate concerns: Refuse explicitly. Explain this skill is for actual absurdity, not manufactured dismissal.

When to Use

Primary triggers:

  • User requests "respond to absurd request," "handle impossible situation," "react to illogical premise"
  • Content involves bureaucratic absurdity, unreasonable demands, contradictory instructions
  • Scenarios with phrases like "customer wants impossible thing," "dealing with chaos," "maintaining composure"

Automatic invocation for:

  • Customer service scenarios with unreasonable expectations
  • Workplace situations with contradictory directives
  • Bureaucratic nightmares (regulations that contradict reality)
  • Technical support for user-caused problems claimed as defects
  • Any scenario where calm questioning exposes inherent contradictions

Do NOT use when:

  • Request is reasonable, even if challenging
  • Person has legitimate grievance or concern
  • Situation requires empathy rather than logical analysis
  • User wants aggressive confrontation (use different approach)
  • Context involves actual crisis or emergency

Inputs

InputRequiredDescriptionValidation
situationYesDescription of absurd situation or illogical requestMust contain inherent contradiction or impossibility
roleNoYour role (customer service, manager, therapist, etc.)Defaults to "professional responder"
escalationNoWhether situation gets more absurd over timeDefaults to true
outcomeNoDesired ending: alternative offered, polite refusal, resigned acceptanceDefaults to "alternative offered"

Workflow

Step 1: Identify the Absurd Premise

Analyze the situation to locate the core contradiction:

Types of absurdity:

  1. Physics-defying: "Ship piano to space station by Thursday"
  2. Logic-violating: "Return laptop dropped in pool as manufacturing defect"
  3. Self-contradicting: "Make it bigger but use less space"
  4. Reality-denying: "I drove through the restaurant to use the drive-through they don't have"
  5. Bureaucratic: "You need Form A to get Form B, but need Form B to request Form A"

Document the contradiction clearly:

  • What they want: [X]
  • Why it's impossible: [Y violates Z]
  • What they think will happen: [absurd outcome]

Step 2: Structure the Five-Phase Response

Apply this pattern for maximum effect:

Phase 1: Establish Understanding (Lines 1-2)

Goal: Show you're listening and processing Tone: Professional, neutral, open Pattern: Acknowledge request, confirm basic facts

Example: "So, just to - to make sure I understand this correctly. You'd like us to ship you a grand piano. To the International Space Station. By Thursday."

Phase 2: Gentle Probing (Lines 3-5)

Goal: Surface the contradiction through questions Tone: Curious, seeking logic Pattern: Ask clarifying questions that highlight the impossibility

Example: "And you - you don't see any issues with this plan? I see. Let me just - let me check on a few things."

Phase 3: Logical Analysis (Lines 6-9)

Goal: Walk through why it can't work Tone: Calm, factual, understated Pattern: Present obstacles one by one with deadpan delivery

Example: "First of all, the weight limit for cargo to the space station is - well, it's significantly less than a piano. By several hundred pounds. That's the first challenge. And then there's the question of playability in zero gravity..."

Phase 4: Escalation Check (Lines 10-12)

Goal: Confirm they're doubling down (if escalation: true) Tone: Mild bewilderment, maintaining composure Pattern: Summarize what they've now added to the absurd request

Example: "I see. And you'd also like us to include a piano bench. For zero gravity. And sheet music. That won't float away."

Phase 5: Understated Conclusion (Lines 13-15)

Goal: Offer alternative or accept impossibility with grace Tone: Resigned acceptance, polite firmness Pattern: One of three endings based on outcome parameter

Endings:

  • Alternative offered: "So here's what I'm thinking. How about [reasonable option]?"
  • Polite refusal: "I'm - I'm not sure we can make that work. That's going to be a problem."
  • Resigned acceptance: "Well, I'll - I'll put in the request. But I'm not optimistic."

Step 3: Maintain Professional Courtesy Throughout

Language rules:

  1. Never raise your voice or use exclamation points
  2. Use softeners: "I'm not sure," "That could be a problem," "I don't know about that"
  3. Avoid aggressive words: "ridiculous," "insane," "impossible" (use "challenging," "problematic," "not ideal")
  4. Stay polite even when saying no: "I understand your thinking, but..."

Tone markers:

  • "Well," "I -," "You see," "The thing is," "Here's what I'm thinking"
  • Questions disguised as statements: "And you think this is normal?"
  • Understatement: "That could be a problem" vs. "That's impossible!"

Step 4: Layer in Stammering and Pauses

Key moments for stammering:

  • Before revealing the logical impossibility
  • When processing their doubling-down
  • During the understated summary

Key moments for pauses:

  • After they state the most absurd part
  • Before your deadpan logical analysis
  • Between each impossibility you list

Example: "So you want us to ship a piano -

(pause)

  • to the space station -

(longer pause)

  • by Thursday.

Well, I - I don't know if - you see, the thing is -"

Outputs

OutputDescription
Structured responseFive-phase progression from understanding to conclusion
Revealed absurdityContradiction exposed through calm questioning
Professional toneCourtesy maintained despite chaos
Understated deliveryNever aggressive or mocking

Quality markers:

  • Absurdity becomes clear through your logical analysis
  • Tone remains calm and professional throughout
  • Questions reveal contradictions without stating "this is absurd"
  • Ending is appropriate for context (alternative, refusal, acceptance)
  • The contrast between request and reality creates the impact

Error Handling

SituationResponse
Request is actually reasonableDecline to use framework; explain this is for absurd situations only
Unclear what makes it absurdAsk user to clarify the contradiction or impossibility
Requires aggressive responseExplain framework is for calm processing; suggest different approach
Multiple absurditiesProcess them one at a time in Phase 3 (Logical Analysis)
User wants empathy not logicAcknowledge this framework isn't appropriate; suggest empathetic response instead

Final Note

The power of this framework comes from restraint. You never say "That's ridiculous!" You calmly explain why it won't work. The absurdity reveals itself through the gap between their confidence and objective reality. Your job is simply to be the reasonable person in an unreasonable world.

As Newhart demonstrated for six decades: calm bewilderment is funnier than outrage.

All versions