CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/speaker-toolkit

Six-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, and publish talk pages to a Jekyll shownotes site. Includes a 111-entry Presentation Patterns taxonomy (81 observable: 62 patterns + 19 antipatterns; 30 unobservable: 21 patterns + 9 antipatterns) for scoring, brainstorming, and go-live preparation.

Quality

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

invisibility.mdskills/presentation-creator/references/patterns/build/

id:
invisibility
name:
Invisibility
type:
pattern
part:
build
phase_relevance:
slides
vault_dimensions:
13
evidence_channels:
slide_sequence, video
detection_signals:
hidden elements revealed during presentation, surprise reveals, handout vs live differences
evaluable_from:
native_deck, native_deck,static_slides, delivery_video,static_slides
strong_evaluable_from:
native_deck, native_deck,static_slides, delivery_video,static_slides
absence_evaluable_from:
null
evidence_requirements:
Evidence must show a live reveal of an element absent from the static or distributed state., Use either inspectable zero-opacity animation metadata or an explicit comparison naming the live and static sources.
not_evaluable_when:
Only a static slide, PDF, or final-state image is available., An entrance effect is visible but the source cannot establish that the element was deliberately absent from the distributed state., The sources do not establish a pre-distribution requirement, so a non-detection cannot prove that this distribution-specific technique was applicable and absent.
related_patterns:
gradual-consistency
inverse_of:
difficulty:
advanced

Invisibility

Summary

Use invisible elements that do not appear on printed slides but are revealed during the live presentation, preserving surprise and creating moments that only the in-room audience experiences.

The Pattern in Detail

The Invisibility pattern exploits a technical property of presentation tools that most presenters never consider: elements with zero opacity are invisible in exported PDFs and printed handouts but can be animated to full visibility during a live presentation. By setting an element's opacity to 0% in the slide designer, you create a ghost element that occupies space on the canvas but leaves no visual trace in any static export. During the live presentation, an animation brings the element to full opacity, revealing it to the audience as if it materialized from nothing. The result is content that exists exclusively in the live experience.

This technique is particularly valuable in a specific and frustrating scenario: when you are forced to distribute handouts or slide decks before your presentation. Many conferences, corporate events, and academic settings require speakers to submit their slides in advance for distribution. This creates a dilemma: anything on your slides is visible to the audience before you present it, which kills surprise, undermines narrative tension, and allows the audience to jump ahead. Invisibility solves this problem by allowing you to include elements in your presentation that simply do not exist in the distributed version.

The implementation is straightforward but requires precision. In the slide designer (Keynote, PowerPoint, or Google Slides), place your element — text, image, shape, or diagram — in its desired position, then set its opacity to 0%. The element is now invisible in the design view and will not appear in any exported format (PDF, image, print). In the animation panel, add an appearance animation (fade in, dissolve, or similar) that transitions the element from 0% to 100% opacity. During the live presentation, triggering this animation reveals the element. In Keynote, this is achieved through the "Opacity" build animation or by using "Appear" with a dissolve. In PowerPoint, the "Fade" entrance effect accomplishes the same result.

The pattern can be used for a variety of purposes beyond simply hiding punchlines. You can create "before and after" reveals where the printed slide shows only the "before" state and the live presentation reveals the "after." You can hide annotations, callouts, or explanatory labels that guide the live audience but would clutter the printed version. You can even create entire hidden slides by making all elements invisible, resulting in what appears to be a blank slide in print but becomes a fully populated slide during presentation.

One advanced application combines Invisibility with interactive or adaptive presentation styles. You can prepare multiple invisible elements on a single slide, each containing a different response or direction, and reveal only the one that is appropriate based on audience questions or discussion. This gives you the appearance of spontaneity — producing exactly the right visual at exactly the right moment — while actually having prepared multiple contingencies in advance.

When to Use / When to Avoid

Use Invisibility when you must distribute slides before your presentation and want to preserve surprise elements. It is also valuable when you want the live experience to differ meaningfully from the printed artifact, creating an incentive for in-person attendance. The pattern is essential for presentations that depend on reveals, surprises, or "aha" moments.

Avoid Invisibility when there is no distribution requirement — if your slides will never be shared, there is no need to hide elements. Also avoid over-relying on the technique, as an audience that discovers multiple "hidden" reveals may feel manipulated rather than surprised. Use it for two or three key moments, not for every slide.

Detection Heuristics

When scoring live presentations, look for elements that appear to materialize on slides that seemed complete or sparse — content that clearly was not visible in the static layout suddenly appearing through animation. Comparing distributed handouts to the live presentation and noting significant differences is the most reliable detection method.

Scoring Criteria

  • Strong signal: Strategic use of hidden elements revealed during live presentation to create surprise or emphasis, particularly when handouts were distributed in advance; clear difference between live and printed versions
  • Moderate signal: Some elements appear through animation that could have been hidden for strategic purposes, but the intent is unclear
  • Absent: All elements visible in both printed and live versions, no strategic use of opacity or hidden elements

Evidence Gate

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.

Relationship to Vault Dimensions

Dimension 13 (Visual Polish and Craft): Invisibility demonstrates advanced technical knowledge of presentation tool capabilities and sophisticated thinking about the relationship between live and printed artifacts.

Combinatorics

Invisibility pairs naturally with Gradual Consistency — both patterns address the live-versus-printed duality, but Invisibility takes it further by making some elements exclusive to the live experience. The pattern can enhance Foreshadowing by hiding the payoff reveal from anyone who reads ahead in the handouts. It also supports A La Carte Content by allowing the presenter to have multiple contingency elements prepared but invisible until needed.

skills

presentation-creator

references

patterns

_index.md

alternate-entry-flows.md

deck-editing-setup.md

deckops-spec.md

idea-sourcing-wizard.md

pattern-history-authorization.md

phase0-intake.md

phase1-intent.md

phase2-architecture.md

phase3-content.md

phase4-guardrails.md

phase5-slides.md

phase6-publishing.md

phase7-post-event.md

SKILL.md

README.md

tile.json