/weekly-status-report
Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities. Use when the user says "write my status report", "weekly update", "summarize my week for my
$ npx -y skills add sgharlow/claude-code-recipes --skill weekly-status-report --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/weekly-status-report
Context preview
The summary Claude sees to decide when to auto-load this skill.
Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities. Use when the user says "write my status report", "weekly update", "summarize my week for my
SKILL.md
weekly-status-report.SKILL.mdname: weekly-status-report
description: Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities. Use when the user says "write my status report", "weekly update", "summarize my week for my manager", or pastes a raw dump of what happened this week.
Weekly Status Report
Synthesize a week of scattered raw inputs into one scannable, audience-ready status report. Report only what the inputs support — never invent accomplishments, metrics, or dates, and never upgrade routine work into a highlight without evidence of impact.
Steps
1. Get the raw material. Accept pasted notes, forwarded emails, task-tool exports, meeting notes, and last week's report if available. Ask for: report period, the user's role, the audience (manager / leadership / client), and any required template. 2. Classify every item, citing the input it came from:
- **Highlights** — only items with stated impact (shipped, resolved, approved, measured).
- **Progress** — grouped by project/workstream, with % or state only if the inputs give it.
- **Blockers & risks** — each with severity (High/Medium/Low) and what unblocks it. If the
inputs don't support a severity, ask rather than guess.
- **Next week** — priorities, deadlines, dependencies.
3. Render the report under one page: HIGHLIGHTS (3–5) → PROGRESS → BLOCKERS & RISKS (table: `Item | Severity | Status | Needed`) → NEXT WEEK → optional NOTES/FYI. Bold key items. 4. Verify before presenting: every claim traces to a line of input; anything the user's raw notes mention that was dropped is listed back ("omitted: …") so nothing disappears silently. If last week's report was provided, note carryover items explicitly. 5. Offer audience variants from the same material on request (3-bullet skip-level version, client-toned version, team-detail version) — same facts, different framing.
Constraints
- The user reviews and sends the report themselves; never deliver it anywhere.
- No metric appears unless it is in the inputs verbatim; flag wanted-but-missing metrics.
- If the inputs are thinner than ~5 items, say so and produce a short-form update instead of
padding a full template.
Full walkthrough, examples, and variations: `recipes/Recipe-002-Weekly-Status-Report-Generation.md`.
Read more
name: weekly-status-report description: Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities. Use when the user says "write my status report", "weekly update", "summarize my week for my manager", or pastes a raw dump of what happened this week.
Weekly Status Report
Synthesize a week of scattered raw inputs into one scannable, audience-ready status report. Report only what the inputs support — never invent accomplishments, metrics, or dates, and never upgrade routine work into a highlight without evidence of impact.
Steps
1. Get the raw material. Accept pasted notes, forwarded emails, task-tool exports, meeting notes, and last week's report if available. Ask for: report period, the user's role, the audience (manager / leadership / client), and any required template. 2. Classify every item, citing the input it came from:
- **Highlights** — only items with stated impact (shipped, resolved, approved, measured).
- **Progress** — grouped by project/workstream, with % or state only if the inputs give it.
- **Blockers & risks** — each with severity (High/Medium/Low) and what unblocks it. If the
inputs don't support a severity, ask rather than guess.
- **Next week** — priorities, deadlines, dependencies.
3. Render the report under one page: HIGHLIGHTS (3–5) → PROGRESS → BLOCKERS & RISKS (table: `Item | Severity | Status | Needed`) → NEXT WEEK → optional NOTES/FYI. Bold key items. 4. Verify before presenting: every claim traces to a line of input; anything the user's raw notes mention that was dropped is listed back ("omitted: …") so nothing disappears silently. If last week's report was provided, note carryover items explicitly. 5. Offer audience variants from the same material on request (3-bullet skip-level version, client-toned version, team-detail version) — same facts, different framing.
Constraints
- The user reviews and sends the report themselves; never deliver it anywhere.
- No metric appears unless it is in the inputs verbatim; flag wanted-but-missing metrics.
- If the inputs are thinner than ~5 items, say so and produce a short-form update instead of
padding a full template.
Full walkthrough, examples, and variations: `recipes/Recipe-002-Weekly-Status-Report-Generation.md`.
Claude Code artifacts graded by Skill Crossroads — click the badge for the evidence-cited scorecard. Your Complete Guide to AI-Powered Productivity
Repo: sgharlow/claude-code-recipes
Other skills on claude-code-recipes.
- /data-cleanup
Clean and standardize messy tabular data (CSV, spreadsheet paste, system exports) into an analysis-ready dataset — consistent dates and names, typed columns, duplicates identified, missing values handled explicitly. Use when the user says "clean this data", "standardize this
Open skill - /meeting-notes-to-actions
Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts. Use when the user says "process my meeting notes", "extract action items", "who owns what from this meeting", or "draft the follow-ups" — or pastes messy
Open skill - /qc-checklist
Turn a process description into an operational quality-control checklist — binary pass/fail checks, acceptance criteria, critical-vs-routine tiers, and failure modes with catch-points. Use when the user says "build a QC checklist", "standardize how we review X", "acceptance
Open skill - /research-synthesis
Synthesize multiple sources — articles, reports, notes, transcripts — into one structured brief with themes, agreements, contradictions, and gaps. Use when the user says "synthesize this research", "combine these sources", "what do these articles agree on", or has a folder of
Open skill - /summarize-document
Summarize a long document into an executive summary, key points, and role-specific implications. Use when the user says "summarize this document", "give me the key points", "do I need to read this?", or drops a long PDF, report, or contract and asks what matters in it.
Open skill