How to use the Weekly Metrics Standup Deck agent skill

What an agent skill is and what this one makes the agent do

An agent skill is a folder containing a SKILL.md file of instructions that an AI agent reads when a task matches the skill. This skill, named weekly-update, tells the agent how to build a weekly metrics update.

When installed, the agent produces a self-contained HTML deck that swipes horizontally with arrow keys. The deck follows a fixed outline: cover, headline number, what shipped, work in progress, blockers, key metrics charts, asks for next week, and a closing slide.

The skill's main emphasis is that each chart should have a decision attached to it, so the update leads to action rather than just reporting numbers.

• Cover slide with squad, week, author and date
• Headline slide with one sentence and one number that matters this week
• What shipped (3 to 5 items), in flight (3 to 5 items), and blocked (1 to 3 items with a clear ask)
• One or two inline metrics charts
• Asks for next week with named owners
• Closing slide with thanks

Install the weekly-update skill

Download the ZIP from the skill's page in this directory, then unzip it into one of two locations. Use ~/.claude/skills/ to make the skill available across your projects, or use a project's .claude/skills/ folder to limit it to that project.

If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

The skill's files are example.html and SKILL.md. The skill's workflow starts by reading a DESIGN.md design system file in the project, so make sure your project has one.

• Option A: unzip into ~/.claude/skills/ for all projects
• Option B: unzip into a project's .claude/skills/ folder for one project
• Option C: upload in the Claude apps under Settings → Capabilities → Skills

Check what the skill needs before you start

The skill needs an AI agent that can read SKILL.md and a DESIGN.md design system file in the project. The source files do not list any API keys or external accounts.

You must supply the numbers yourself. The skill structures content but does not check data sources, so verify every figure before it goes on a slide.

• An agent that can read SKILL.md
• A DESIGN.md file in the project, which the workflow reads first
• Your own verified numbers, squad name, week range and audience

Trigger the skill with natural requests

Describe the deck you want in plain language and mention the weekly update. The skill's trigger terms include phrases such as html deck, html slides, kpi, metrics and finance, so these words help the agent pick it up.

The agent will ask for the squad name, week range and audience (squad-internal or cross-functional) if you have not given them. Have your figures ready so you can paste them in.

• "Make a weekly metrics standup deck for the growth squad, week 42, from these numbers."
• "Build an HTML slide deck for our ops update: shipped, in flight, blockers, and the KPI charts."
• "Turn this weekly status into an HTML deck with a decision attached to each chart."

Review the output and present it

The deck is a single HTML file. Open it in a browser and move between slides with the arrow keys or by clicking. Each slide is as wide as the browser window.

Read each chart and confirm that the decision above it matches what your team will actually do. If a chart has no decision, either add one or remove the chart.

• Open the HTML file in a browser and use the arrow keys to navigate
• Check every number against your source data
• Confirm each chart has a decision attached

Safety notes and limits

According to the source, this skill does not run scripts and does not use the network. No API keys or external accounts are listed.

The output is a single HTML file, not a PowerPoint or Google Slides file. If you need one of those formats, this skill is not the right tool.

• Runs scripts: no
• Uses network: no
• Output format: single HTML file only