Guide · Agent skill
How to use the Weekly Update Deck agent skill (weekly-update)
Updated · written with AI from the project's own documentation and checked against our catalogue data
Weekly Update Deck is an agent skill, a set of instructions that teaches an AI agent how to produce a specific kind of output. This one tells the agent to format a team's weekly status report as a short horizontal-swipe slide deck written in HTML. This guide explains what the skill does, how to install it, how to ask for a deck in plain language, and what to watch for before sharing the result.
Weekly Update Decknexu-io/html-anything · Apache-2.0 Download the skill Quick start
- 1Download the package. Download the ZIP from this page and unzip it to get SKILL.md and example.html.
- 2Place the skill folder. Unzip into ~/.claude/skills/ for personal use or into .claude/skills/ in a project folder.
- 3Or upload it in the Claude apps. Go to Settings → Capabilities → Skills and upload the skill there.
- 4Gather your weekly content. List shipped items with owners, in-progress items with progress, blockers, metrics with last week's values, and asks.
- 5Ask for the deck in plain language. Request a weekly update deck for your team and include the content for each section.
- 6Review the HTML file. Open the output in a browser, test the arrow-key navigation and check that no sensitive information is included.
What the weekly-update skill makes the agent do
The skill is a template for a fixed weekly status structure. When it is active, the agent builds a deck of 6-8 slides in this order: Cover (week number, team and a one-line theme), Shipped (list of completed work with owners), In flight (items with progress bars), Blocked (blockers in red callouts), Metrics (KPI cards in a grid with week-over-week comparison), Asks (a list of requests) and a Thanks closing slide.
The output is a standalone HTML file. Viewers move between slides with the keyboard left and right arrow keys, and the current slide is reflected in the page URL through the hash.
Install the Weekly Update Deck skill
Download the ZIP from this page and unzip it. The package contains two files: SKILL.md, which holds the instructions, and example.html, a sample of the output.
You have two options. For a personal setup, unzip the folder into ~/.claude/skills/. For a single project, unzip it into the project's .claude/skills/ folder.
In the Claude apps you can instead upload the skill under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Project: .claude/skills/ inside your project folder
- Claude apps: Settings → Capabilities → Skills
Trigger the skill with a natural request
You do not need a special command. Describe the update you want in ordinary words and mention the weekly status, team update or deck. The agent should pick up the skill from the request and follow its structure.
Give the agent the raw material for each section: what shipped and who owned it, what is in progress and roughly how far along it is, what is blocked, the key metrics this week and last week, and what you need from others. The more specific the input, the cleaner the deck.
- Make a weekly update deck for Team Atlas, week 14. Theme: stabilising the release pipeline.
- Turn these notes into the weekly status slides: shipped, in progress with percentages, blockers, and KPIs compared with last week.
Example inputs and what you get back
A useful prompt lists the content for each slide. For example, under Shipped you might list three items with owner names; under Blocked, one item with the reason it is stuck. The agent maps these into the cover, list, progress bar, red callout, KPI card and asks slides.
Open example.html from the package to see the expected look before you run your own week through the skill.
What the skill needs and safety notes
The source lists no required dependencies. The skill does not run scripts and does not use the network, so it only shapes the agent's written output.
The output is a standalone HTML file that you must host and share yourself. Because of this, do not put sensitive internal metrics or blockers into a deck that will leave the team, and check the file before you send it.
- Runs scripts: no
- Uses network: no
- Check metrics and blockers before sharing outside the team
Tips for better weekly decks
Keep each slide to the template's short format. The skill is limited to 6-8 slides, so it suits a status update rather than a detailed report. If you need long documentation, use a different format.
Send the same structure every week. Consistency is the main benefit, so reuse the same team name and section order, and provide last week's numbers so the metric cards can show the comparison.
- Use the arrow keys to test the deck before sending it.
- Keep blocker descriptions specific so the red callouts are useful.
- Limit asks to a short, concrete list.
What people use it for
- Sending a weekly status deck to stakeholders who prefer visual slides over email.
- Preparing a recurring team update with the same section order every week.
- Summarising shipped work, blockers and asks for a manager review meeting.
- Creating a visual alternative to a plain document-based status report.
Frequently asked questions
Is the weekly-update skill free to use?
The source states the skill is licensed under Apache-2.0. The listing does not state pricing for the skill itself, so check the project's licence files for the terms that apply.
What do I need to install the weekly-update skill?
The source lists no requirements. Download the ZIP, unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it under Settings → Capabilities → Skills in the Claude apps.
Does the skill run scripts or access the internet?
No. The source says it runs no scripts and uses no network. It only guides the agent to write the HTML deck.
How many slides does the weekly update deck have?
The template produces 6-8 short slides in a fixed order: cover, shipped, in flight, blocked, metrics, asks and thanks.
Can I use this for a long report or detailed documentation?
Not well. The skill is designed for short status updates, so long-form reports or detailed documentation are a poor fit.
How do I view or present the generated deck?
Open the HTML file in a browser. Viewers switch slides with the left and right arrow keys, and the current slide appears in the URL hash.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are a team lead or project manager who sends a recurring status update and wants a clean, consistent visual format. Pick a different tool if you need long reports, detailed documentation, or a way to share sensitive metrics safely, since you must host and distribute the HTML file yourself.
Download the skill