Today's Agent Skill: Automated Weekly Status Report
What It Does
Every Friday, someone on your team spends 20–30 minutes hunting through Slack threads, Jira boards, and email chains to write a status report that nobody reads closely anyway. The information exists — it's just scattered. An agent can gather it, synthesize it, and deliver a clean report before your first coffee.
How It Works
The skill pulls from up to three configurable sources (a project tracker, a communication channel log, and a calendar), extracts completed items, blockers, and upcoming milestones, then formats them into a structured weekly update. It applies a consistent template so reports stay scannable and comparable week over week.
How to Deploy It
Drop the SKILL.md content into your agent's skills directory and register it in your agent config under the trigger phrase 'weekly status' or bind it to a Friday 4 PM cron. Point the three source fields at your actual tools (Jira, Linear, Notion, Slack export — whatever you use) in the Input section.
SKILL.md — Ready to Deploy
## Description
Generates a structured weekly status report by synthesizing completed work, active blockers, and upcoming priorities from configured project and communication sources. Produces a consistent, scannable format suitable for team leads, stakeholders, or personal accountability.
## Trigger
- Phrase: "weekly status", "generate status report", "end of week report"
- Schedule: Friday 4:00 PM (recommended cron binding)
## Input
- `project_source` (required): URL or export path for the project tracker (Jira, Linear, Notion, GitHub Issues, etc.)
- `comms_source` (optional): Slack channel export, email thread dump, or standup log covering the past 7 days
- `calendar_source` (optional): Calendar export or upcoming meetings list for the next 7 days
- `team_name` (optional): Label for the report header (defaults to "Team")
- `report_period` (optional): ISO date range; defaults to Mon–Fri of the current week
## Steps
1. Retrieve and parse the project source; extract items closed/merged/completed this week.
2. Identify items that are overdue, blocked, or flagged with a blocker label.
3. Extract items scheduled or planned to start next week.
4. If comms_source is provided, scan forCopy the full SKILL.md and drop it into your agent's skills directory to activate this skill.