The last status report you'll write by hand

A Claude Code skill that writes your status report.

May 11, 2026

From my experience, status reporting costs on average two hours a week.

Artifact review, merged PR checks, chasing contributors for impact summaries. All of it manual… every single week.

So I built a Claude Code skill to handle it. And I’m sharing the full file here - drop it in, configure two variables, and run it.

What you need

Claude Code installed and running;
GitHub CLI (gh) authenticated with repo access;
Notion MCP connected to Claude Code (or swap for Google Drive, Jira, or M365 (more on that below);
GitHub handles of the contributors to report on.

The skill file

Save the following as SKILL.md inside ~/.claude/skills/weekly-reporter/SKILL.md.

# Weekly Reporter

> Compiles a weekly executive summary of impactful achievements for specified
> contributors by scouring Notion and git repositories. Use when generating
> status reports, impact summaries, or performance review inputs for individuals
> over a one-week period. Do not use for real-time status checks, daily
> standups, or when no contributor names or handles are provided.

## Configuration

REPO_SEARCH_PATH: ~/your-code/*   # glob — adjust to match your repo layout
LOOKBACK_DAYS:    7

Adjust REPO_SEARCH_PATH before running (e.g. ~/code/** to search recursively,
or ~/work/acme-* to target a specific org). The agent resolves the glob with
find $REPO_SEARCH_PATH -maxdepth 0 -type d before running any git commands.

<!--
SWAP THE DATA SOURCE — Notion is wired up below, but you can replace step 2
for any of these MCP integrations with minimal changes:

  Google Drive   — tools: search_files, list_recent_files, read_file_content
                   Best for: teams on Google Workspace (Docs, Slides, Sheets).

  Microsoft 365  — tools: search via the Microsoft Graph MCP server
                   (SharePoint, Teams messages, OneNote notebooks)
                   Best for: enterprise orgs on M365 / SharePoint.

  Jira           — tools: search_issues, get_issue via the Atlassian MCP server
                   Filter by assignee + updated date to pull completed tickets.
                   Best for: engineering teams tracking work in Jira sprints.

For code: GitHub (gh CLI) is shown below. GitLab users substitute glab.
-->

## Overview

This skill guides the agent in compiling an executive summary of achievements
for a given set of contributors over the last week.

## Workflow

1. Confirm Inputs: Ensure you have the list of contributors (names or GitHub /
   GitLab handles) and the target date range (default: last LOOKBACK_DAYS days).

2. Scour Notion:
   - Use the Notion MCP search tool to find pages authored by or mentioning
     the target contributors within the lookback window.
   - Fetch the full content of relevant pages.
   - Query recent meeting notes involving the contributors.
   - Prioritize pages with titles indicating progress, status, design, or
     impact (e.g. "Status Update", "Design Doc", "RFC", "Spec").

3. Analyze Code Contributions:
   - Resolve REPO_SEARCH_PATH to a list of git repositories with:
       find ~/your-code/* -maxdepth 0 -type d -exec test -d {}/.git \\; -print
   - For each repo, list recent commits:
       git -C {repo} log --author="{name}" --since="{LOOKBACK_DAYS} days ago" --oneline
   - GitHub: list merged PRs:
       gh pr list --author="{handle}" --state=merged --limit=20
     Inspect with: gh pr view {pr_number}
   - GitLab: substitute glab mr list / glab mr view
   - Only include merged / landed contributions — exclude drafts and open PRs.

4. Compile Executive Summary:
   - Synthesize findings from Notion and the repositories.
   - Structure with: Key Achievements, Code Contributions, Design & Documentation.
   - Focus on impact — not activity.

## Guidelines

- Focus on Impact: highlight what was achieved, unblocked, or delivered.
- Be Concise: summaries should be punchy and easy to scan. 1-2 sentences per
  item, mapping Action -> Impact -> Proof directly.
- Verify Dates: all activities must fall within the LOOKBACK_DAYS window.
- Prefer CLI for Code: use git and gh/glab directly — not web or API calls.

How to invoke it

Open a Claude Code session and run:

Use the weekly-reporter skill for the following contributors:
handle-1, handle-2, handle-3
Time range: last 7 days

It runs git log and gh pr list per contributor, searches Notion for relevant updates, and compiles the summary. Takes 2–4 minutes.

What the output looks like

Here’s the output from a run I did this week:

Weekly Report — May 3–10, 2026

Key Achievements

Shipped the core content asset for the weekly-reporter launch. Wrote and
iterated a full Substack draft — "I automated status reporting. This is what
I did with the time." — built around a personal management story (2 hours
reclaimed, how they were spent).

Validated the keepmomentum.eu market position with data. Completed a
comprehensive competitive analysis covering the $7.3B global coaching market
and the $1B+ AI coaching segment. Confirmed the target gap: no individual
practitioner is offering AI-assisted skill practice directly to engineering
managers. BetterUp leads the enterprise tier with $567M raised and holds
0.12% of the HCM market — the category is wide open.

Code Contributions

Commit   Date    Description
92f3c9d  May 9   Add Google Analytics 4 alongside existing Google Ads tag
f1b8749  May 9   Add email course section as soft secondary CTA

Both landed directly on the main branch. No open PRs.

Content & Documentation

Artifact                                        Type              Status
"I automated status reporting…"                 Substack draft    Draft — needs cold read
"I use AI to automate status reporting…"        Substack draft    Superseded by above
"I built an AI agent that handles my report"    LinkedIn post     Draft — scheduled May 20
Market analysis                                 Research doc      Complete

---

On tool calls: this run made 8 tool calls — 5 against Notion
(searches/fetches) and 3 against Bash (git commands + repo scan).

Two hours of manual work. Five minutes of review.

Configuring for other data sources

The skill ships with Notion wired up. The comment block at the top of the file shows exactly which MCP tools to swap for Google Drive, Microsoft 365, and Jira - change step 2 of the Workflow to point at the right tools, and the rest of the skill runs unchanged.

For anything else: if it has an MCP connector and you can search it by contributor and date, it can slot into step 2.

If you set it up and run into something, reply here. I’ll help you debug it.

Discussion about this post

Ready for more?