html-ppt-pitch-deck
Helps your agent create a concise and impactful investment pitch. It focuses on grabbing attention quickly, presenting traction, moat, and the funding ask.
What it does
This feature creates a visually appealing presentation for investors. It's designed to quickly grab attention and present crucial information about your company.
When to use it
- ✓When you need to pitch your startup to investors.
- ✓When participating in an accelerator's demo day.
- ✓To create a concise and impactful fundraising material.
Example of what to ask your AI
“Create a fundraising pitch deck for my AI-focused education technology startup.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
It uses a pre-defined template with a specific design for investment pitches. You replace the example content with your company's information, while keeping the visual structure.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add nexu-io/open-design --skill html-ppt-pitch-deckOr download just the file:
curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/design-templates/html-ppt-pitch-deck/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
HTML PPT · Pitch Deck
A focused entry point into the html-ppt master skill that lands the user directly on the pitch-deck full-deck template.
When this card is picked
The Examples gallery wires "Use this prompt" to the example_prompt above. When you accept that prompt, this card is the right pick if the user wants exactly the visual identity of pitch-deck (see the upstream full-decks catalog for screenshots and rationale).
How to author the deck
- Read the master skill first. All authoring rules live in
design-templates/html-ppt/SKILL.md— content/audience checklist, token rules, layout reuse, presenter mode, the keyboard runtime, and the "never put presenter-only text on the slide" rule. - Start from the matching template folder:
design-templates/html-ppt/templates/full-decks/pitch-deck/— copyindex.htmlandstyle.cssinto the project, keep the.tpl-pitch-deckbody class. - Bring the shared runtime with the template. The upstream
index.htmllinks the shared CSS/JS via../../../assets/...because it sits three folders deep insidedesign-templates/html-ppt/templates/full-decks/. Once you copyindex.htmlinto the project, those parent-relative URLs no longer resolve andbase.css,animations.css, andruntime.jswill 404 — meaning the deck never activates and slide navigation is dead. Pick one of these two recipes per project:- Recipe A — copy + rewrite (preferred): copy
design-templates/html-ppt/assets/fonts.css,design-templates/html-ppt/assets/base.css,design-templates/html-ppt/assets/animations/animations.css, anddesign-templates/html-ppt/assets/runtime.jsinto a project-localassets/(withassets/animations/animations.css), then rewrite the four<link>/<script>tags inindex.htmlfrom../../../assets/...to the matching project-local paths (assets/fonts.css,assets/base.css,assets/animations/animations.css,assets/runtime.js). - Recipe B — inline: read the same four files and replace each
<link rel="stylesheet" href="../../../assets/...">with a<style>...</style>containing the file's contents, and the<script src="../../../assets/runtime.js">with a<script>...</script>containingruntime.js. Yields a single self-containedindex.html. Either way, do not ship the upstream../../../assets/...URLs verbatim into a project artifact — they only work in-tree.
- Recipe A — copy + rewrite (preferred): copy
- Pick a theme. Default tokens look fine; if the user wants a different
feel, swap in any of the 36 themes from
design-templates/html-ppt/assets/themes/*.cssvia<link id="theme-link">and letTcycle. - Replace demo content, not classes. The
.tpl-pitch-deckscoped CSS only recognises the structural classes shipped in the template — keep them. - Speaker notes go inside
<aside class="notes">or<div class="notes">— never as visible text on the slide.
Attribution
Visual system, layouts, themes and the runtime keyboard model come from
the upstream MIT-licensed lewislulu/html-ppt-skill. The
LICENSE file ships at design-templates/html-ppt/LICENSE; please keep it in place when
redistributing.
FAQ
What are 'tokens'?
Tokens are like markers that help the AI understand and organize your presentation content, such as headings and text.
Where do I put speaker notes?
Speaker notes should be placed within specific tags like `<aside class="notes">` or `<div class="notes">`, so they don't appear on the slides.
Can I change the presentation's look?
Yes, you can choose from several pre-defined visual themes to alter your presentation's appearance.
Details
Original description by the author
OpenDesign's demo-day pitch: hook, traction, moat, and the raise — built to make a partner sit up by page three. Built as a decision-grade fundraising pitch deck for accelerator partners, angels.
repo: nexu-io/open-design
Popularity
- GitHub stars
- 101k
- Ranking position
- #427
- License
- Apache-2.0
- Updated
- 10/16/2026
Comments
- …
More skills from this repository
sample-plugin
Makes your agent create a metadata file for tests. It helps ensure code works correctly in different situations.
nexu-io/open-design
aster-atelier
Helps your agent create an artistic website with a classic look. It uses elegant imagery, blue skies, and serif fonts for a cinematic feel.
nexu-io/open-design
audio-jingle
Makes your agent generate audio like jingles and sound effects. It can create music and voices, saving the result as an audio file.
nexu-io/open-design
blog-post
Helps your agent write long articles or blog posts. It includes space for images, quotes, and author information.
nexu-io/open-design
Similar skills
architecture-decision-records
Has your agent record important project structure decisions. It helps to understand the reasoning behind choices and maintain a clear history of changes.
affaan-m/ECC
code-tour
Lets your agent create step-by-step code walkthroughs with exact file and line anchors. It's useful for project introductions, code explanations, or change reviews. Helps understand how a system works.
affaan-m/ECC
codebase-onboarding
Helps your agent analyze unfamiliar code and create an onboarding guide. It includes an architecture map, entry points, and conventions. Ideal for starting on a new project.
affaan-m/ECC