name: send-weekly-update
description: Draft a skimmable weekly update email with key numbers first and an inline HTML detail table. Use when someone needs to summarize project or client activity, upcoming work, scheduling status, and next steps from authorized source material.

---
name: send-weekly-update
description: Draft a skimmable weekly update email with key numbers first and an inline HTML detail table. Use when someone needs to summarize project or client activity, upcoming work, scheduling status, and next steps from authorized source material.
---

# Send Weekly Update Email

Turn the week's source material into a concise email that a busy recipient can understand at a glance. This skill prepares a draft; it does not send messages or change a source sheet unless the user explicitly asks and the required tools and permissions are available.

## Before starting

Ask for or identify:

- the recipient or audience;
- the reporting period and project, account, or workstream;
- the source sheet, report, notes, metrics, or communications to use;
- whether a source sheet or detail report needs to be prepared or refreshed first;
- the required tone, sending channel, and deadline.

Do not infer confidential facts from a project name. If source material is missing, say exactly what is missing and continue only with clearly labeled assumptions. Never include private information unless it is authorized for the intended recipient.

## Workflow

1. If a source sheet or report is requested, prepare or refresh it first. Verify the underlying counts, names, dates, and status before drafting the email. Do not link to the sheet in the email unless the user explicitly requests a link.
2. Gather the supplied or explicitly authorized source material. Keep a short source list and note the date of each source.
3. Extract the categories that apply to the work: completed items and names, upcoming items and counts, scheduled or pending work, decisions, blockers, and next steps.
4. Separate facts from interpretation. Resolve contradictions by showing the conflict and asking for confirmation.
5. Draft the email with the key numbers up front. List names only for completed items unless the user asks for more detail. Keep upcoming or pending items as counts when names or scheduling details would create unnecessary noise.
6. Put the detailed breakdown in an inline HTML table when the channel supports HTML. Use a readable table with a light-gray header, 1px borders, 13px table text, and columns appropriate to the source data, such as team, date, status, and outcome.
7. Keep the body short. Do not add a separate deliverables section, an items-to-flag section, or a scheduling call to action unless the user asks for one. The detail table should carry the supporting information.
8. Use a plain-ASCII subject line. Avoid em dashes, en dashes, curly quotes, and other Unicode punctuation in the subject.
9. End with a review checklist: facts to confirm, missing owners or dates, recipient-sensitive content, and whether the source sheet is accurate and up to date.

## Quality bar

- Key numbers appear before supporting context.
- Completed, upcoming, and pending counts reconcile to the verified source.
- The reader can tell what changed and what happens next without opening another document.
- The inline table is valid HTML and readable on desktop and mobile.
- The subject uses plain ASCII punctuation.
- Private information is included only when the user has authorized it for the intended audience.

## Output modes

If the user asks for a plan, return the source-check and proposed email structure without pretending the update has been sent. If the user asks for a draft, return the subject, HTML body, and short fact-check list. If the user asks to send it and the email tool supports HTML, use its HTML content mode; confirm the final audience, channel, and content before taking the sending action.