html-ppt-tech-sharing — Claude Code skill: HTML presentation builder
html-ppt-tech-sharing — a skill for building engineering presentations in HTML with navigation, themes, and speaker notes. Uses the tech-sharing template from the html-ppt library.
Apache-2.0 183 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill html-ppt-tech-sharing -a claude-codeWhat html-ppt-tech-sharing does
The skill generates a presentation from index.html and style.css, adds keyboard navigation (arrows, T to cycle themes), presenter mode, and animations. It includes 36 ready-made themes and structural classes for slides. Speaker notes go inside <aside class="notes"> and stay hidden from the slide.
After copying the template, you must manually move base.css, animations.css, runtime.js, and fonts.css from design-templates/html-ppt/assets/ into the project and rewrite the paths in index.html — otherwise navigation breaks. The second option is to inline the files directly into the HTML with <style> and <script> tags.
The visual system and keyboard runtime come from the MIT-licensed lewislulu/html-ppt-skill repository. The license file sits at design-templates/html-ppt/LICENSE.
What it helps with
- Build a technical presentation with speaker notes and animation
- Add keyboard navigation and presenter mode to HTML slides
- Create an engineering talk with switchable themes
- Make an HTML presentation without PowerPoint or Keynote
Example prompts for the agent
- Create a tech-sharing presentation about OpenDesign internals: agent stream, sandbox, and artifacts
- Build HTML slides for an engineering talk with speaker notes
- Generate a tech-sharing deck on AI tooling rollout
How to install html-ppt-tech-sharing
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-tech-sharing -a claude-code2Manually: put the files in place
~/.claude/skills/html-ppt-tech-sharing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/html-ppt-tech-sharing/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-tech-sharing -a codex2Manually: put the files in place
.agents/skills/html-ppt-tech-sharing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-tech-sharing -a cursor2Manually: put the files in place
.cursor/skills/html-ppt-tech-sharing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/html-ppt-tech-sharing/SKILL.md2Manually: put the files in place
.github/skills/html-ppt-tech-sharing/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-tech-sharing -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/html-ppt-tech-sharingManually: put the files in place
.devin/skills/html-ppt-tech-sharing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-tech-sharing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about html-ppt-tech-sharing
How to install html-ppt-tech-sharing in Claude Code?
Run npx skills add nexu-io/open-design --skill html-ppt-tech-sharing -a claude-code, then open ~/.claude/skills/html-ppt-tech-sharing/SKILL.md.
What does html-ppt-tech-sharing do?
It builds engineering presentations in HTML with keyboard navigation, presenter mode, 36 themes, and animations. Speaker notes go in a separate block and stay hidden from the slide.
Why doesn't navigation work in the presentation?
After copying index.html, the paths to base.css, animations.css, and runtime.js remain relative (../../../assets/...) and fail to resolve. Move the files into the project and rewrite the links, or inline the contents with <style> and <script> tags.
Source text
SKILL.md · Apache-2.0
---
name: html-ppt-tech-sharing
en_name: "Give an Engineering Tech Talk like a Staff Developer-Advocate"
zh_name: "像 Staff DevRel 一样做工程分享"
description: |
OpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. Built as a decision-grade AI literacy deck for engineers, dev community.
en_description: |
OpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. Built as a decision-grade AI literacy deck for engineers, dev community.
zh_description: |
像 Staff DevRel 一样做工程分享——一份可商业交付的AI 素养 Deck,围绕真实主题、证据链与决策目标组织。
tags:
- "ai-literacy"
- "enterprise-ai-copilot-rollout-brief"
- "ai"
- "copilot"
- "workflow"
- "decision-deck"
- "commercial-slide-agent"
- "html-ppt-tech-sharing"
triggers:
- "enterprise-ai-copilot-rollout-brief"
- "ai-literacy"
- "Give an Engineering Tech Talk like a Staff Developer-Advocate"
- "像 Staff DevRel 一样做工程分享"
- "ai"
- "copilot"
- "workflow"
- "html deck"
- "html slides"
od:
mode: deck
upstream: "https://github.com/lewislulu/html-ppt-skill"
preview:
type: html
entry: index.html
design_system:
requires: false
speaker_notes: true
animations: true
category: "ai-literacy"
scenario: "ai"
example_prompt: "Create \"Give an Engineering Tech Talk like a Staff Developer-Advocate\" as a decision-grade AI literacy deck in this template's own visual system. Subject: OpenDesign internals: how the agent stream, sandbox, and artifacts work — an engineering deep-dive talk. Audience: engineers, dev community. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce the slide plan, written slides, visual direction, speaker-ready structure, and a critic pass against this rubric: does the deck make AI implementation concrete enough to fund."
---
# HTML PPT · Tech Sharing
A focused entry point into the [`html-ppt`](../html-ppt/SKILL.md) master skill that lands the user directly on the **`tech-sharing`** 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 `tech-sharing` (see the upstream [full-decks catalog](../html-ppt/references/full-decks.md) for screenshots and rationale).
## How to author the deck
1. **Read the master skill first.** All authoring rules live in
[`design-templates/html-ppt/SKILL.md`](../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.
2. **Start from the matching template folder:**
`design-templates/html-ppt/templates/full-decks/tech-sharing/` — copy `index.html` and
`style.css` into the project, keep the `.tpl-tech-sharing` body class.
3. **Bring the shared runtime with the template.** The upstream
`index.html` links the shared CSS/JS via `../../../assets/...` because it
sits three folders deep inside `design-templates/html-ppt/templates/full-decks/`.
Once you copy `index.html` into the project, those parent-relative URLs
no longer resolve and `base.css`, `animations.css`, and `runtime.js`
will 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`, and
`design-templates/html-ppt/assets/runtime.js` into a project-local
`assets/` (with `assets/animations/animations.css`), then rewrite the
four `<link>`/`<script>` tags in `index.html` from
`../../../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>` containing `runtime.js`. Yields a single
self-contained `index.html`.
Either way, do not ship the upstream `../../../assets/...` URLs
verbatim into a project artifact — they only work in-tree.
4. **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/*.css`
via `<link id="theme-link">` and let `T` cycle.
5. **Replace demo content, not classes.** The `.tpl-tech-sharing` scoped CSS only
recognises the structural classes shipped in the template — keep them.
6. **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`](https://github.com/lewislulu/html-ppt-skill). The
LICENSE file ships at `design-templates/html-ppt/LICENSE`; please keep it in place when
redistributing.
© nexu-io · Apache-2.0 · nexu-io/open-design