Today's Agent Skill: Auto-Generate Your Weekly Status Report
What It Does
Most professionals spend 20–40 minutes every Friday composing a status update that reads like a chore — cherry-picking wins from scattered notes, Slack threads, and calendar events. By the time it's sent, half the context is already fuzzy. This skill flips that: the agent drafts the report for you, pulling from your task list, completed items, and blockers, so you spend two minutes editing instead of twenty writing.
How It Works
The skill scans a structured input (task list, completed items, blockers, upcoming priorities) and renders a clean weekly status report in a consistent format. It categorizes work into Completed, In Progress, Blocked, and Next Week sections, surfaces metrics where available, and flags anything overdue. Output is ready to paste into email, Slack, or a project management tool.
How to Deploy It
Drop the SKILL.md content into any SKILL.md-compatible agent's skill directory and trigger it each Friday by passing your task dump as input — either pasted directly or piped from a task manager export. For full automation, wire it to a cron-style scheduler that pulls from your task tool's API and fires at 4:30 PM every Friday.
SKILL.md — Ready to Deploy
## Description
Generates a structured weekly status report from a raw task list and notes. Designed for individual contributors and managers who want a consistent, professional update without the manual writing overhead.
## Trigger
User says: "weekly status", "generate my status report", "draft my Friday update", or provides a task dump with the phrase "status report".
## Input
- **completed_tasks**: List of tasks finished this week (bullet list or numbered)
- **in_progress**: Tasks currently active
- **blockers**: Anything stalled and why
- **next_week**: Planned priorities for the coming week
- **optional — metrics**: Any numbers worth surfacing (PRs merged, tickets closed, revenue touched, calls made)
- **optional — tone**: "executive" (tight, metric-heavy) or "team" (conversational, context-rich). Defaults to "team".
## Steps
1. Parse input into four canonical buckets: Completed, In Progress, Blocked, Next Week.
2. If metrics are present, prepend a one-line headline stat (e.g., "Closed 7 of 9 sprint tickets").
3. For each Blocked item, append a one-sentence ask or ETA if derivable from context.
4. Apply tone setting: executive mode uses bullet fragments; team mode uses briefCopy the full SKILL.md and drop it into your agent's skills directory to activate this skill.