Seven-skill presentation system: ingest talks into a rhetoric vault, run interactive clarification, generate a speaker profile, create presentations that match your documented patterns, produce the deck illustrations + thumbnail visual layer, publish talk pages to a Jekyll shownotes site, and verify a recorded screencast against its storyboard. Includes a 113-entry Presentation Patterns taxonomy (83 observable: 64 patterns + 19 antipatterns; 30 unobservable: 21 patterns + 9 antipatterns) for scoring, brainstorming, and go-live preparation.
74
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
The room is cold. Instead of pushing harder or pretending not to notice, name the temperature out loud, keep needling it as a running gag, and cash the payoff the moment the room turns. The speaker heckles the audience — affectionately, collectively, and with a punchline waiting.
Every speaker meets the quiet room. Hands do not go up, polls die, and the interaction the talk was built around stops working. The standard responses fail in predictable ways. Pushing harder ("come on, don't be shy!") reads as need. Pretending the poll landed reads as dishonest, because the room knows it did not. Abandoning interaction altogether surrenders the talk's structure to the first two minutes of a bad read.
Reverse Heckle takes the third option: make the room's behaviour the material. It has three beats and needs all of them.
Diagnose. Name what is happening, out loud, without complaint. The observation must be accurate and lightly held — a hypothesis offered to the room, not a grievance filed against it. Attributing it to something other than the audience's interest (the hour, the venue, a regional norm, the speaker's own question) keeps it away from accusation.
Needle. Return to it. One remark is a wry aside; a pattern is a running gag. Each callback raises the stakes slightly and — this is the mechanism — makes participating into the punchline. The room now has a reason to answer that has nothing to do with the question: answering breaks the joke, and breaking the joke is funnier than the joke.
Pay off. When the hands go up, say so. The payoff line is what converts thirty minutes of low-grade needling into a shared victory rather than a long complaint. Skip it and the audience is left holding the diagnosis with nothing on top.
The mechanism is worth stating plainly, because it explains the pattern's constraint. Reverse Heckle works by making non-participation conspicuous — the room becomes aware of itself as a character in the talk. That awareness is only pleasant if the room already likes the speaker. Delivered by someone the audience has not warmed to, the identical words are contempt, and the room closes for good.
Use it when a talk depends structurally on audience response — polls, predictions, guess-first reveals — and the response is not arriving. Use it early, while the diagnosis can still be framed as curiosity rather than frustration.
Avoid it before rapport exists. The pattern is a withdrawal against goodwill and overdrafts badly. Avoid it when the reticence has a cause the joke would trample — a language barrier, a corporate audience where speaking up carries a cost, a room that has just heard bad news. Avoid it entirely in webinars and recorded-to-camera formats, where there is no room to turn. And never let the target narrow: the pattern is safe aimed at the room, and stops being safe the moment it lands on one identifiable person, at which point it is hecklers with the roles swapped.
Distinguish from ordinary self-deprecating filler about a quiet room: the difference is the return trip. No repetition and no payoff means no pattern.
Use strong_evaluable_from, evidence_requirements, and not_evaluable_when above to evaluate positive evidence.
Current catalog artifacts may support positive detection only. Because absence_evaluable_from is null, no delivery video, transcript, rendered or native deck, comparison artifact, or claim of full coverage authorizes an absence finding; when no positive signal is established, record not_evaluable, not absent.
Not applicable to formats without a co-present audience.
Relates to Dimension 4 (Audience Interaction) as the primary axis, but is the recovery move rather than the interaction itself. Most Dimension 4 patterns assume the audience responds; this one is for the delivery where they do not, and it is the difference between a talk that loses its interactive spine in the first five minutes and one that gets it back by minute forty.
Relates to Dimension 3 (Humor & Wit) as the vehicle. The diagnosis only survives repetition if it is funny; a repeated accurate complaint is just a complaint. The pattern is a running gag whose subject happens to be the audience.
Depends on know-your-audience, which supplies the read the diagnosis is built on. Getting the read wrong makes the gag land as a misjudgement of the room in front of the room.
Pairs strongly with guess-first: the predict-before-reveal beats are exactly the moments that expose reticence, so they supply both the evidence for the diagnosis and the eventual payoff.
Pairs with greek-chorus. A named ally in the room gives the needling a specific target who is safely in on it, which keeps the collective version lighter by comparison.
Inverse of hecklers. The catalog already scores the audience disrupting the speaker; this is the same energy pointed the other way, and it is a pattern rather than an antipattern only because the speaker controls the volume and owns the payoff.
Field-observed rather than sourced from the literature.
Provenance note. This entry was drafted from the JavaZone 2026 delivery of
"The Right 300 Tokens Beat 100k Noisy Ones", but the speaker reviewed that
episode and it is not an instance of this pattern: he had been warned the
room would not participate and named it defensively, then cheered sincerely
when it turned. That belongs to inoculation (see its expected-failure
refinement), not here. The technique described above — deliberately needling a
cold room until participating becomes the punchline — is retained as a distinct
and useful move, but it currently has no confirmed observed instance in the
corpus. Treat it as available for selection, not as established speaker
history, until a delivery evidences it.
.tessl-plugin
rules
skills
illustrations
presentation-creator
references
patterns
build
deliver
prepare
scripts
screencast-recorder
shownotes-publisher
vault-clarification
vault-ingress
references
scripts
vault-profile