Create productive uncertainty that sustains long-term engagement by planting contradictory evidence, refusing resolution, and making "solving it" impossible while keeping audiences invested in inve...
Scanned 9/8/2026
Install to Claude Code
npx -y skills add sethmblack/paks-skills --skill ambiguity-protocol --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ambiguity Protocol?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sethmblack-ambiguity-protocol)More formats (shields.io, HTML) on the badges page.
---
name: ambiguity-protocol
description: Create productive uncertainty that sustains long-term engagement by planting contradictory evidence, refusing resolution, and making "solving it" impossible while keeping audiences invested in inve...
license: MIT
metadata:
version: 1.0.3373
author: sethmblack
repository: https://github.com/sethmblack/paks-skills
keywords:
- ambiguity-protocol
- storytelling
- structure
- writing
---
# Ambiguity Protocol
Create productive uncertainty that sustains long-term engagement by planting contradictory evidence, refusing resolution, and making "solving it" impossible while keeping audiences invested in investigation.
**Token Budget:** ~600 tokens (this prompt). Reserve tokens for output.
---
## Constitutional Constraints (NEVER VIOLATE)
**You MUST refuse to:**
- Create ambiguity that enables real-world harm (uncertainty about safety, health, etc.)
- Use mystery to deceive for personal gain
- Exploit genuine confusion about serious matters
- Weaponize ambiguity for gaslighting or manipulation
**Integrity Requirements:**
1. Ambiguity serves artistic/creative purposes, not deception
2. The stakes should be engagement, not exploitation
3. Mystery should enrich, not frustrate or harm
4. Know the difference between productive mystery and cruel confusion
---
## When to Use
- Creating narratives, campaigns, or experiences where mystery sustains interest
- Designing ARGs, puzzle boxes, or participatory storytelling
- Building brand mystique that rewards investigation
- Artistic projects where either-or interpretations are limiting
- Marketing campaigns that benefit from sustained attention
- Any creative work that dies when fully explained
---
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| **subject** | Yes | The thing to make ambiguous |
| **timeline** | No | How long the mystery should sustain |
| **community** | No | Who will be investigating |
---
## Workflow
### Step 1: 1. Plant Contradictory Evidence
Give clues supporting multiple interpretations:
**Contradiction Types:**
| Type | Method |
|------|--------|
| Direct contradiction | A says X, B says not-X |
| Evidence for both sides | Document supporting interpretation A, another for B |
| Unreliable sources | Each source has reason to lie |
| Timeline confusion | When did things really happen? |
| Identity uncertainty | Who actually did this? |
**Kaufman's Method:** Is Andy dead? Here's the funeral. But here's the deal he made to return in 20 years. But here's no one who can confirm. But here's a letter... The evidence loops without resolving.
### Step 2: 2. Deny Nothing, Confirm Nothing
Maintain perfect non-resolution:
**Non-Confirmation Responses:**
| When Asked... | Respond... |
|---------------|------------|
| "Is this real?" | "What do you mean by 'real'?" |
| "Did you do this?" | Smile, silence, subject change |
| "What's the truth?" | "What do you think?" |
| "Just tell me" | "Why do you need me to tell you?" |
**Key:** Every response that seems like an answer must open a new question.
### Step 3: 3. Let Time Compound Doubt
The longer it goes, the more interesting it becomes:
**Time Amplification:**
- Early: "This is confusing"
- Middle: "Nobody knows the truth"
- Late: "The mystery itself is the point"
- Permanent: "We may never know"
**Kaufman's Principle:** After enough time, the question of whether it's real becomes more interesting than any answer could be.
### Step 4: 4. Make "Solving It" Impossible
No definitive answer exists—by design:
**Impossibility Architecture:**
- Remove or obscure the "real" answer
- Make multiple answers equally supported
- Ensure any "proof" can be questioned
- Build the ambiguity into structure, not just secrecy
**Template:** If a definitive answer could exist, you've failed. The ambiguity must be structural, not just hidden.
### Step 5: 5. Engage the Mystery-Solvers
Their investigation is part of the art:
**Community Engagement:**
- Drop new ambiguous clues for investigators
- Let their theories become part of the mythology
- Neither validate nor invalidate their work
- Their conversations extend the piece
**Kaufman's Legacy:** Entire communities debate whether Andy Kaufman faked his death. Their debate IS the art continuing.
---
## Outputs
Format the output as:
```markdown
## Ambiguity Protocol: [Subject]
### Contradictory Evidence Map
| Interpretation A | Interpretation B |
|------------------|------------------|
| Evidence: [clue] | Counter-evidence: [clue] |
| Source: [who/what] | Source: [who/what] |
### Non-Confirmation Responses
| Question | Response That Opens New Questions |
|----------|-----------------------------------|
| [expected question] | [non-resolving response] |
### Time Compound Strategy
**Week 1:** [initial mystery state]
**Month 1:** [how confusion deepens]
**Year 1:** [what the mystery becomes]
**Permanent State:** [the question that will never be answered]
### Solution Prevention
**Why Solving Is Impossible:**
[Structural reason no definitive answer can emerge]
### Investigator Engagement
**Breadcrumbs to Drop:** [ambiguous clues for active investigators]
**Theories to Neither Confirm Nor Deny:** [let them build mythology]
```
---
## Error Handling
| Situation | Response |
|-----------|----------|
| Someone claims definitive proof | Plant counter-evidence; acknowledge their work without confirming |
| Community loses interest | Drop new ambiguous clue |
| Ambiguity is causing real harm | Clarify what's necessary for safety; maintain mystery on artistic elements |
| You're asked point-blank | The character who knows doesn't exist; you genuinely don't have a "real" answer |
---
## Constraints
- Do not use this analysis as the sole basis for critical decisions
- Do not apply this framework to situations outside its intended scope
- Acknowledge that analysis is based on available data, which may be incomplete
- Honor the complexity of real-world situations that resist simple categorization
- Present findings with appropriate confidence levels
- Recognize the limits of the methodology
## 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
## Example
**Input:** "Design ambiguity protocol for a podcast that may or may not be fiction"
**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
## Ambiguity Protocol: "The Residency" Podcast
### Contradictory Evidence Map
| It's Fiction | It's Real |
|--------------|-----------|
| Credits list writers | But many audio dramas don't credit actors |
| Events are too coincidental | Hospital records match (when checked) |
| Host never shows face | But provides verifiable employment history |
| "Based on true events" disclaimer | But refuses to specify what's true |
| Expert guest caught in contradiction | Expert is real person with real credentials |
### Non-Confirmation Responses
| Question | Response That Opens New Questions |
|----------|-----------------------------------|
| "Is this real?" | "What would change for you if you knew?" |
| "Are you an actor?" | "I'm a medical professional. Everything you've heard about me is true." |
| "Can you prove any of this?" | "Why would I need to prove it to you?" |
| "What's the truth?" | "I've told you what happened. The rest is yours." |
### Time Compound Strategy
**Week 1:** Listeners enjoy either as fiction or documentary
**Month 1:** Reddit debates emerge; no consensus forms
**Year 1:** "The Residency real or fake" becomes its own genre of content
**Permanent State:** The podcast that might be the most honest account of hospital work ever recorded—or might be the most elaborate fiction
### Solution Prevention
**Why Solving Is Impossible:**
The host genuinely exists as the person described. The hospital exists. Some events can be corroborated. Others cannot. The "fiction" disclaimer could be legal protection OR narrative device. There is no moment where "real" was separated from "fake"—they were interwoven from creation.
### Investigator Engagement
**Breadcrumbs to Drop:**
- Occasional verifiable details that reward research
- "Easter eggs" that could be production artifacts or real documentation
- A "deleted episode" that surfaces with different, contradictory details
**Theories to Neither Confirm Nor Deny:**
- "The host is a real doctor who adds fictional cases"
- "It's all real but legally can't say so"
- "The whole thing is performance art about medical narrative"
- "Multiple hosts use the same persona"
---
## Integration with Andy Kaufman Expert
This skill should be invoked when the Kaufman expert encounters:
- Requests to create lasting mysteries
- Projects that benefit from sustained investigation
- Campaigns where closure would diminish impact
- Any work where "the answer" matters less than "the question"
May combine with:
- **commitment-framework**: Maintain ambiguity while never breaking
- **hostile-performance**: Let audiences' desire for resolution be part of what's withheld
---
## Success Criteria
The skill is successfully applied when:
1. Evidence exists for multiple interpretations
2. No response confirms or denies definitively
3. Time deepens rather than resolves the mystery
4. Structural impossibility prevents "solving"
5. Investigator community becomes part of the art
6. The question outlives any attempt at answerIs this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!