Today's Agent Skill: Automated Weekly Status Reports
What It Does
Every Friday, knowledge workers lose 30–60 minutes hunting through Slack threads, ticket queues, and email chains just to write a status report nobody reads carefully anyway. The problem isn't the writing — it's the archaeology. An agent that does the digging and drafts the report hands you back your Friday afternoon.
How It Works
The skill ingests raw inputs — a bullet-point brain dump, Jira/Linear ticket IDs, or pasted Slack excerpts — and transforms them into a structured status report following your organization's template. It categorizes work into completed, in-progress, and blocked buckets, surfaces key metrics and decisions, and flags any items that need escalation before the next reporting cycle.
How to Deploy It
Add this skill to any SKILL.md-compatible agent by dropping the SKILL.md block below into your agent's skills directory and referencing it in your agent config. Trigger it each Friday by pasting your raw notes into the agent with the phrase 'status report' — or wire it to a cron that pulls from your project tracker automatically.
SKILL.md — Ready to Deploy
## Description
Generates a formatted weekly status report from unstructured inputs: bullet-point notes, ticket IDs, pasted Slack messages, or a free-form brain dump. Produces a report ready to paste into email, Confluence, or a Slack channel.
## Trigger
Activates when the user input contains 'status report', 'weekly update', 'Friday report', or 'draft my update'.
## Input
- **Required:** Raw notes in any format (bullets, prose, ticket IDs, Slack paste)
- **Optional:** Recipient audience (team, exec, client), reporting period (defaults to current week), custom template or section names
- **Optional:** Blockers or escalations to highlight
## Steps
1. Parse all input and identify discrete work items, decisions, and blockers.
2. Categorize each item: Completed, In Progress, Blocked, or Next Week.
3. Within each category, sort by impact — highest-visibility items first.
4. Identify any items marked as blocked or at-risk and flag them in a dedicated Escalations section.
5. Extract key metrics if present (e.g., tickets closed, revenue moved, users onboarded).
6. Draft report using the standard template (see Output Format).
7. Add a one-sentence executive summary at the top suitable forCopy the full SKILL.md and drop it into your agent's skills directory to activate this skill.