Today's Agent Skill: Automated Weekly Status Report
What It Does
Every Friday, knowledge workers lose 30–45 minutes manually hunting through Slack threads, task trackers, and email to piece together a status update nobody reads closely anyway. The cognitive overhead of context-switching back through a week's worth of work is real — and entirely automatable. This skill drafts your weekly status report for you, ready to send or lightly edit.
How It Works
The skill pulls your completed tasks, blockers, and notes from a configured source (Notion, Linear, a plain text scratch file, or pasted input), then synthesizes them into a structured status report using a consistent template your team already expects. It categorizes work into Done / In Progress / Blocked / Next Week buckets, surfaces metrics if present, and flags any items that need explicit stakeholder attention.
How to Deploy It
Drop SKILL.md into your agent's skills directory and trigger it each Friday afternoon with 'draft my weekly status' — the agent will ask for your source data if none is auto-connected. For fully automated runs, wire it to a Friday 4 PM cron that reads your task tracker via an existing MCP integration.
SKILL.md — Ready to Deploy
## Description
Drafts a structured weekly status report from raw task notes, completed tickets, or pasted weekly activity. Output is ready to send with minimal editing.
## Trigger
- "draft my weekly status"
- "write my Friday update"
- "generate status report for this week"
- "summarize my week for the team"
## Input
Accept one or more of the following:
- Pasted raw notes or bullet list of work done
- Linear / Jira / Notion task list (via MCP or pasted export)
- Free-form description of the week
- Optional: recipient context (manager, whole team, exec summary)
If no input is provided, prompt: "Paste your notes, completed tasks, or a quick brain-dump of the week."
## Steps
1. Parse all input and extract distinct work items, blockers, and forward-looking notes.
2. Categorize each item into one of four buckets: ✅ Done, 🔄 In Progress, 🚧 Blocked, 📅 Next Week.
3. Identify any items that require explicit stakeholder action or decision (flag these).
4. Pull any metrics or quantitative results mentioned (e.g., "closed 12 tickets", "response rate 34%") and surface them in the Done section.
5. Draft using the output format below.
6. If recipient context was provided, adjust tone (exec Copy the full SKILL.md and drop it into your agent's skills directory to activate this skill.