How to use the HTML Product Launch Deck agent skill

What the skill makes the agent do

The skill is aimed at sales and account teams drafting a decision-grade proposal for a prospective customer. Its example subject is a mid-market design team weighing a switch from closed cloud tools, with a design team lead and IT as the audience.

The agent produces a polished HTML deck built from the product-launch template. It copies the template files, fixes asset links so the deck works offline, keeps speaker notes out of the visible slide, and structures content around a decision rather than a feature list. Before writing, the agent asks for key details such as the audience, the decision goal and any numbers that must stay in the deck.

• Output is an HTML file you open in a browser, not a PowerPoint or Google Slides file.
• The skill supplies structure and layout. It tells the agent not to invent market data or figures.
• Speaker notes go inside an aside or div with the class notes, so they do not appear on the slide.

Install the skill from a ZIP file

Download the ZIP for this skill from this page and unzip it. You can install it for yourself or for a single project.

For a personal install, unzip it into ~/.claude/skills/. For a project-only install, unzip it into the .claude/skills/ folder inside your project. The skill files include SKILL.md and an example.html file.

If you use the Claude apps instead of files on disk, open Settings, go to Capabilities, then Skills, and upload the skill there.

• Personal folder: ~/.claude/skills/
• Project folder: .claude/skills/ inside the project
• Claude apps: Settings → Capabilities → Skills

Check the requirements before you start

The skill needs an AI agent that can read and write files in a project folder. It also relies on the html-ppt master skill files, which the source references through relative paths in the repository. Without those files, the agent cannot follow the authoring rules or find the template.

You need a web browser to open and view the finished deck. The skill does not run scripts and does not use the network, according to its listing.

• An agent that can read and write files in a project folder
• The html-ppt master skill files, referenced by relative paths in the repository
• A web browser to view the HTML deck

Trigger the skill with a natural request

You do not need special syntax. Describe the deck you want and mention the sales or rollout context. The skill's triggers include phrases such as html deck, html slides, sales, renewal, customer and b2b-sales, so requests using those words are most likely to pick it up.

Give the agent the missing essentials up front: who the audience is, what decision you want, what source material you have, your deadline and any numbers that must stay exactly as written. The agent is designed to ask for these first.

• Example: Build an HTML sales deck for a design team lead and IT, asking them to move from closed cloud tools to our team plan. Our must-keep numbers are in the attached notes.
• Example: Make an html slides proposal for a renewal call with a customer whose main concern is rollout risk.
• Example: Draft a decision-focused html deck for a prospective customer. Ask me for anything missing before you write the slides.

Understand how the deck is assembled

The source is explicit that the upstream index.html loads shared CSS and JavaScript through parent-relative paths. Once you copy that file into a project, those paths break and the slides will not activate. The skill therefore offers two recipes: copy the shared assets into a project-local assets folder and rewrite the links, or inline the same files into one self-contained index.html.

Either way, do not ship the original parent-relative asset URLs in the final file. The agent is also told to pick a theme. Default tokens are fine, and any of the 36 bundled theme files can be swapped in, with the T key cycling through them.

• Recipe A (preferred): copy fonts.css, base.css, animations.css and runtime.js into a local assets folder and point the tags there.
• Recipe B: replace the link and script tags with style and script blocks holding the file contents.
• Keep the .tpl-product-launch body class and the structural classes in the template.

Review the deck before sharing it

Open the HTML file in a browser and step through every slide. Confirm that navigation works, since the source warns that broken links leave the deck inactive. Check that no speaker notes appear as visible text. Then check every number against your source material, because the skill does not verify figures.

The skill's example prompt includes a critic pass with one test: can the champion forward this deck internally without rewriting it. Use that test as your final check.

• Navigation works with the keyboard after opening the file offline.
• Speaker notes are not visible on any slide.
• Every figure matches a source you can name.
• The attribution and LICENSE file stay in place when you redistribute the deck.