New to Claude Skills? Learn how to install them →

nexu-io on GitHub

HTML PPT Weekly Report

Free

Create structured weekly reports for growth analysis.

by nexu-io84.9k stars on nexu-io/open-design
1 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What HTML PPT Weekly Report does

The HTML PPT Weekly Report skill is designed for teams focused on product growth and analytics. It provides a structured template that allows users to create visually appealing presentations summarizing key performance indicators (KPIs) such as stars, installs, and activation metrics. This skill serves as a focused entry point into the broader HTML PPT framework, specifically tailored for weekly reporting. By utilizing this skill, teams can streamline their reporting process, ensuring that critical data is presented clearly and effectively.

To get started, users should first familiarize themselves with the master HTML PPT skill, which outlines the authoring rules and best practices for creating presentations. The weekly report template is located within the designated folder, and users can easily copy the necessary HTML and CSS files into their projects. The skill emphasizes the importance of maintaining the correct file structure to ensure that all assets load correctly, which is crucial for the functionality of the presentations.

The skill also offers flexibility in terms of design, allowing users to choose from multiple themes to match their branding or presentation style. Additionally, it provides guidelines for adding speaker notes and customizing content without disrupting the underlying structure of the template. This makes it suitable for both technical and non-technical users who need to produce professional-grade reports quickly and efficiently.

Overall, the HTML PPT Weekly Report skill is an essential tool for product and growth teams looking to enhance their data presentation capabilities. It simplifies the process of creating informative and visually appealing reports, enabling teams to make data-driven decisions effectively.

When to use it

Use this skill when you need to generate a weekly report that summarizes key performance metrics for your product or service.

When not to use it

This skill may not be suitable for one-off presentations or when advanced customization beyond the provided templates is required.

What you can build with it

Weekly Growth Review

Use this skill to create a weekly report that summarizes key metrics like installs and activations for your product.

Team Performance Analysis

Generate a decision-grade deck for your product team to review performance and make data-driven decisions.

KPI Presentation for Stakeholders

Prepare a visually appealing presentation of KPIs to share with stakeholders during weekly meetings.

How to install HTML PPT Weekly Report

View source

1. Install with the skills CLI

npx skills add nexu-io/open-design/html-ppt-weekly-report --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by nexu-io

HTML PPT · Weekly Report

A focused entry point into the html-ppt 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 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 — 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. The LICENSE file ships at design-templates/html-ppt/LICENSE; please keep it in place when redistributing.

Frequently asked questions about HTML PPT Weekly Report

Similar skills