Weekly Status Report

Weekly status reports are essential but tedious. This recipe automates the entire process: an agent gathers workspace activity, compiles metrics, and posts a summary — every week, without anyone lifting a finger.

The Pattern

GATHER     → Query tasks, messages, documents from the past week
ANALYZE    → Calculate metrics and identify highlights
DISTRIBUTE → Post summary to a channel and/or create a document

Manual Version (One-Time)

Before automating, try it manually to dial in the format:

@Analyst compile a weekly status report for this week:

1. Tasks completed this week (by assignee)
2. Tasks started but not yet completed
3. New tasks created
4. Overdue tasks
5. Documents created or updated
6. Key decisions from channel discussions

Format as a structured document titled 
"Status Report — Week of [date]"

Review the output and adjust the instructions until you're happy with the format.

Automated Version

Step 1: Create the Automation Skill

Go to Settings > Skills and create a new automation skill:

• Name: Weekly Status Report
• Schedule: 0 17 * * 5 (Fridays at 5 PM)
• Channel: #general (where the summary posts)
• Tools: search_tasks, search_messages, search_documents, create_document, post_message

Step 2: Write the Instructions

Generate a weekly status report for the workspace:

1. TASKS
   - Query all tasks completed this week
   - Query all tasks created this week
   - Count tasks by state (open, in progress, waiting, completed)
   - List any overdue tasks

2. ACTIVITY
   - Count messages sent across all channels
   - Identify the most active channels
   - Note any new documents created

3. HIGHLIGHTS
   - Summarize the most significant completed tasks
   - Flag any blockers or overdue items

4. OUTPUT
   - Create a document titled "Status Report — Week of [today's date]"
   - Post a 3-bullet summary in this channel with a link to the full document

Keep the summary concise. Use tables for task lists.

Step 3: Attach to an Agent

Attach the skill to your Analyst or PM agent. The agent will run every Friday at 5 PM and post results to #general.

Customization

Per-Team Reports

Create separate automation skills for different teams:

# Engineering Team — posts to #engineering
Schedule: 0 17 * * 5
Instructions: Focus on tasks in the "Engineering" and "Infrastructure" 
task groups. Include PR and deployment activity from GitHub connector.

# Marketing Team — posts to #marketing  
Schedule: 0 17 * * 5
Instructions: Focus on tasks in the "Marketing" and "Content" 
task groups. Include content published and campaign metrics.

Different Frequencies

Adding Metrics from Databases

If you track KPIs in a database:

Also query the "Sales Metrics" database for:
- Total revenue this week
- New deals added
- Deals closed

Include these numbers in the Highlights section.

Including Connector Data

If GitHub is connected:

Also include from GitHub:
- PRs merged this week
- Issues opened vs closed
- Any critical issues still open

Report Archive

Each report is saved as a document, building a searchable archive over time. Query past reports:

@Assistant search documents for "Status Report" 
and compare the last 4 weeks of task completion rates. 
Are we trending up or down?

Tips

• Start manual, then automate — Run the report manually a few times to perfect the format before creating the automation skill
• Keep summaries short — The channel post should be 3-5 bullets. Full details go in the document.
• Use databases for tracking — If you want metrics over time, have the agent write key numbers to a database each week
• Review the first few runs — Check the automated output to catch any issues with the instructions
• Pin the latest report — Pin the most recent status report in the channel for easy access