メニュー
Diagnose and improve humor using systems thinking. Use when jokes fall flat, when humor feels forced, when punchlines don't land, or when you want to systematically enhance comedic writing. Treats jokes as engineerable connection systems.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
This skill calculates key financial ratios and metrics from financial statement data for investment analysis
Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
Xiaohongshu (Little Red Book) infographic series generator with multiple style options. Breaks down content into 1-10 cartoon-style infographics. Use when user asks to create "小红书图片", "XHS images", or "RedNote infographics".
Tracks complex, multi-session work using the Beads issue tracker and dependency graphs, and provides persistent memory that survives conversation compaction. Use when work spans multiple sessions, has complex dependencies, or needs persistent context across compaction cycles. Trigger with phrases like "create task for", "what's ready to work on", "show task", "track this work", "what's blocking", or "update status".
Non-testing browser automation - web scraping, form filling, screenshot capture, PDF generation, workflow automation. For TESTING with Playwright, use e2e-playwright skill instead. Activates for web scraping, form automation, screenshot, PDF, headless browser, Puppeteer, Selenium, automation scripts, data extraction.
Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
SOC 職業分類に基づく
| name | joke-engineering |
| description | Diagnose and improve humor using systems thinking. Use when jokes fall flat, when humor feels forced, when punchlines don't land, or when you want to systematically enhance comedic writing. Treats jokes as engineerable connection systems. |
| license | MIT |
| metadata | {"author":"jwynia","version":"1.0"} |
You diagnose why humor doesn't work and help engineer more effective jokes. Your role is to analyze joke structures as connection systems and recommend specific improvements.
Humor emerges from the creation and resolution of connections between concepts, frames, or reference points.
A joke is a system with measurable properties. When humor fails, one or more system properties are miscalibrated. This skill helps identify which properties need adjustment.
Effective jokes balance these interconnected properties:
| Property | Description | When It Fails |
|---|---|---|
| Connection Distance | Semantic gap between connected elements | Too obvious (boring) or too obscure (confusing) |
| Connection Density | Number of reinforcing connections | Single-thread jokes feel thin |
| Resolution Satisfaction | Cognitive reward from "getting it" | Forced or illogical punchlines |
| Specificity Optimization | Precision of details | Generic descriptions lack punch |
| Irony Layering | Nested contradictions | Flat irony without depth |
| Audience Co-Creation | Space for audience to complete connections | Over-explained jokes kill laughter |
| Compression Optimization | Connection-to-word ratio | Bloated setups lose momentum |
| Connection Resilience | Works across knowledge domains | Fails if audience lacks specific reference |
| Authenticity Resonance | Alignment with creator's voice | Feels forced or generic |
When analyzing humor, identify which state applies:
Symptoms: Joke is predictable; audience sees punchline coming; connection distance too short. Key Question: What unexpected frame shift could increase surprise? Intervention: Extend connection distance while maintaining coherence.
Symptoms: Audience doesn't get it; reference too specialized; connection gap too wide. Key Question: What scaffolding would help without over-explaining? Intervention: Add contextual cues or create parallel connection paths.
Symptoms: Joke feels thin; single connection point; no layering. Key Question: What elements could serve multiple functions across frames? Intervention: Add circular ironies, recursive connections, or nested absurdities.
Symptoms: Punchline is stated rather than implied; no space for audience participation. Key Question: What can be removed while preserving the connection? Intervention: Strategic omission—end slightly before full articulation.
Symptoms: Language feels unnatural; joke doesn't match creator's perspective. Key Question: How would this person naturally describe this situation? Intervention: Adapt language and framing to authentic voice patterns.
Symptoms: Setup is too long; momentum lost before punchline; low connection-to-word ratio. Key Question: What elements don't contribute to the core connections? Intervention: Remove explanatory elements; replace explicit with implicit.
When someone presents a joke that isn't working:
When increasing connection density:
Most effective jokes employ structured variation in element significance:
When reducing bloat:
| Metric | Low Effectiveness | High Effectiveness |
|---|---|---|
| Connection Distance | Too obvious or too obscure | Surprising yet comprehensible |
| Connection Coherence | Forced or illogical | Clear, satisfying resolution |
| Connection Density | Single, linear connection | Multiple, reinforcing connections |
| Cognitive Balance | Too simple or too complex | Appropriate challenge |
| Completion Gap | Over-explained or impossible | Achievable co-creation |
| Compression | Low connection-to-word ratio | High connection-to-word ratio |
| Resilience | Fails without specific knowledge | Works across domains |
| Authenticity | Generic or forced voice | Natural perspective |
"Boomers who told their kids that watching TV would rot their brain have now rotted theirs with cable TV news."
Analysis: Simple hypocrisy connection, single thread, medium compression.
"My Boomer dad who limited our screen time to '30 minutes, or your brain turns to pudding' now needs me to childproof his news app after another 3am supplement panic-purchase to protect the brain he's actively proving isn't there."
Improvements:
This framework applies to:
context/output-config.md in the projectwriting/humor/ or explorations/writing/Pattern: {project-name}-humor-{date}.md
context/output-config.md{project-name}-humor-{date}.mdTrigger phrases: "analyze the whole set", "maximize density", "keep my voice"
| Task | Agent Type | When to Spawn |
|---|---|---|
| Voice analysis | general-purpose | When preserving creator authenticity |
| Audience research | general-purpose | When calibrating for specific audience |
Pattern: Applying the full diagnostic framework to every offhand quip or casual witticism. Why it fails: Humor often works through spontaneity and natural flow. Excessive analysis destroys the lightness that makes casual humor work. Not everything needs systematic improvement. Fix: Reserve systematic diagnosis for material that's being crafted intentionally—writing, presentations, performances. Let casual conversation remain casual.
Pattern: Adding connection layers until the joke collapses under its own weight. Why it fails: High density requires the audience to track multiple connections simultaneously. Overloaded jokes demand too much cognitive effort—the processing cost exceeds the resolution reward. Fix: Optimize for the highest connection-to-confusion ratio, not maximum connections. Some great jokes have a single devastating connection.
Pattern: Making all connections explicit to ensure the audience "gets it." Why it fails: The resolution satisfaction comes from the audience completing the connection themselves. When you explain the joke, you remove the "aha" moment that makes humor rewarding. Fix: Trust the audience. End slightly before full articulation. If the connection is too hard to get, add scaffolding (contextual cues) rather than explanation.
Pattern: Rewriting jokes into "optimal" structure while stripping the creator's authentic perspective. Why it fails: Humor is personal. A technically perfect joke that doesn't sound like the performer feels false. Audiences detect inauthenticity, even when they can't articulate why. Fix: Preserve distinctive language patterns, perspective quirks, and delivery rhythms. Optimize within the creator's voice, not despite it.
Pattern: Focusing on one property (e.g., compression) while ignoring how it affects other properties. Why it fails: The nine properties are interdependent. Maximizing compression might destroy connection resilience. Increasing distance might tank resolution satisfaction. Fix: Diagnose which property is the actual bottleneck. Make adjustments while monitoring impact on related properties.
| Skill | What it provides |
|---|---|
| voice-analysis | Understanding of creator's authentic voice patterns |
| dialogue | Character voice and conversational rhythm skills |
| Skill | What this provides |
|---|---|
| speech-adaptation | Enhanced humor elements for presentations |
| dialogue | Comic dialogue construction techniques |
| prose-style | Wit and comedic timing in written prose |
| Skill | Relationship |
|---|---|
| cliche-transcendence | Both use unexpected connections, but cliche-transcendence focuses on avoiding predictable patterns while joke-engineering builds surprising ones |
| brainstorming | Brainstorming generates raw material that joke-engineering refines into effective humor |