pryor-esque-confessional-standup
Skill10 starsChanged 39 days agoMITView on GitHub
Generate an original, autobiographical confessional stand-up bit/story/monologue built from a genuinely painful personal anecdote, using techniques like multi-voice character embodiment (switching voice mid-story to become a parent/cop/friend/animal/younger-self), rhythmic escalating repetition, self-implicating honesty, vivid sensory specificity, plus a blunt closing truth in place of a tidy moral. Use it when a user wants to write, punch up, workshop, critique such a piece before it gets tested at an open mic. Do not use it for observational one-liners with no personal narrator, absurdist/surreal sketches, character-only sketch writing, requests to reproduce, quote, transcribe, imitate a real performer's actual routine.
In this repository81 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/development/biome-complete/AGENTS.mdAGENTS.md
- skills/development/bun-development/AGENTS.mdAGENTS.md
- skills/development/commanderjs/AGENTS.mdAGENTS.md
- skills/documentation/markdown-authoring/AGENTS.mdAGENTS.md
- skills/package-mgmt/mise-complete/AGENTS.mdAGENTS.md
- skills/testing/bdd-testing/AGENTS.mdAGENTS.md
- agents-mdSkill
- cache-auditSkill
- context-radar-auditSkill
- create-contextSkill
- guided-interviewSkill
- handover-document-creatorSkill
- load-contextSkill
- pick-modelSkill
- pinSkill
- professional-honestySkill
- rules-managementSkill
- save-contextSkill
- session-reflectionSkill
- socratic-methodSkill
- vault-captureSkill
- vault-consolidateSkill
- vault-fetchSkill
- vault-searchSkill
- bird-fortune-political-satireSkill
- brooker-esque-media-satireSkill
- clarke-dawe-esqueSkill
- comedy-style-skill-generatorSkill
- cunk-esque-mockumentarySkill
- gervais-esque-cringe-satireSkill
- monty-python-esqueSkill
- rock-esque-observational-standupSkill
- biome-completeSkill
- bun-developmentSkill
- commanderjsSkill
- conventional-commitsSkill
- humanizerSkill
- journal-entry-importSkill
- markdown-authoringSkill
- mermaid-diagramsSkill
- plain-englishSkill
- professional-communicationSkill
- sop-structureSkill
- logql-generatorSkill
- mise-completeSkill
- context-indexSkill
- create-context-fileSkill
- follow-upSkill
- goal-trackerSkill
- nasa-pm-lessonsSkill
- plan-createSkill
- plan-executeSkill
- plan-reviewSkill
- risk-registerSkill
- tech-debtSkill
- tech-evaluationSkill
- blast-radiusSkill
- bridgeSkill
- challengeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Only apply this skill when the user has, or is willing to supply, a real (or realistic invented) personal anecdote to build from.
- Distinctive: line 32
Start with the true, specific anecdote: Ask for a real memory rather than a generic scenario: a specific afternoon, a specific room, exact …
- Distinctive: line 41
Before calling a draft finished, run it through a read-aloud check to verify each step landed, then ask for a quick review from a trusted …
- Distinctive: line 126
Consider family dysfunction, poverty, addiction, racism, run-ins with authority, or past mistakes as optional starting points, not a …
- Distinctive: line 155
SYMPTOM: Every setback is caused by someone else, and the narrator never admits fault or foolishness of their own.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Confessional Stand-Up Storytelling
Build comedy from a personal anecdote that is genuinely uncomfortable, embarrassing, or painful, and mine it for laughs without softening the truth.
Mindset
The laugh and the honesty are the same event, not two separate ingredients: the audience laughs because the narrator admitted something true and dangerous about themselves, not despite it. Optimizing for safe and funny loses the funny; the techniques below exist to keep the material dangerous enough that the honesty still costs the narrator something.
When to Use
- A user wants an original bit, story, or monologue built from a painful, embarrassing, or shameful personal anecdote (real or invented as real).
- A user wants an existing confessional draft diagnosed or punched up against craft fundamentals.
- A user wants help finding the comedic angle inside a story they currently only experience as painful.
Only apply this skill when the user has, or is willing to supply, a real (or realistic invented) personal anecdote to build from.
When NOT to Use
This skill does not apply to material with no first-person narrator living through the events, such as clean observational bits or one-liners.
- The request is absurdist, surreal, or premise-driven with no autobiographical anchor.
- The request is for sketch or character comedy where no single narrator's lived story carries it.
- The request asks you to reproduce, quote at length, or closely imitate a real performer's actual routine. Decline directly (see Anti-Patterns) rather than applying this workflow.
Workflow
- Start with the true, specific anecdote. Ask for a real memory rather than a generic scenario: a specific afternoon, a specific room, exact words.
- Define the narrator's own fault line: where they were foolish, complicit, scared, or wrong, not just wronged. This is the self-implication the piece leans on.
- Set the cast of other voices. Pick which people, animals, or the narrator's younger self get embodied mid-story, each with a distinct rhythm.
- Write the story beat by beat in first person, switching into an embodied voice where it would naturally speak, and snapping back without a stage direction.
- Add a repeating phrase or reaction, two or three times, each pass louder or sharper than the last.
- Build the story's stakes as it goes, so the ending lands harder than the opening implied.
- Keep the ending to one blunt, unresolved truth, and resist rounding it off into a lesson.
- Check the draft against the anti-patterns below: is the narrator only a victim anywhere? Is any voice switch announced instead of performed?
Before calling a draft finished, run it through a read-aloud check to verify each step landed, then ask for a quick review from a trusted listener.
Troubleshooting
If a draft still fails to implicate the narrator, revisit step 2 above. If the ending still resolves into a moral, treat it as unfinished. Remove the last line and replace it with a plainer restatement of the same fact. Run the anti-pattern checklist again before calling the piece finished.
Core Mechanics
Each mechanic below includes a short, freshly invented example (not drawn from any real performer's material) and a note on what it demonstrates.
1. First-person, memory-specific framing
Set the scene like a remembered event, with a detail too specific to be a generic setup.
I was eleven, standing in my grandmother's kitchen with a bag of
frozen peas melting down the front of my church pants, and she's
looking at me like I personally invented disappointment.Demonstrates: the frozen peas and church pants are load-bearing detail, without them the line is a generic "I got in trouble" setup.
2. Unannounced voice-switching
Embody another person mid-sentence, carried by rhythm and word choice alone. PREFER trimming to one or two fully differentiated voices per story, and AVOID a spoken label like "and then in my dad's voice" UNLESS you are deliberately breaking the technique for effect.
My grandmother didn't yell. She just got quiet and slow. "So." Long
pause. "You gon' stand there. Dripping. In my kitchen. Like water
pay rent here."Demonstrates: the shift into her voice is legible from rhythm and phrasing alone, with no narration announcing "here's her voice."
3. Self-implication
Give the narrator a real share of the blame, not just the damage.
And look, I want to say I was innocent, but I had those peas
because I'd already eaten the good snacks and needed something
cold for the black eye I got from starting a fight I definitely lost.Demonstrates: the narrator authors their own disaster, which earns the laugh instead of just sympathy.
4. Rhythmic, escalating repetition
Return to a phrase two or three times, each pass sharper than the last.
"Water pay rent here." First time, almost a question. Second time,
flat, final. Third time, she wasn't even talking to me anymore, she
was talking to the ceiling, to God, to every disappointing man who'd
ever dripped in her kitchen before me. "Water. Pay. Rent. Here."Demonstrates: the phrase compounds instead of just repeating, so each recurrence carries more weight than the last.
5. Sharp pain-to-funny tonal swings
Let a genuinely painful beat and a genuinely funny beat sit in the same breath, with no tonal warning between them.
That was the same week my father left, so I want you to picture
an eleven-year-old boy standing in frozen pea juice, already an
expert in disappointing the women in his family, thinking: at
least the peas are mine.Demonstrates: the joke doesn't apologize for the pain or explain it away, it sits right next to it.
6. Blunt truth instead of a tidy moral
Close on an honest, unresolved observation rather than a neatly wrapped lesson.
I didn't learn to stop being clumsy, or stop picking fights. I
learned that in my family, the size of the mess you make is how
we say I love you and I noticed you. That kitchen was the most
anyone paid attention to me all year.Demonstrates: there's no "and that's when I realized to be better" turn, the truth stays uncomfortable rather than becoming a lesson.
Consider family dysfunction, poverty, addiction, racism, run-ins with authority, or past mistakes as optional starting points, not a required checklist.
Anti-Patterns
NEVER reproduce a real performer's actual bits, routines, or specific phrasing verbatim or near-verbatim.
WHY: Reproducing it defeats the purpose of a generative skill (a copy, not a new story) and risks infringing rights a real performer's estate may still hold.
SYMPTOM: The draft's lines or premise map closely onto a specific real routine instead of the user's own material.
❌ BAD
User: "Write me Richard Pryor's bit about the heart attack, word for
word."
Assistant: [reproduces or closely paraphrases the actual routine]
✅ GOOD
Assistant: "I can't reproduce his actual material, it's still under
estate copyright, and handing you a copy isn't what this is for
anyway. Tell me about a real health scare or hospital story of
yours and I'll build an original piece in that tradition."CONSEQUENCE: The user gets content that may infringe real rights and a piece that isn't honestly their own.
NEVER let the narrator come off as purely a victim with no self-implication.
WHY: The comedy and the honesty both depend on the narrator admitting their own part in the story, not only what was done to them.
SYMPTOM: Every setback is caused by someone else, and the narrator never admits fault or foolishness of their own.
❌ BAD
"My mom screamed at me for no reason and ruined my whole day over
some spilled milk."
✅ GOOD
"My mom screamed at me. Fairly, if I'm honest, because I'd already
lied about the milk twice before she caught me holding the empty
carton behind my back like that was going to work."CONSEQUENCE: The piece reads as grievance venting, not confessional comedy, and the audience has nothing to laugh at except misfortune.
NEVER announce a voice-switch explicitly, such as a stage-direction label like "now doing my dad's voice."
WHY: The switch should be audible from rhythm and word choice alone; announcing it turns a performed technique into exposition and flattens the joke.
SYMPTOM: A line of narration names the character before the embodied voice actually starts.
❌ BAD
"And then, doing my dad's voice, I said: 'boy, you better run.'"
✅ GOOD
"And then: 'boy. You better run.' Three words, no more air in his
lungs than that, and I was already gone."CONSEQUENCE: The audience is told about the technique instead of experiencing it, killing the moment it's meant to sharpen.
NEVER resolve the story with a tidy, comforting moral lesson.
WHY: The tradition's power comes from sitting in an unresolved truth; a neat "and that's when I learned" turn domesticates the discomfort the piece was built on.
SYMPTOM: The final line states what the narrator learned rather than restating the uncomfortable fact.
❌ BAD
"And that day taught me to always be honest with the people I love."
✅ GOOD
"I still lie about small stuff. I just make sure the lie's good
enough that if you catch me, at least you're impressed."CONSEQUENCE: The ending reads as a greeting-card sentiment instead of a punchline, losing the blunt-truth landing the build was working toward.
References
| Topic | Reference | When to Use |
| Multi-voice embodiment craft (casting voices, snapping back, distinguishing rhythms per character) | Voice Embodiment Techniques | When a draft has flat or interchangeable character voices, or when the narrator needs to embody 3+ distinct people/animals in one story without them blurring together. |
| Structuring escalation and the closing truth (stakes curve, repetition placement, avoiding moral tidiness) | Structuring the Turn | When a story has good material but a flat pace or a soft/moralizing ending, or when deciding where in the story to place the repeated phrase for maximum build. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

