agentleFS
pantheon-orgpantheon-org/tekhne/skills/comedy/brooker-esque-media-satire/SKILL.md

brooker-esque-media-satire

Skill10 starsChanged 40 days agoMITView on GitHub

Generate original, misanthropic media/technology satire in the Charlie-Brooker tradition — a cynical column, monologue, short story built from one extended grotesque metaphor, self-loathing narration, hyperbole-and-bathos, corporate-jargon translation, plus a near-future premise that escalates one believable step at a time toward a bleak, deflating ending. Use for a satirical takedown of a TV show, app, gadget, news format, or social-media trend, plus dystopian near-future short stories about a plausible technology/social mechanic. Do NOT use for mockumentary/character-voice sketches, deadpan two-hander political interviews, observational stand-up; also not for reproducing a real writer's actual column, script, episode — this skill only generates new material inspired by the technique, never a copy.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the escalation obeying its own machine-like rules: a nightmare that follows believably from a small premise unsettles a reader.

    line 12
  2. Distinctive:

    Use this for a cynical column or monologue about a TV format, app, gadget, or news story.

    line 16
  3. Distinctive:

    Use this for a Black-Mirror-style short story pushing one small, current mechanic into a nightmare.

    line 17
  4. Distinctive:

    Use this to mock corporate jargon by quoting it and translating it plainly.

    line 18
  5. Distinctive:

    Do not use this to quote, closely paraphrase, or "tidy up" an existing real column, script, or episode.

    line 24
  6. Distinctive:

    Keep hopeful or triumphant endings out of scope for this skill.

    line 25
  7. Very specific:

    Before starting, have a mundane subject (a TV format, gadget, app, news story, or social trend) and a target form: rant/column/monologue, …

    line 29
  8. Distinctive:

    Add a jargon-mockery beat if the subject carries corporate language: quote it dryly, translate what it means.

    line 38
  9. Distinctive:

    Keep the ending flat: close on a bleak note, without triumph.

    line 40
  10. Distinctive:

    Run a final check against the anti-patterns below to verify the draft before calling it done.

    line 41
  11. Distinctive:

    PREFER a single scaling metaphor system (an illness, a production line, a court case) over switching images mid-piece.

    line 45
  12. Distinctive:

    Follow the trivial-annoyance-first pattern for hyperbole and bathos together: describe it in apocalyptic terms, then undercut it with how …

    line 54
  13. Distinctive:

    Test the escalation for logical jumps before finishing a story.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Misanthropic Media & Technology Satire

Build comedy around a weary, contemptuous narrator dismantling media, technology, or culture through one sustained, escalating metaphor rather than a string of unrelated jokes: the output is new writing, never a reproduction of anyone else's material.

Mindset

Keep the escalation obeying its own machine-like rules: a nightmare that follows believably from a small premise unsettles a reader; breaking that rule once turns the piece silly instead.

When to Use

  • Use this for a cynical column or monologue about a TV format, app, gadget, or news story.
  • Use this for a Black-Mirror-style short story pushing one small, current mechanic into a nightmare.
  • Use this to mock corporate jargon by quoting it and translating it plainly.

When NOT to Use

  • Skip this for mockumentary-style sketches built on character voices rather than narration.
  • Skip this for deadpan interviews or observational stand-up — anything not a narrator dismantling a subject through metaphor.
  • Do not use this to quote, closely paraphrase, or "tidy up" an existing real column, script, or episode.
  • Keep hopeful or triumphant endings out of scope for this skill.

Prerequisites

Before starting, have a mundane subject (a TV format, gadget, app, news story, or social trend) and a target form: rant/column/monologue, or escalating short story.

Workflow

  1. Define the subject — a mundane, recognisable format, gadget, app, or trend.
  2. Set the form: follow the rant branch below for a column or monologue; otherwise follow the story branch for a short story.
  3. Build the rant around one grotesque metaphor: extend it across elaborate sentences, then puncture with a short, blunt clause.
  4. Build the story around one escalating cause-and-effect chain instead, one plausible consequence at a time.
  5. Include self-directed contempt alongside contempt for the subject, weighted however suits the piece.
  6. Add a jargon-mockery beat if the subject carries corporate language: quote it dryly, translate what it means.
  7. Return to the centre near the end, worse, rather than introducing something new.
  8. Keep the ending flat: close on a bleak note, without triumph.
  9. Run a final check against the anti-patterns below to verify the draft before calling it done.

Core Mechanics

PREFER a single scaling metaphor system (an illness, a production line, a court case) over switching images mid-piece. AVOID a second unrelated joke once the first metaphor lands, UNLESS the piece is deliberately fragmented.

The app doesn't send notifications, it triages you: every ping is a small
paramedic arriving to say which part of your life is bleeding out fastest.

→ produces: one image (triage) followed mechanically, not switched mid-thought.

Follow the trivial-annoyance-first pattern for hyperbole and bathos together: describe it in apocalyptic terms, then undercut it with how small the problem really is.

The buffering wheel spun for what felt like a geological era — and then
the video played, and it was a man reviewing a kettle.

→ creates: an apocalyptic build-up punctured by a small, flat payoff.

Test the escalation for logical jumps before finishing a story.

make check-draft FILE=draft.md

That command is illustrative only — this skill ships no such script.

Anti-Patterns

NEVER reproduce Charlie Brooker's actual columns, Screenwipe/Newswipe scripts, Black Mirror episodes, or specific lines verbatim or near-verbatim.

WHY: it is copyrighted material, and reproducing it defeats a generative skill — the user gets a copy, not new satire.

SYMPTOM: a draft sentence could be traced back to a real broadcast column or episode with only a few words changed.

❌ BAD — lightly reworded lift of a known line about a real talent show,
changing only a few nouns.

✅ GOOD — an entirely new grotesque metaphor for an invented streaming
competition, built from scratch.

→ produces: material that teaches the technique instead of copying a joke.

CONSEQUENCE: the output is a copyright liability disguised as a deliverable.

NEVER let the escalation break plausible cause-and-effect logic.

WHY: random surrealism reads as silly; a believable step reads as unsettling — that believability is the engine of the form.

SYMPTOM: a step in the chain needs a new capability or actor that nothing earlier set up.

❌ BAD — "The fridge started ordering groceries. Then, for no reason, it
declared war on a neighbouring appliance."

✅ GOOD — "The fridge started ordering groceries. Then it began
substituting cheaper brands to hit a margin target in the terms of service."

→ produces: a step the reader can imagine a real company actually taking.

CONSEQUENCE: the piece stops being unsettling and becomes a shrug.

NEVER end on a triumphant or hopeful note.

WHY: the bleak ending — the narrator saw it coming and nothing was done — is the punchline; a hopeful ending undercuts the tone.

SYMPTOM: the final beat has a character learning something, fixing the situation, or feeling relief.

❌ BAD — "She deleted the app, felt the sun on her face, and realised
she'd been free all along."

✅ GOOD — "She deleted the app. It reinstalled itself during a routine
update nobody remembers agreeing to."

→ produces: a last beat with no fix and no relief, which is the joke.

CONSEQUENCE: a hopeful last beat reads as a tonal U-turn, and the escalation stops paying off.

References

TopicReferenceWhen to Use
Extended-metaphor mechanics, narrator voice, jargon-translation technique in depthExtended Metaphor & Narrator VoiceLoad only when writing a rant/column/monologue and the metaphor is drifting or self-contempt feels bolted on; skip it unless that form is in play
Structuring a full near-future escalation chain and landing a bleak closeDystopian Escalation StructureLoad only when writing the short-story form and the escalation stalls, jumps illogically, or the ending drifts hopeful; not needed for a short rant

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.