html-ppt-weekly-report — Claude Code skill: what it does, install
html-ppt-weekly-report is a Claude Code skill that builds an HTML deck for OpenDesign’s weekly growth review. It covers stars, installs, and activation, with drivers and a recommended decision.
Apache-2.0 186 installs ★ 108,855 updated 2026-10-25
npx skills add nexu-io/open-design --skill html-ppt-weekly-report -a claude-codeWhat html-ppt-weekly-report does
The skill turns OpenDesign’s weekly growth review into a weekly-report HTML deck. It presents the metrics, identifies their drivers, and connects charts to decisions. The template comes from the open-design project.
Start by reading the master skill at design-templates/html-ppt/SKILL.md, then copy index.html and style.css from the weekly-report folder. Move the shared CSS and JavaScript files into the project’s assets/ directory and update their paths, or embed their contents in the HTML. The original ../../../assets/... links break after copying, so the deck will not activate and slide navigation will fail until the paths are fixed. Put speaker notes in notes blocks, not on the slides.
What it helps with
- build an HTML deck for a weekly growth review
- show changes in stars, installs, and activation
- connect charts to their drivers and recommended decisions
- copy the presentation template while keeping its asset paths valid
Example prompts for the agent
- Create an HTML deck for OpenDesign’s weekly growth review of stars, installs, and activation.
- Build a
weekly-reportpresentation and tie each chart to a decision. - Move the
weekly-reporttemplate into the project and fix its CSS and JavaScript paths.
How to install html-ppt-weekly-report
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-weekly-report -a claude-code2Manually: put the files in place
~/.claude/skills/html-ppt-weekly-report/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/html-ppt-weekly-report/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-weekly-report -a codex2Manually: put the files in place
.agents/skills/html-ppt-weekly-report/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-weekly-report -a cursor2Manually: put the files in place
.cursor/skills/html-ppt-weekly-report/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nexu-io/open-design design-templates/html-ppt-weekly-report/SKILL.md2Manually: put the files in place
.github/skills/html-ppt-weekly-report/SKILL.md1Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-weekly-report -a gemini-cli2Platform CLI
gemini skills install https://github.com/nexu-io/open-design --path design-templates/html-ppt-weekly-reportManually: put the files in place
.devin/skills/html-ppt-weekly-report/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add nexu-io/open-design --skill html-ppt-weekly-report -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-weekly-report
How do I install html-ppt-weekly-report in Claude Code?
Run npx skills add nexu-io/open-design --skill html-ppt-weekly-report -a claude-code. The skill file is available at ~/.claude/skills/html-ppt-weekly-report/SKILL.md.
What does html-ppt-weekly-report do?
It creates an HTML deck for OpenDesign’s weekly growth review, covering stars, installs, and activation alongside their drivers and a recommended decision.
What must change when copying the weekly-report template?
The ../../../assets/... paths only work from the template’s original location. After copying, update them to point to project-local assets or embed the CSS and JavaScript in the HTML.
Source text
SKILL.md · Apache-2.0
---
name: html-ppt-weekly-report
en_name: "Write a Weekly Growth Review like a Head of Analytics"
zh_name: "像分析负责人一样写每周增长复盘"
description: |
OpenDesign's weekly growth review: stars, installs, activation — the number, the driver, and the recommended move. Built as a decision-grade data & finance deck for growth & product team.
en_description: |
OpenDesign's weekly growth review: stars, installs, activation — the number, the driver, and the recommended move. Built as a decision-grade data & finance deck for growth & product team.
zh_description: |
像分析负责人一样写每周增长复盘——一份可商业交付的数据财务 Deck,围绕真实主题、证据链与决策目标组织。
tags:
- "data-finance"
- "product-analytics-deck"
- "finance"
- "kpi"
- "metrics"
- "decision-deck"
- "commercial-slide-agent"
- "html-ppt-weekly-report"
triggers:
- "product-analytics-deck"
- "data-finance"
- "Write a Weekly Growth Review like a Head of Analytics"
- "像分析负责人一样写每周增长复盘"
- "kpi"
- "finance"
- "metrics"
- "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: "data-finance"
scenario: "finance"
example_prompt: "Create \"Write a Weekly Growth Review like a Head of Analytics\" as a decision-grade Data, KPI & finance deck in this template's own visual system. Subject: OpenDesign's weekly growth review: stars, installs, activation — the number, the driver, and the recommended move. Audience: growth & product team. 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 every chart have a decision above it."
---
# HTML PPT · Weekly Report
A focused entry point into the [`html-ppt`](../html-ppt/SKILL.md) master skill that lands the user directly on the **`weekly-report`** 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 `weekly-report` (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/weekly-report/` — copy `index.html` and
`style.css` into the project, keep the `.tpl-weekly-report` 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-weekly-report` 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