Weekly Update
OpenDesign's weekly metrics standup: this week's numbers, the one anomaly, and the single decision it forces. Built as a decision-grade data & finance deck for ops & growth team.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Weekly Update when an AI agent needs a reusable SKILL.md workflow for this job: OpenDesign's weekly metrics standup: this week's numbers, the one anomaly, and the single decision it forces. Built as a decision-grade data & finance deck for ops & growth team.
When not to use it
Skip Weekly Update when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/weekly-update # Save SKILL.md to ~/.claude/skills/weekly-update/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/weekly-update/SKILL.md. For a shared project, commit the folder at .claude/skills/weekly-update/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Weekly Update skill for this task: Read DESIGN.md. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Weekly Update Deck Skill
Produce a single-file horizontal-swipe HTML deck for a weekly team update.
## Workflow
1. Read DESIGN.md. 2. Identify squad name, week range, and audience (squad-internal vs cross-functional). 3. Slides: 1. Cover (squad + week + author + date) 2. Headline (one sentence + one number that matters this week) 3. What shipped (3–5 items, link-style affordance) 4. In flight (3–5 items, owner avatars) 5. Blocked (1–3 items + clear ask) 6. Metrics that matter (1–2 inline charts) 7. Asks for next week (named owners) 8. Closing + thanks 4. Arrow keys or click navigation. Each slide is 100vw wide.
## Output contract
``` <artifact identifier="weekly-update-w42" type="text/html" title="Weekly Update — Growth · W42"> <!doctype html>...</artifact> ```
Intended uses
- Read DESIGN.md.
- Identify squad name, week range, and audience (squad-internal vs cross-functional).
- Slides:
- Cover (squad + week + author + date)
- Headline (one sentence + one number that matters this week)
- What shipped (3–5 items, link-style affordance)
- In flight (3–5 items, owner avatars)
- Blocked (1–3 items + clear ask)
- Metrics that matter (1–2 inline charts)
- Asks for next week (named owners)
- Closing + thanks
- Arrow keys or click navigation. Each slide is 100vw wide.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.