A configurable Claude skill that drafts any recurring update — weekly status reports, biweekly check-ins, sprint retros, monthly research roundups, quarterly leadership briefings, anything cyclical. The format is fully defined by your YAML config; the skill makes no assumptions about sections, status conventions, or sources.
Most teams write the same update over and over again. The structure is stable — same sections, same audience, same cadence — but the content changes every cycle. People spend an hour or two each cycle re-typing structure they already know.
update-kit captures the stable parts in a config file (sections, sources, tone, sensitivities, output format) and pulls the changing parts from wherever your team keeps them (Notion, Slack, Drive, Gmail, pasted notes, attached PDFs). You write the config once, then each cycle is a one-line prompt.
It's not opinionated about format. It works for:
- Weekly engineering status with R/Y/G indicators
- Monthly research roundups with narrative prose and no statuses
- Sprint retros with start/stop/continue
- Quarterly board updates with highlights/metrics/risks/asks
- Daily standups with per-person bullets
- Anything else you can describe in a config
- Download the latest
update-kit.skillfrom Releases - In Cowork (or any Claude surface that supports skills), open the skills panel and click Save skill
- Drop the file in and confirm install
- Copy
YOUR-CONFIG.template.yamlinto your project folder (or Claude Project knowledge) and rename it to whatever you like — e.g.weekly-eng-config.yaml - Fill in your update's name, sections, cadence, sources, and tone
- (Optional) Pick a status convention from the presets in the template, or write your own
- Ask Claude:
"Draft this week's status update."
The skill finds your config, pulls source material from whatever you've enabled (or asks you to paste), and renders the draft in chat ready to copy into your destination.
If you skip the config step, the skill will ask you setup questions on the fly and offer to save your answers.
update-kit/
├── README.md # this file
├── LICENSE
├── SKILL.md # the skill Claude reads when triggered
├── YOUR-CONFIG.template.yaml # blank template
├── example-prompts.md # phrasings that trigger common workflows
└── examples/ # ready-to-adapt example configs
├── example-weekly-engineering.yaml
├── example-monthly-research-roundup.yaml
└── example-sprint-retro.yaml
Just ask Claude. Some triggers:
"Draft this cycle's update." "Draft this week's status report from these notes: [paste]" "Refresh the monthly research roundup. Pull from Notion." "Run update-kit."
The skill:
- Reads your config to know the structure
- Pulls from your configured sources (or the notes/files you provide)
- Drafts each section per your spec
- Uses placeholder language for anything you've flagged as sensitive
- Renders the draft in the output format your config specifies (default: chat)
- Flags any gaps where the source material was thin
- Invent metrics, dates, or names. If a fact isn't in the source you give it, it flags the gap rather than guessing.
- Auto-send. You always review before posting or sharing.
- Impose a structure your config doesn't define. The config is the contract.
- Engineering / SRE weekly status
- Sales pipeline updates
- Product team biweekly OKR check-ins
- Research team monthly roundups
- Sprint retros and post-mortems
- Quarterly board / leadership briefings
- Community manager weekly digests
- Customer success account reviews
- Standup / async daily updates
- Investor monthly notes
The three configs in examples/ cover three very different shapes. Use them as starting points for your own.
Issues and PRs welcome. If you've used update-kit for an interesting case and want to contribute an example config, please open a PR adding it to examples/ — those are the best documentation we have.
MIT — see LICENSE.