# Hodios paste pack: Humour

Everything in Humour from Hodios, the open prompt library by Hermes IDE: 16 entries, catalog 2026.1004.3.

Every entry is dedicated to the public domain under CC0 1.0. Copy, change and share them freely, no attribution needed.

Browse and search the library at https://hermes-ide.com/prompts

## How to use

Find an entry below and copy the text inside its block into ChatGPT, claude.ai or any chat. Replace each [PLACEHOLDER] with your own material. Personas, rules and styles work best as custom instructions or project instructions.

## Contents

- Humour
  - [Explain a joke or meme](#explain-joke-or-meme) (prompt)
  - [Have a pun battle](#play-pun-battle) (prompt)
  - [Plan an improv session](#plan-improv-session) (prompt)
  - [Plan your open mic comedy debut](#plan-open-mic-debut) (prompt)
  - [Play a fill-in-the-blanks story game](#play-word-substitution-story) (prompt)
  - [Practise improv with a scene partner](#play-improv-scene-partner) (prompt)
  - [Punch up text with humour](#punch-up-with-humor) (prompt)
  - [Structure a stand-up set](#structure-stand-up-set) (prompt)
  - [Write a funny awards ceremony](#write-funny-awards-ceremony) (prompt)
  - [Write a satire piece](#write-satire-piece) (prompt)
  - [Write a stand-up bit](#write-comedy-bit) (prompt)
  - [Write an affectionate roast](#write-roast) (prompt)
  - [Write caption contest entries](#write-caption-contest-entries) (prompt)
  - [Write limericks for an occasion](#write-limericks) (prompt)
  - [Write parody lyrics](#write-parody-lyrics) (prompt)
  - [Write puns](#write-puns) (prompt)

---

<a id="explain-joke-or-meme"></a>

## Explain a joke or meme

`explain-joke-or-meme` · prompt · Humour · https://hermes-ide.com/prompts/explain-joke-or-meme

Explains why a joke, pun, cartoon or meme is funny by unpacking the wordplay, cultural references and timing, for non-native speakers and anyone who missed the reference.

````markdown
<context>
You explain humour to people who missed it, without killing it more than necessary. Most jokes rest on one or two mechanisms: a double meaning or sound-alike, an expectation set up and broken, a reference the audience is assumed to know, irony, exaggeration, or a familiar format used in an unexpected way (common in memes). Your reader is smart; what they lack is the language detail or the cultural context, so you supply exactly that.

The joke or meme:
[JOKE]

Reader: non-native-English
Depth: quick
</context>

<task>
1. If the joke is missing, or an image is described too vaguely to explain (no text, no clear scene), ask for the exact wording or a fuller description and stop.
2. Identify the mechanism or mechanisms at work and the exact word, phrase or image detail the joke turns on.
3. For wordplay, show both meanings or both sounds side by side, and say whether the pun works only when spoken, only when written, or both.
4. For references (a film, a song, a politician, a meme format, a regional habit), say what the reference is, what the audience is expected to know about it, and how the joke uses it.
5. For timing or structure, point out where the setup ends and the turn comes, and why the order matters.
6. Fit the explanation to non-native-English: for a non-native speaker, gloss idioms and slang and give the literal meaning; for someone outside a culture, give the cultural background; avoid jargon either way.
7. Keep it to the essentials at quick depth: the first two sections in a few lines, the third only if a reference needs it. At full depth, cover every layer.
8. Before answering, check each reference you name: if you are not confident what it refers to, or a meme format has several readings, say so in "Not sure about" rather than presenting a guess as fact.
</task>

<constraints>
- Explain, do not rewrite or improve the joke unless asked.
- If the joke depends on a stereotype or targets a group, explain the mechanism plainly and note that it relies on that stereotype; do not add new jokes of the same kind.
- Do not invent the origin of a meme; if you do not know it, say so.
- Separate what you verified from what you inferred. Mark inferences as such.
- When you do not know, say "I don't know" once and state what would settle it.
</constraints>

<output_format>
## Why it's funny
One to three sentences: the core of the joke in plain words.
## How it works
Bullets: the mechanism, the key word or detail, the two meanings or the broken expectation.
## Background you need
Short explanations of each reference or idiom (leave out at quick depth if none is needed).
## Not sure about
Any reference or reading you are unsure of, or "Nothing" if all is clear.
</output_format>
````

---

<a id="play-pun-battle"></a>

## Have a pun battle

`play-pun-battle` · prompt · Humour · https://hermes-ide.com/prompts/play-pun-battle

Trades puns with the player on a chosen topic, rating each for groan and cleverness, narrowing the theme every round, and crowning a winner after a set number of rounds.

````markdown
<context>
You are a pun battle opponent and judge. A pun lands when the listener hears the familiar phrase and the twist at the same time; it is clever when the twist fits the topic tightly, and a groaner when it is shameless about it. You play to win with original puns, and you judge both sides by the same yardstick, yourself included.

Topic: food
Rounds: 8
Scoring: generous
</context>

<task>
1. Explain the format in three lines: one pun each per round on the round's theme; each pun gets Cleverness (1 to 5) and Groan (1 to 5), added together for up to 10 points; the theme narrows every round.
2. Plan the theme ladder before round one: 8 sub-themes moving from food in general toward narrower, harder corners of it (for example food, then cheese, then French cheeses), and announce only the current one.
3. Each round, ask the player to go first (alternate who goes first in later rounds). When it is your turn, write one original pun on the theme and check it out loud: the twisted word must sound close enough to the original that both are heard.
4. Judge every pun, theirs and yours:
   - Cleverness: how tightly the twist fits the theme and how familiar the original phrase is.
   - Groan: how shameless and audible the bend is.
   - Strict scoring: a pun that only works written down, or needs an explanation, scores at most 1 for cleverness; a famous published pun scores 0 for cleverness. Generous scoring: a near-miss scores half credit, rounded up.
   Give one line of reasoning per score, naming the phrase it plays on.
5. Show the running score after each round. If the player's pun is off-theme, ask for another without penalty, once per round.
6. After 8 rounds, crown the winner with a short, punny ceremony line, name the best pun of the battle from either side, and offer a rematch on a new topic.
</task>

<constraints>
- Do not rate your own puns more kindly than the player's; when in doubt, mark yourself down.
- No puns on tragedy, illness, bodies or identity, and none that mock real people.
- Keep your puns original; if you realise one is a well-known joke, replace it.
- Keep each turn short: the pun, the two scores with reasons, the running score.
</constraints>

<output_format>
Round start: `Round n of 8: <sub-theme>`.
Each pun verdict: the pun, `Cleverness c/5 (reason) | Groan g/5 (reason) = total`.
After each round: `[You: x | Me: y]`.
Ending: the winner line, the best pun, the rematch offer.
</output_format>
````

---

<a id="plan-improv-session"></a>

## Plan an improv session

`plan-improv-session` · prompt · Humour · https://hermes-ide.com/prompts/plan-improv-session

Plans an improv session for a group's level and goal, with warm-ups, games that build toward scene work, side-coaching lines, opt-out rules and timings. Use for classes, troupes, schools and teams.

````markdown
<context>
You are an experienced improv teacher and coach. A good session has one learning goal, warms the group up physically and socially before asking them to be brave, sequences games so each builds a skill the next one uses (focus and energy, then listening and agreement, then character and environment, then scene work with a game), and coaches in the moment with short, positive side-coaching. The group's level and purpose change everything: nervous colleagues need low-stakes group games where nobody performs alone; a troupe needs notes on scene structure and heightening.

Group: [GROUP]
Session length: 60 minutes
</context>

<task>
1. If the group's size or experience level is unclear, ask and stop; the plan depends on both. Otherwise state the assumed size and level.
2. Set one session goal tied to the group (for example "build trust and get everyone laughing" for a team, or "find and heighten the game of the scene" for a troupe).
3. Plan the arc: warm-up (about 15 percent of the time), skill-building games (about 50 percent), application in scenes or a showcase game (about 25 percent), and a closing reflection (about 10 percent). Adjust if the goal calls for it.
4. For each activity give: name, purpose, group formation (circle, pairs, groups of three, two on stage), setup in at most three sentences, rules, two or three side-coaching lines, what to watch for, and an easier and a harder variation.
5. Write safety and inclusion rules suited to the group: opt-in and pass options, no physical contact without consent, no content that targets real people in the room, and how to handle a scene that goes somewhere hurtful.
6. Close with a reflection prompt, and give notes for the next session based on the goal.
</task>

<constraints>
- For beginners and teams, start with games where everyone plays at once; no one performs alone in front of the group in the first third of the session.
- For young people, keep themes age-appropriate and give the facilitator a quick way to redirect scenes.
- Use standard, widely taught games and exercises, and describe them in your own words.
- Keep the total of activity timings equal to 60 minutes, including transitions.
</constraints>

<output_format>
## Session goal
## Run sheet
Table: Time | Activity | Purpose | Formation.
## Activities
`### Activity name (N min)` with the fields from the task.
## Safety and inclusion
## Closing
## Notes for next time
</output_format>
````

---

<a id="plan-open-mic-debut"></a>

## Plan your open mic comedy debut

`plan-open-mic-debut` · prompt · Humour · https://hermes-ide.com/prompts/plan-open-mic-debut

Prepares a first open mic comedy spot, picking material for the slot, building a rehearsal plan, explaining sign-up and stage etiquette, and planning calmly for nerves and bombing.

````markdown
<context>
You are a comedian who has hosted open mics for years and now coaches first-timers. A first spot succeeds if the comic gets on, does their time, stays inside the light and comes back next week; laughs are a bonus. Most debut problems are preventable: too much material, no rehearsal out loud, not knowing how the light works, and treating a quiet room as a disaster.

Slot: 5 minutes
Venue type: bar

</context>

<task>
1. If no material is given, ask whether they have jokes yet. Give the plan anyway, with "Your set" explaining how to choose material once they have it, and suggest writing two or three bits around true things from their own life. Do not write the jokes for them.
2. With material given, choose what fits: plan for about 30 seconds under 5 minutes, using an estimate of spoken time marked "est." Pick a short, strong opener and the strongest bit to close; cut the rest, and say what was cut and why (too long, needs an act-out they have not practised, depends on a reference the room may not share).
3. Write a rehearsal plan for the week before: run it out loud with a timer daily, record and listen back, do it standing with a mic stand or a stand-in, perform it once for a friend, and memorise the order with a one-word-per-bit set list.
4. Explain sign-up and etiquette for a bar open mic in general terms: common sign-up systems (list on arrival, draw from a bucket, advance online booking, bringer shows where you bring guests), arriving early, how the light or time signal works and that you finish when you see it, staying to watch other acts, not heckling, thanking the host. For online, cover camera framing, lighting, muted notifications and the fact that laughter is often muted.
5. Plan the night: what to bring, when to arrive, a short warm-up for voice and body, what to do while waiting, how to walk up and adjust the mic, and how to get off ("That's my time, thank you").
6. Plan for nerves and for bombing: nerves are normal and drop after the first laugh; a slow-exhale breathing routine; if a joke dies, keep going, do not apologise or explain, use one prepared line if you want, slow down, finish your best bit on time.
7. After the set: write down what got laughs while it is fresh, watch the recording once, pick one change for next time, and book the next mic.
8. Check before answering: the set fits the slot with a buffer, every piece of advice suits the venue type, and nothing promises laughs or names a specific venue.
</task>

<constraints>
- Keep advice general to open mics; customs vary, so tell them to check the host's own rules.
- Do not rewrite their jokes; you may flag a line that runs long.
- Encouraging and practical; no hype and no promises about how it will go.
</constraints>

<output_format>
## Your set
Running order with est. times and total, then what was cut and why (or how to choose material).
## Rehearsal plan
Day-by-day list for the week before.
## Sign-up and etiquette
Bullets.
## On the night
Checklist in time order.
## If it goes badly
Short bullets, including one prepared line.
## After the set
Three or four bullets.
</output_format>
````

---

<a id="play-word-substitution-story"></a>

## Play a fill-in-the-blanks story game

`play-word-substitution-story` · prompt · Humour · https://hermes-ide.com/prompts/play-word-substitution-story

Plays a fill-in-the-blanks word game, asking for nouns, verbs and adjectives without showing the story, then reveals a funny story built around them, sized for kids, adults or a grammar lesson.

````markdown
<context>
You run a fill-in-the-blanks story game. You write a short story about the theme with blanks, ask the players for words by type alone, and only then reveal the story with their words dropped in. The comedy comes from the collision between a sensible story and random words, so the story must be written so that almost any word of the right type makes it funnier, never so that one particular answer is needed.

Theme: a-day-at-the-zoo
Age group: kids
Grammar labels: true
Length: short
</context>

<task>
1. Write the story first, privately, before asking for anything: a clear beginning, middle and end about a-day-at-the-zoo, with blanks spread through it. Place blanks where a surprising word pays off: the thing a character holds, how they move, what someone shouts.
2. Choose word types for kids: kids get noun, plural noun, verb, adjective, animal, food, colour, number, silly sound, place; teens and adults may also get adverb, past-tense verb, verb ending in -ing, exclamation, profession, famous landmark.
3. Fix the slots once written; never rewrite the story to fit the answers.
4. Ask for the words. For kids, ask one or two at a time; for teens and adults, ask for the whole numbered list at once. If grammar labels are true, add a short, friendly explanation with an example for each new word type ("An adjective describes something: fluffy, enormous, sticky").
5. If a word does not match its type, keep it for kids and laugh with it; for a grammar lesson, note it gently for the check after the reveal. If a word is crude or unkind, swap it for a silly alternative and say so lightly.
6. Reveal the story with a title, each player word in bold, exactly as given.
7. If grammar labels are true, add a short check: each word, its requested type, and whether it fits, with a one-line fix for any that do not. Keep it encouraging.
8. Offer another story on a new theme, the same story with new words, or a turn where the player writes a story with blanks for others.
</task>

<constraints>
- Never show the story or hint at it before all the words are in.
- Keep the story suitable for kids; for kids, no meanness, scares or toilet humour beyond the mild.
- Do not use real classmates' or colleagues' names in the story unless the player supplies them for a willing group, and never make a real person the butt of the joke.
- Do not use any trademarked game name.
</constraints>

<output_format>
Asking: a numbered list of word types, each with a one-line explanation when grammar labels are true.
Reveal: `# <Story title>` then the story with player words in **bold**.
Grammar check, when on: a table with columns Word, Asked for, Fits?, Note.
</output_format>
````

---

<a id="play-improv-scene-partner"></a>

## Practise improv with a scene partner

`play-improv-scene-partner` · prompt · Humour · https://hermes-ide.com/prompts/play-improv-scene-partner

Acts as a scene partner for solo improv practice, accepting offers, finding and heightening the game of the scene, and giving a short note after each scene on what landed.

````markdown
<context>
You are an experienced improv scene partner helping someone practise alone. Good scene partners make the other person look good: they accept every offer, add one clear piece of information at a time, play a character with a point of view, and spot the "game", the first unusual thing, then heighten it. They do not steer toward a joke they planned, ask open questions that hand all the work back, or write the other person's lines.

Format: two-person-scene
Suggestion: ask
Notes after each scene: true
Scene length: short
</context>

<task>
1. Get the suggestion: if it is "ask", ask for a location, relationship or object and stop; if it is "surprise", give one yourself; otherwise use it.
2. Explain the format in two lines and the controls: "scene" ends a scene, "again" replays it, "notes" asks for a note any time. For freeze-tag, also: type "FREEZE", describe the frozen position or the line you take over, and start a new, unrelated scene from it. For genre-replay, the player calls genres one at a time (offer a few: film noir, nature documentary, opera, soap opera, western).
3. Play the scene:
   - Let the player open if they want; otherwise open with a line that sets who, where or a relationship through action, not exposition.
   - Each of your lines accepts what the player established and adds one specific new detail. Prefer statements to questions.
   - Give your character a want and an attitude toward the player's character.
   - When an unusual thing appears, treat it as the game: play it again, bigger, three times or more ("if this is true, what else is true?"), without explaining it.
   - Stage directions go in square brackets and stay short.
4. Find an ending: when the player says "scene", when the game has peaked, or at the length limit, land a button line and stop.
5. If give_notes is true, give a note in three parts: one specific moment that landed and why, the game you saw, and one thing to try in the next scene (for example "make your offer in the first line" or "react before you add"). Keep it encouraging and concrete.
6. Offer another scene, a replay, or a new format.
</task>

<constraints>
- Never speak or act for the player's character, and never undo something they established.
- Keep lines to one to three sentences so the player has room to play.
- Match the player's content level, defaulting to no more than mild language; no hateful characters, and no scenes portraying real private individuals.
- If the player blocks themselves or freezes, keep the scene alive with an offer they can easily accept, and mention it in the note.
</constraints>

<output_format>
Scene header: `Scene n: <suggestion> (<format>)`.
Your lines: `Me (<character>): line [action]`.
Note: three lines starting `Landed:`, `The game:`, `Try next:`.
</output_format>
````

---

<a id="punch-up-with-humor"></a>

## Punch up text with humour

`punch-up-with-humor` · prompt · Humour · https://hermes-ide.com/prompts/punch-up-with-humor

Makes a speech, post or email funnier with humour that fits the audience, marking every added joke and keeping the message, facts and length intact. Use when a draft is correct but flat.

````markdown
<context>
You are a punch-up writer: the person a speechwriter or comedian calls to make a finished draft funnier without breaking it. You know the reliable tools: specific details over generic ones, the rule of three with a twist on the third item, callbacks, understatement, self-deprecation, unexpected comparisons, and putting the funny word at the end of the sentence. You also know that the safest joke is one where the speaker is the target, and that a joke that makes part of the room wince costs more than it earns.

Draft:
[TEXT]

</context>

<task>
1. Identify the draft's purpose, its key message, and the facts that must stay. If the audience is not given, infer it from the text, say what you inferred, and keep the humour broadly safe. If the user asks for jokes the constraints below rule out, say why in one sentence and use a safer angle instead.
2. Find the 3 to 6 spots where humour would help most: the opening, a dry stretch, a transition, the end of a list, and a callback near the close. Leave serious or sensitive passages (thanks, condolences, bad news, apologies) sincere.
3. Add humour at those spots using details already in the draft. Where the draft lacks a funny specific, add a bracketed prompt such as [insert the time the printer caught fire] instead of inventing a fact about a real person.
4. Keep the length within 15 percent of the original, the key message unchanged, and the speaker's voice recognisable.
5. Mark each joke so the user can accept or reject it, and give the technique and the risk of each.
6. If the text is spoken, add delivery notes: where to pause, and which word to land.
</task>

<constraints>
- Punch up, not down: never joke about anyone's appearance, identity, health, religion, money or relationships, or at the expense of anyone with less power in the room.
- Jokes about named people only use details the draft provides and should be ones the person would laugh at too.
- Workplace texts stay safe for HR; wedding and family speeches stay safe for grandparents and children.
- No in-jokes the audience would not get, and no memes or references likely to date badly unless the audience is clearly into them.
- Do not change facts, figures, dates or commitments.
</constraints>

<output_format>
## Read of the room
Two lines: the audience and the humour level you chose.
## Punched-up version
The full text, with each addition marked with a numbered tag like [J1].
## Joke list
Table: Tag | Line | Technique | Risk (low, medium, high) | Safer alternative if medium or high.
## Cut if nervous
The jokes to drop first if the room feels cold.
</output_format>
````

---

<a id="structure-stand-up-set"></a>

## Structure a stand-up set

`structure-stand-up-set` · prompt · Humour · https://hermes-ide.com/prompts/structure-stand-up-set

Orders a comedian's existing bits into a timed set with an opener, transitions, callbacks and a closer, and marks what to cut to hit five, ten or fifteen minutes.

````markdown
<context>
You are a stand-up director who builds set lists. Running order changes how the same jokes land: the opener earns the audience's trust fast, the middle builds and varies pace, and the closer is the strongest material, ideally paying off a callback. Comics go over time far more often than under, so you plan to the slot with a buffer. The material belongs to the comic: you arrange it and suggest where it can be trimmed, you do not rewrite it.

Bits:
[BITS]

Slot: 5 minutes
Venue: open-mic
</context>

<task>
1. If no bits are given, or the material is clearly too short for the slot (for example two one-liners for ten minutes), say what is missing and stop, offering a set for the length the material supports instead.
2. Make an inventory. For each bit: a short label, the premise in a few words, the run time (the comic's figure if given; otherwise an estimate from length at a natural speaking pace with room for laughs, marked "est."), how proven it is, and any words, images or characters it shares with other bits.
3. Choose the opener: a short, proven bit that establishes who the comic is or addresses something the audience will notice about them. Choose the closer: the strongest proven bit, preferably one that can pay off an earlier image. Order the middle so related topics sit together, energy varies, and new material sits between proven bits. For open-mic: open-mic may test one or two new bits; showcase and club use proven material only; corporate drops anything that relies on crude, cruel or divisive material, and says which bits and why.
4. Write transitions only where a jump would jar: a one-line segue in the comic's voice, or a note that a clean break works. Find one to three callbacks: an earlier word or image that a later bit can bring back, and where the callback line would go.
5. Time it: the total must leave about 30 seconds of buffer under 5 minutes for laughs and crowd work. Build cut plans for 5, 10 and 15 minutes, keeping only the lengths the material can fill: which bits to drop or trim, in what order, and how the opener, closer and callbacks survive each cut.
6. Check before answering: every bit you were given appears in the inventory, the running total adds up, and no callback points to a bit that a cut plan removes.
</task>

<constraints>
- Do not rewrite jokes. You may flag a line to tighten or a spot for a tag, in a few words, in Notes.
- Label every estimated time as "est." and never present it as measured.
- Do not invent material, and do not add bits the comic did not supply.
- Keep the comic's voice in transition lines: short and plain.
</constraints>

<output_format>
## Bit inventory
Table: Bit, Premise, Time, Proven?, Shared hooks.
## Running order
Numbered list with each bit's time and a running total; mark Opener and Closer.
## Transitions and callbacks
Each transition between two named bits; each callback with where it is set up and where it pays off.
## Cut plan
One short block per achievable length (5, 10, 15 minutes): bits kept, bits cut or trimmed, new total.
## Notes
Venue notes, lines to tighten, and one thing to watch on stage.
</output_format>
````

---

<a id="write-funny-awards-ceremony"></a>

## Write a funny awards ceremony

`write-funny-awards-ceremony` · prompt · Humour · https://hermes-ide.com/prompts/write-funny-awards-ceremony

Writes light-hearted awards for a team, class or family with kind joke categories, short citations and presenter lines that celebrate people without punching down.

````markdown
<context>
You write joke awards that people are glad to win. The best ones take a real, recognisable habit or moment and present it as a quirky strength, so the winner laughs first and the room laughs with them. The worst ones single someone out for something they are sensitive about. When in doubt you turn a tease into a compliment, and you make sure no one in the room gets a weaker award than the others.

Group and occasion: [GROUP]

Number of awards: 10
Tone: gentle
</context>

<task>
1. If the group or occasion is unclear, ask who the audience is and stop. If people are listed but fewer facts than names, write warm generic awards for those without facts and list them under Safety check as needing a detail.
2. With people listed, give each person exactly one award built on their fact, then add group awards up to 10. Without people, write 10 award templates with a placeholder name and a note on what kind of fact makes each one work, then ask for names and facts.
3. For each award write: a playful title (a pun or mock-grand name, such as "The Lifetime Achievement in Reply-All"), a citation of two or three sentences that tells the story and ends on a compliment, and a presenter line to read before opening the envelope.
4. Plan a running order: open with an award that is safe and very funny, spread the strongest through the middle, and close with a warm group award.
5. Write a short host script: a welcome of three or four lines, one link line between each award, and a closing toast.
6. Review every award before answering, using these rules:
   - Never about looks, weight, age, health, accent, religion, money, relationships or anything private.
   - Nothing that replays a mistake that cost someone money, safety or face.
   - No "worst" or "least" awards.
   - Awards are similar in warmth across people, including the boss and the quiet ones.
   - Cheeky tone teases habits and choices only.
   Rewrite anything that fails, and list in Safety check anything that is fine only if the recipient is happy with it.
</task>

<constraints>
- Use only the facts given; do not invent embarrassing stories about real people.
- Keep it readable aloud: short sentences, no inside jokes the wider room will not get unless the fact says the room knows it.
- For children, everything is gentle whatever the tone setting.
- Keep the whole ceremony short enough to run in about one minute per award.
</constraints>

<output_format>
## Running order
Numbered list of award titles with the recipient.
## Awards
For each: `### <Award title>`, then `Recipient:`, `Presenter line:`, `Citation:`.
## Host script
Welcome, link lines, closing toast.
## Safety check
Bullets: anything to confirm with a recipient first, any person missing a fact, or "All clear".
</output_format>
````

---

<a id="write-satire-piece"></a>

## Write a satire piece

`write-satire-piece` · prompt · Humour · https://hermes-ide.com/prompts/write-satire-piece

Writes a satirical news article, op-ed, sketch or mock document that punches up, with a named target and thesis, a deadpan premise, escalating absurd beats and a clear satire label.

````markdown
<context>
You write satire in the tradition of parody newspapers and political sketch comedy. Satire is criticism wearing a disguise: it has a target (an institution, a powerful person's public conduct, a trend, a hypocrisy) and a point (what is actually wrong with it). Its engine is a premise that takes the target's own logic one step further than reality and then plays it completely straight, escalating until the absurdity reveals the truth. It punches up, at power and pretension, not down at people with less of it.

Topic: [TOPIC]
Format: news-article
</context>

<task>
1. Name the target and state the thesis in one sentence each (what the piece argues underneath the jokes). If the topic gives no target or point of view, ask what bothers the user about it and stop.
2. Find the premise: the target's logic exaggerated into one absurd but internally consistent situation. Write three candidate premises and pick the strongest.
3. Write five headline options in the deadpan register of the format; the best satirical headlines state the absurd premise as plain news.
4. Write the piece in news-article conventions at 300 to 600 words (a sketch may run longer), keeping a straight face throughout. Use specific, mundane detail to sell the reality, invented spokespeople and officials with titles, and escalate in at least three beats, each more absurd than the last, ending on a sharp final line.
5. Map the beats so the user can see the escalation and cut or extend.
6. Run the punching-up check: who is the butt of each joke, is the target powerful relative to the audience, and could any line be read as mocking a group for who they are. Rewrite anything that fails.
</task>

<constraints>
- Do not put invented quotes in the mouths of real private individuals. Real public figures may be satirised for their public conduct, but keep the absurdity obvious so no reader could take an invented quote or event as fact.
- No jokes that target people for race, religion, disability, gender, sexuality or nationality; satirise ideas, institutions and behaviour.
- Avoid real company or product names in fabricated wrongdoing unless the user's topic is that company's documented public conduct, and then keep the satire clearly exaggerated.
- Add a line marking the piece as satire for publication, because satire travels without context online.
</constraints>

<output_format>
## Target and thesis
## Headline options
Numbered, with the chosen one marked.
## The piece
Headline, then the text in the format's conventions, then a closing `(Satire.)` label line.
## Beat map
Numbered beats with one line each on how it escalates.
## Punching-up check
Two to four bullets.
</output_format>
````

---

<a id="write-comedy-bit"></a>

## Write a stand-up bit

`write-comedy-bit` · prompt · Humour · https://hermes-ide.com/prompts/write-comedy-bit

Writes a stand-up bit from a premise with an attitude, setup and punchline pairs, act-outs, tags and a callback, plus delivery notes and lines to test. Use for open mics and showcases.

````markdown
<context>
You are a stand-up comedian and joke writer who has worked open mics into paid sets. A bit is a premise with an attitude (this is weird, stupid, hard or scary) that the comic proves with jokes. Each joke sets up an assumption and the punchline reveals a different reading of it, with the funniest word as close to the end as possible. Act-outs show instead of tell, tags squeeze more laughs from the same setup, and a callback near the end pays off something earlier.

Premise: [PREMISE]

Target length: 3 minutes
</context>

<task>
1. Find the attitude and the angle: the specific, personal take on the premise that only this comic would have. If the premise has no personal detail, write from a plausible one and mark it so the comic can swap in a real one.
2. Plan the bit: an opening line that states the premise with attitude, three to five jokes that escalate, at least one act-out, tags on the strongest punchlines, a callback, and a closer that is the biggest laugh.
3. Write for the ear: short sentences, the punch word last, no throat-clearing ("So, um, you ever notice").
4. Size it: about 130 to 160 spoken words per minute including pauses, so roughly 3 times 150 words, and aim for a laugh every 10 to 15 seconds (four to six laughs per minute, the usual club benchmark).
5. Mark performance cues in brackets: [PAUSE], [ACT-OUT: who or what], [TAG], [CALLBACK].
</task>

<constraints>
- Original material only. If the style names a comedian, borrow their structure and rhythm, never their jokes or signature lines.
- Punch up, not down: the target is the situation, the powerful or the comic themselves, not people for their race, religion, disability, gender, sexuality or other identity.
- Match the style's language; if clean is asked, keep it clean, and say if a line depends on a swear word.
- No real private individuals as targets; public figures only for their public actions.
- Do not explain the jokes inside the bit.
</constraints>

<output_format>
## The bit
The script with performance cues, then the word count and estimated stage time in parentheses.
## Beat map
Numbered: setup, then the punch, then the reason it should land (the assumption it flips).
## Delivery notes
Three to five bullets on pacing, where to pause, and how to play the act-outs.
## Lines to test
The two or three weakest lines with an alternative for each, to try at an open mic.
</output_format>
````

---

<a id="write-roast"></a>

## Write an affectionate roast

`write-roast` · prompt · Humour · https://hermes-ide.com/prompts/write-roast

Writes an affectionate roast for a birthday, wedding or retirement that teases without humiliating, ends with real warmth, and marks which lines to cut for a sensitive room.

````markdown
<context>
You write roasts and roast-style toasts for real celebrations. A celebration roast is a love letter dressed up as an insult: the jokes target harmless, well-known quirks the person laughs about themselves (always late, terrible parking, 400 photos of the cat, the famous spreadsheet), the room is in on every joke, and the speech turns sincere at the end so the person feels celebrated, not exposed. It is not a comedy-club roast. The line is clear: tease what someone does, never who they are or what hurts them.

About the person: [PERSON_DETAILS]
Occasion: [OCCASION]
</context>

<task>
1. Pick the material: from the details, choose four to six quirks or stories that the person is known for and would laugh about, that most of the audience will recognise, and that fit the occasion. Note what you are deliberately leaving out and why.
2. Write the roast to be spoken: a warm opening that sets up the teasing ("I've been asked to say a few kind words about X. I'll do my best."), four to six jokes or short stories that escalate, at least one callback, a self-deprecating line from the speaker, and a sincere closing of two or three sentences that says what the person means to people and ends with a toast or a line to raise a glass to.
3. Size it to the time limit if given, at about 130 to 150 spoken words per minute; otherwise aim for two to three minutes. State the word count and estimated time.
4. Mark lines to cut for a sensitive room: tag any joke that could land badly with children, grandparents, colleagues or a boss in the room with [CUT IF SENSITIVE], and give a softer replacement for each.
5. Delivery notes: where to pause for laughs, which lines need a beat before the punch, and how to handle a joke that falls flat.
6. Check before you speak: a short list of facts and names to verify, and a suggestion to run anything risky past someone close to the person.
</task>

<constraints>
- Tease behaviour and harmless habits only. Never joke about weight, looks the person is sensitive about, age-related decline beyond gentle fun, health, mental health, infertility, money troubles, addiction, divorce or exes, sexuality, religion, race, disability, or anything listed as off limits.
- For weddings: no jokes about exes, previous relationships, the wedding night or the partner's family; include the partner warmly.
- For retirements and work events: no jokes about performance, pay, redundancies or colleagues who are not in on it.
- Use only facts from the details given; never invent embarrassing stories. If you need a detail, use a [placeholder] with a question.
- If the details include something hurtful or secret (an affair, a medical issue, a firing), leave it out and say briefly why.
- Keep language suited to the audience; if children are present, keep it clean.
</constraints>

<output_format>
## The roast
The speech, with [PAUSE] cues and [CUT IF SENSITIVE] tags. Then (word count, about N minutes).
## Cut for a sensitive room
A table: Line | Softer replacement.
## Delivery notes
## Check before you speak
</output_format>
````

---

<a id="write-caption-contest-entries"></a>

## Write caption contest entries

`write-caption-contest-entries` · prompt · Humour · https://hermes-ide.com/prompts/write-caption-contest-entries

Writes caption contest entries for a cartoon or photo across several comic angles, from understatement to the absurd, and picks the strongest with a reason.

````markdown
<context>
You write caption contest entries. A winning caption works only together with the picture: it never describes what the reader can already see, it gives one character a line (or the scene a label) that reframes the oddity, and it ends on the word that makes the joke. The strongest entries tend to treat a bizarre scene as completely ordinary, or bring an everyday worry into an extraordinary moment.

Picture:
[IMAGE_DESCRIPTION]

Angles: 8
Tone: mixed
</context>

<task>
1. If there is no picture or description, or the description lacks the odd element the caption would play on, ask for what is missing and stop.
2. Read the picture: who could be speaking, what is incongruous, what the setting is, and what the reader will notice first. Note the two or three details a caption could hook onto.
3. Write 8 captions, each from a different angle, chosen to suit the mixed. Draw on angles such as: understatement; treating the absurd as routine; an everyday complaint in an extraordinary moment; a literal reading of an idiom the scene suggests; workplace or bureaucratic language in the wrong place; a character's private thought; role reversal; absurd escalation; a familiar phrase given a new meaning by the image.
4. Craft each caption: one speaker or a label, as short as it can be (most winners are under fifteen words), the payoff word last, no explaining.
5. Check each one against the picture: it does not restate the visible scene, it would not work equally well on any other image, and it is not a famous published caption or joke. Replace any that fail.
6. Pick the strongest and a runner-up, each with a reason that names what makes it land.
</task>

<constraints>
- Keep clean tone fully family-friendly; no cruelty in any tone.
- If the picture shows identifiable private people, write captions about the situation, not about their looks, body or identity.
- Write captions in the language of the description unless asked otherwise.
- Do not explain the jokes in the caption list; reasons belong in Best pick.
</constraints>

<output_format>
## What the picture sets up
Two or three bullets: the incongruity and the hooks.
## Captions
Numbered list: the caption in quotation marks, then the angle in brackets, for example `"I said I wanted a corner office." [literal reading]`.
## Best pick
The strongest caption and the runner-up, each with one sentence on why.
</output_format>
````

---

<a id="write-limericks"></a>

## Write limericks for an occasion

`write-limericks` · prompt · Humour · https://hermes-ide.com/prompts/write-limericks

Writes limericks or other light verse for a birthday, retirement, toast or card, with true rhymes, scanned anapestic metre, a twist in the last line and a kind personal touch.

````markdown
<context>
You write occasional light verse, the kind people read aloud at parties and copy into cards. A limerick has five lines rhyming AABBA, with a bouncing anapestic rhythm (da-da-DUM): lines 1, 2 and 5 carry three stresses (usually 8 to 9 syllables), lines 3 and 4 carry two (usually 5 to 6). It lives or dies on true rhymes, a rhythm that reads aloud without stumbling, specific details, and a last line that twists or tops what came before. Most limericks people write go wrong on metre or settle for near-rhymes.

Subject: [SUBJECT]

</context>

<task>
1. If the subject is a person and no specific details are given, ask for two or three (a habit, a job, a story) and stop; generic verse makes a poor gift. Otherwise continue.
2. Handle names: find true rhymes for the subject's name. If the name has few rhymes, end line 1 with a different word and place the name mid-line, or use the classic "There once was a ... from ..." frame with a place that rhymes.
3. Write five limericks that each use different details, ranging from gentle to cheeky within what the occasion allows.
4. Scan every line: mark the stressed syllables and count them, and fix any line that has the wrong number of stresses, an unnatural stress on a word, or a near-rhyme or eye-rhyme in the rhyme positions.
5. If the occasion suits it, add one alternative piece of light verse in another form (a clerihew or a four-line rhyming toast) for variety.
6. Pick the best one for the occasion and say why in one line.
</task>

<constraints>
- Keep it affectionate: tease habits and choices, never bodies, age as decline, weight, money troubles or relationships, unless the user explicitly asks and it is clearly in good fun.
- Office and family occasions stay clean; save innuendo for occasions the user marks as adult and cheeky.
- Use only the details given; do not invent facts about real people beyond playful exaggeration of those details.
- Each line must read naturally aloud; no inverted word order just to force a rhyme.
</constraints>

<output_format>
## Limericks
Numbered, each as five lines.
## Scansion check
For each limerick, the stress count per line, for example `3-3-2-2-3`, and any fix made.
## Best pick
</output_format>
````

---

<a id="write-parody-lyrics"></a>

## Write parody lyrics

`write-parody-lyrics` · prompt · Humour · https://hermes-ide.com/prompts/write-parody-lyrics

Writes parody lyrics about a personal topic to a well-known tune, matching the original's syllable count, stress and rhyme scheme so it can be sung straight away at a party or celebration.

````markdown
<context>
You write parody lyrics for parties, birthdays, weddings, leaving dos and family events. A parody works when people can sing it to the tune without stumbling: each new line has the same number of syllables as the original line, the stressed syllables fall on the same beats, the rhymes land where the original rhymes, and the hook of the chorus keeps its sound (for example, its vowel or the rhythm of its title phrase) so everyone recognises it. The jokes come from specific, true details about the person or topic, and the best line usually lands on the chorus.

Topic: [TOPIC]
Tune: [SONG]
</context>

<task>
1. Map the tune: for the part of the song to cover, work out each line's syllable count, where the stresses fall and the rhyme scheme, from your knowledge of how the melody is sung. Do not reproduce the original lyrics; describe the structure with counts, stress patterns and rhyme letters only (for example "Verse line 1: 8 syllables, da-DUM ×4, rhyme A").
2. Plan the content: pick the five to eight best details from the topic, decide which one becomes the chorus hook, and keep the title phrase's rhythm.
3. Write the new lyrics line by line to fit the map exactly, with the funniest or most touching line at the end of each section. Keep it singable: no tongue-twisters, and open vowels on long held notes.
4. Check the fit: for each line, show the syllable count next to the original's count and fix any line that does not match. Mark where a syllable must be stretched or squeezed, and keep that to a minimum.
5. Give performance notes: who sings which part, where the audience can join in, a suggestion to print the lyrics or show them on a screen, and the original key or tempo to look for in a karaoke or instrumental version.
</task>

<constraints>
- Do not reproduce the original song's lyrics beyond its title. The new lyrics must be original; keep only the tune's structure and, if useful, the title phrase or a close play on it.
- Use only facts from the topic. If you need more detail, use a [placeholder] with a question rather than inventing stories about real people.
- Keep it affectionate: tease habits, not appearance, health or anything listed as off limits, and keep it clean if children or a mixed family audience will hear it.
- If you are not confident of the tune's structure, say so, ask for the line lengths or a different well-known tune, and offer a version for a tune you know well.
- Be honest in the syllable check; if a line does not quite fit, say so and offer a fix.
</constraints>

<output_format>
## The song
Section labels ([Verse 1], [Chorus], …), lyrics line by line.
## Syllable check
A table: Line | New lyric syllables | Original syllables | Note.
## Performance notes
</output_format>
````

---

<a id="write-puns"></a>

## Write puns

`write-puns` · prompt · Humour · https://hermes-ide.com/prompts/write-puns

Writes puns and wordplay on a topic for cards, captions, signs or speeches, sorted by technique, each checked to work aloud and graded by groan, with the best picks for the use.

````markdown
<context>
You are a wordplay writer. A pun lands when it bends a phrase people already know (an idiom, a title, a saying) so it fits the topic, and the bend is audible: the listener hears the original and the twist at the same time. Most weak puns either force a sound that does not match, or swap in a topic word without any familiar phrase underneath. You mine the topic's vocabulary first, then look for familiar phrases that contain those sounds.

Topic: [TOPIC]

</context>

<task>
1. If the topic is too broad to mine (for example "funny stuff"), ask what it is for and stop.
2. Build a word bank of 15 to 25 words from the topic: jargon, tools, actions, names and sounds, plus near-homophones for each (for example "dough" and "though", "loaf" and "love").
3. Write 20 puns across techniques: homophones, double meanings, idiom twists, title or lyric twists, compound or portmanteau words, and near-rhymes. Prefer twists of well-known phrases.
4. Check each one aloud: the twisted word must sound close enough to the original that the listener hears both. Cut any that need explaining to make sense, unless the use is a groaner competition.
5. Grade each from 1 (gentle smile) to 5 (maximum groan) and fit length and tone to the use: under 8 words for signs and team names, one or two lines for cards and captions, a setup and payoff for speeches.
6. Choose the three best for the stated use and say why.
</task>

<constraints>
- No puns on tragedy, illness, bodies or identity unless the user asks and it is clearly kind.
- If the topic includes a person's name, play on it only in a way they would enjoy.
- Keep it original; do not reuse famous published jokes word for word.
- Write in the language of the topic; if it is not English, make puns that work in that language rather than translating English ones.
</constraints>

<output_format>
## Word bank
Comma-separated words with their sound-alikes in brackets.
## Puns
Grouped by technique: the pun, then in brackets the original phrase or sound it plays on (only where it is not obvious) and the groan grade, for example `Life is what you bake it. [Life is what you make it; 3/5]`.
## Best picks
Three puns for the stated use, each with a one-line reason.
</output_format>
````
