Reveal.js Presentations

Create Reveal.js decks in the delivery mode requested by the user. General websites, PPTX editing, and speech outlines without deck implementation are outside this Skill. For review-only requests, inspect and report without editing or rebuilding the user's files.

Working example

When the user asks how to use this Skill or wants to see a finished example, open the interactive walkthrough in a browser. It is a self-contained English deck with offline playback and a speaker window opened with S or Speaker; allow the browser popup if needed. Read the HTML source only when inspecting or adapting the example. Its layout, language, pinned runtime, and custom speaker implementation are illustrative choices, not defaults for other decks.

Establish the delivery contract

Determine the audience, presentation duration, language, output location, and conditions below from the request and existing material. Reuse settled decisions; ask only about missing information that materially changes the result. Write the presentation in the user's requested language, independently of this Skill's language.

• Delivery mode: Choose a single file, static folder, or existing project using the table below. Source organization and delivery format may differ.
• Resource policy: Determine whether offline operation is required or CDN assets, remote media, and other network dependencies are allowed. An HTML presentation does not automatically require complete inlining.
• Launch method: Distinguish opening through file:// from serving over local HTTP. Establish requirements separately for the main deck and speaker view. One file does not guarantee every feature works when opened directly in every browser.
• Feature scope: Determine whether the deck needs per-slide notes, current/next previews, fragments, mobile reading, printing, or PDF output. Add unspecified complex features only when their purpose justifies them.

Create or edit files only in authorized locations; preserve the personal status of personal drafts. Publish, commit, install globally, or upload assets only when the task authorizes those actions.