# Clinical Absurdist > Apply medical precision, systematic analysis, and technical language to absurd or ridiculous situations, treating nonsense with diagnostic seriousness. - Skill: `sethmblack/clinical-absurdist` (Agent Skill) - Install (CLI): `npx skillmds add sethmblack/clinical-absurdist` - Raw SKILL.md: https://api.skillmd.com/api/skills/sethmblack/clinical-absurdist/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - License: MIT - Author: sethmblack (https://skillmd.com/u/sethmblack) - Updated: 2026-09-08 - Page: https://skillmd.com/skills/sethmblack/clinical-absurdist --- # Clinical Absurdist Skill Apply medical precision, systematic analysis, and technical language to absurd or ridiculous situations, treating nonsense with diagnostic seriousness. ## Purpose This skill applies Graham Chapman's medical training to comedy: diagnose absurd premises, dissect them systematically, deliver conclusions with clinical detachment. Technical expertise enhances rather than diminishes comedy when applied to ridiculous content. ## When to Use **Trigger Conditions:** - Technical or specialized content requiring comedic treatment - Systematic analysis needed for absurd situations - Medical, scientific, or analytical frameworks applicable - Complex problems that benefit from diagnostic approach - Situations requiring precision applied to nonsense - Expertise being applied to ridiculous subjects **Best For:** - Technical documentation with humor - Scientific or medical content - Problem analysis and diagnosis - Systematic deconstruction of absurdity - Expert commentary on ridiculous situations - Precision enhancing comedy ## Inputs | Input | Required | Description | |-------|----------|-------------| | input_data | Yes | The primary data or content to analyze | | context | No | Additional background or constraints (default: none) | | output_format | No | Preferred format for results (default: structured markdown) | ## Core Technique ### The Clinical Analysis Pattern 1. **Observe Symptoms** - Identify the absurd elements as if they're medical symptoms 2. **Conduct Systematic Examination** - Apply diagnostic framework to ridiculous premise 3. **Use Technical Vocabulary** - Employ precise, specialized language for nonsense 4. **Deliver Diagnosis** - State conclusions with clinical gravity 5. **Prescribe Treatment** - Recommend solutions with medical seriousness ### Key Principles - **Precision in word choice** - Medical exactness even for silly subjects - **Systematic thinking** - Logical framework applied to illogical content - **Clinical detachment** - Professional composure regardless of absurdity - **Technical language enhances** - Specialized vocabulary makes comedy funnier - **Diagnostic seriousness** - Treat ridiculous as worthy of expert analysis ## Outputs **Primary Output:** A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data. **Format:** ```markdown ## Analysis: [Topic] ### Key Findings - [Finding 1] - [Finding 2] - [Finding 3] ### Recommendations 1. [Action 1] 2. [Action 2] 3. [Action 3] ``` **Example output:** See the Example section below for a complete demonstration. ## Additional Notes **Best practices:** - Use this skill when the situation clearly matches its intended use cases - Combine with related skills for comprehensive analysis - Iterate on outputs if initial results don't fully meet requirements **Common variations:** - Adjust the depth of analysis based on available time and information - Scale the approach for different levels of complexity - Adapt the output format to audience needs **When to skip this skill:** - The situation doesn't match the core use cases - Simpler approaches would be more appropriate - Time constraints require faster methods ## Integration This skill is part of a broader analytical framework. Use it when you need systematic analysis following this specific methodology. **Works well with:** - Other analytical skills for comprehensive evaluation - Creative skills when generating solutions based on insights - Strategic planning skills when acting on recommendations **When to prefer this over alternatives:** - The situation matches this skill's specific use cases - You need the particular perspective this framework provides - Other approaches haven't yielded satisfactory results **Integration with expert personas:** - This skill can be invoked as part of a larger analysis workflow - Combine with domain-specific expertise for deeper insights - Use iteratively for complex, multi-faceted problems ## Error Handling | Situation | Response | |-----------|----------| | Insufficient input data | Request specific additional information needed for analysis | | Ambiguous requirements | Ask clarifying questions before proceeding | | Conflicting constraints | Highlight the conflicts and ask for prioritization | | Out of scope request | Explain the skill's boundaries and suggest alternatives | | Incomplete analysis | Acknowledge limitations and indicate what additional inputs would help | ## Examples ### Example 1: Ornithological Analysis **Input:** Questions about coconut transport **Output:** "The question of African versus European swallows requires systematic ornithological examination. First, establish baseline metrics: airspeed velocity under standard atmospheric conditions, wing loading ratios, and migratory patterns. The African swallow (*Hirundo rusticola*) presents distinct aerodynamic properties compared to the European variety (*Hirundo rustica*). Coconut transport capability depends on grip strength (lacking in passerines), flight endurance under additional mass loading, and behavioral disposition toward tropical fruit conveyance. My clinical assessment: coconut transport via swallow is physiologically implausible regardless of subspecies. However, tandem configuration utilizing length of line might provide viable alternative. Recommend further study before operational deployment." ### Example 2: Witch Diagnosis Protocol **Input:** Determining if someone is a witch **Output:** "Right. Systematic diagnostic approach. Hypothesis: Subject may be witch. Methodology: Comparative density analysis. Observation One: Witches burn. Observation Two: Wood burns. Logical deduction: Witches and wood share combustible properties, suggesting similar density. Observation Three: Wood floats. Observation Four: Ducks float. Transitive property: If wood equals duck in floatation, and witch equals wood in combustibility, then witch should equal duck in density. Diagnostic test: Weigh subject against duck. If mass equilibrium achieved, subject demonstrates duck-level density, confirming wood-equivalent properties, thereby indicating witch classification. This represents sound medical reasoning applied to supernatural determination. The science is settled." ### Example 3: Messiah Syndrome Differential **Input:** Evaluating messianic claims **Output:** "Patient presents with unwanted messianic attribution. Differential diagnosis must distinguish between (1) genuine divine status, (2) mistaken identity, or (3) mass delusion affecting observers rather than patient. Clinical indicators: Patient denies special status (suggestive of humility or accurate self-assessment). Followers demonstrate confirmation bias, interpreting ordinary actions as miraculous (classic symptom of collective ideation). Patient exhibits normal human responses: frustration, exasperation, desire for privacy (inconsistent with traditional divine affect). Assessment: Patient suffers not from delusion but from being trapped in others' delusional system. Treatment protocol: Repeated firm denial ('I'm not the Messiah'), logical argument ('I'm just a very naughty boy'), and if necessary, strategic withdrawal. Prognosis: Poor. Once crowd commits to diagnosis, evidence-based correction proves ineffective. Recommend managing symptoms rather than curing underlying cause." ## Application Process ### Step 1: Establish Clinical Framework - What type of expertise applies? (medical, scientific, technical) - What diagnostic or analytical method fits? - What specialized vocabulary is appropriate? ### Step 2: Observe and Document - What are the "symptoms" or elements to analyze? - What details merit systematic examination? - What can be measured, categorized, or classified? ### Step 3: Apply Systematic Analysis - What logical framework structures the examination? - What steps would an expert follow? - What technical precision enhances the analysis? ### Step 4: Deliver Clinical Diagnosis - What conclusion does systematic analysis support? - How would an expert state findings? - What treatment or recommendation follows? ### Step 5: Maintain Detachment - How does professional composure enhance comedy? - What tone suggests genuine expertise? - How does seriousness amplify absurdity? ## Workflow ### Step 1: Gather and Review Inputs Collect all relevant information: - Review the provided data and context - Identify key parameters and constraints - Clarify any ambiguities or missing information - Establish success criteria ### Step 2: Analyze the Situation Perform systematic analysis: - Identify patterns and relationships - Evaluate against established frameworks - Consider multiple perspectives - Document key findings ### Step 3: Generate Recommendations Create actionable outputs: - Synthesize insights from analysis - Prioritize recommendations by impact - Ensure recommendations are specific and measurable - Consider implementation feasibility ## Constraints **Do NOT Use When:** - Providing actual medical advice or diagnosis - Safety-critical information requiring clarity - Technical precision would obscure necessary understanding - Mockery of genuine medical conditions or disabilities - Real expertise needed, not comedic expertise **Boundaries:** - Apply precision to comedy, never compromise safety - Technical language enhances, never confuses - Clinical detachment serves humor, not coldness - Expertise is real (or convincingly presented), not mocked - Never make light of genuine suffering ## Integration with Other Skills **Pairs well with:** - `deadpan-authority` - Clinical expert with unshakeable authority - `dignified-chaos-navigation` - Systematic approach to chaotic situations - `matter-of-fact-revolutionary` - Technical analysis of taboo subjects - `collaborative-straight-man` - Expert analysis setting up others' reactions **Sequence:** 1. Establish expert authority (deadpan-authority) 2. Apply clinical analysis (clinical-absurdist) 3. Navigate complications (dignified-chaos-navigation) 4. Deliver controversial findings (matter-of-fact-revolutionary) ## Success Indicators You've successfully applied clinical-absurdist when: - Technical precision applied to ridiculous subject matter - Systematic analysis treats absurdity with diagnostic seriousness - Specialized vocabulary enhances rather than obscures comedy - Clinical detachment maintained throughout - Expertise feels genuine even when analyzing nonsense ## Attribution **Source:** Graham Chapman's medical degree (Emmanuel College, Cambridge) informed his comedy approach. Chapman qualified as doctor but chose comedy, bringing diagnostic thinking, systematic analysis, and clinical precision to absurdist performances. **Core Philosophy:** "A doctor diagnosing symptoms doesn't laugh at them. Similarly, apply medical precision to absurdity - the systematic seriousness makes the ridiculous even funnier."