CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/speaker-toolkit

Two-skill presentation system: analyze your speaking style into a rhetoric knowledge vault, then create new presentations that match your documented patterns. Includes an 88-entry Presentation Patterns taxonomy for scoring, brainstorming, and go-live preparation.

Overall
score

95%

Does it follow best practices?

Validation for skill structure

Overview
Skills
Evals
Files

_anti_going-meta.mdskills/presentation-creator/references/patterns/deliver/

id:
going-meta
name:
Going Meta
type:
antipattern
part:
deliver
phase_relevance:
guardrails
vault_dimensions:
9, 14
detection_signals:
speaker discusses preparation process, equipment apologies, meta-commentary about the talk itself
related_patterns:
breathing-room, carnegie-hall, crucible
inverse_of:
display-of-high-value
difficulty:
foundational

Going Meta

Summary

Never talk about the talk itself. The audience does not care about your preparation struggles, equipment issues, or timing concerns. Any behind-the-scenes problem you resolved is invisible to them unless you make it visible.

The Pattern in Detail

"I was building these slides until 2 AM last night." "Sorry, I thought I had sixty minutes but apparently I only have forty-five." "The projector is not showing my colors correctly." "I originally had a much better demo but it stopped working this morning." Every one of these statements is an instance of Going Meta — breaking the fourth wall to comment on the presentation itself rather than delivering the content the audience came for. It is one of the most common and most damaging antipatterns in public speaking.

The core problem is that Going Meta converts invisible issues into visible ones. If you built your slides at 2 AM but they look fine, the audience would never know. The moment you mention it, every audience member starts scrutinizing your slides for signs of rush work. If the projector shifts your colors slightly, most people would not notice — until you point it out, at which point they cannot unsee it. If your original demo broke but your backup works, you are a hero — unless you tell them about the original, at which point they spend the rest of the talk wondering what they missed. You are literally creating problems in the audience's mind that did not previously exist.

The impulse to Go Meta usually stems from one of three sources. First, nervous honesty: the speaker is anxious and their brain defaults to narrating the anxiety. "I am so nervous" is the most basic form. Second, preemptive excuse-making: the speaker fears the audience will notice an imperfection and tries to get ahead of it by explaining the circumstances. This almost always backfires because the explanation draws attention to the imperfection. Third, misplaced rapport-building: the speaker thinks that sharing their preparation struggles will humanize them and create connection. In practice, it undermines the Display of High Value by broadcasting vulnerability that the audience did not ask for and does not benefit from.

The rule is simple: if the audience would not know about a problem unless you mentioned it, do not mention it. The projector is slightly off? Deliver your talk. The demo needs a workaround? Execute the workaround without commentary. You had to restructure your talk this morning? The audience sees only the version you deliver, not the version you planned. The only exception is when a visible, ongoing issue directly affects the audience's experience and ignoring it would seem oblivious — for example, if the room is extremely hot or if significant audio problems are making it hard to hear. Even then, acknowledge briefly and move on; do not dwell.

This does not mean you cannot be authentic or vulnerable. The Mentor pattern encourages sharing your learning journey. The difference is that Mentor vulnerability serves the audience ("here is what I struggled with so you can avoid the same mistake") while Going Meta vulnerability serves the speaker ("here is why you should lower your expectations of me").

When to Use / When to Avoid

This is an antipattern to avoid in every presentation. There are no scenarios where telling the audience about your behind-the-scenes struggles improves their experience. Even in casual, informal settings, meta-commentary about the talk subtracts rather than adds. The only narrow exception is when a visible, audience-affecting issue requires brief acknowledgment to demonstrate awareness — but even then, acknowledge and move on immediately.

Detection Heuristics

  • Speaker mentions preparation timeline, lost sleep, or last-minute changes
  • Speaker apologizes for equipment, projector, or demo issues
  • Speaker comments on the talk's structure, timing, or slot placement
  • Speaker references problems the audience would not have noticed otherwise

Scoring Criteria

  • Strong signal (2 pts): Speaker never goes meta — no apologies, no preparation commentary, no equipment excuses, all problems handled invisibly
  • Moderate signal (1 pt): One or two minor meta-comments that are quickly moved past without dwelling
  • Absent (0 pts): Multiple instances of going meta — speaker repeatedly comments on preparation, equipment, timing, or other behind-the-scenes concerns

Relationship to Vault Dimensions

This antipattern maps to Vault Dimension 9 (Speaker Authority / Credibility) because every meta-comment erodes the audience's confidence in the speaker, and to Vault Dimension 14 (Speaker Craft / Professionalism) because avoiding meta-commentary is a fundamental professional discipline.

Combinatorics

Going Meta is the direct inverse of Display of High Value — one builds authority, the other erodes it. Carnegie Hall rehearsal helps prevent it by building familiarity that reduces the anxiety-driven narration impulse. Preparation reduces Going Meta by resolving issues in advance so there is nothing to apologize for. The Breathing Room pattern helps by providing comfortable silence as an alternative to nervous meta-commentary.

Install with Tessl CLI

npx tessl i jbaruch/speaker-toolkit@0.5.1

skills

presentation-creator

references

patterns

_index.md

guardrails.md

process.md

slide-generation.md

SKILL.md

CHANGELOG.md

README.md

tile.json