I Automated My Weekly Status Report. It Took 20 Minutes to Set Up.

Every Friday at 4pm, I would open a blank document and stare at it. I knew what I'd done that week. I just had to find a way to describe it that made it sound coherent and forward-looking without being either dishonest or exhausting to write. Forty-five minutes later, I'd have a status report.

My manager would skim it in two minutes. My skip-level might read the executive summary. The rest went into a folder where reports go to be forgotten.

I automated it. Here's exactly what I built and how long it actually took.

The Problem With Status Reports

The reason status reports are painful isn't that you don't know what you did. It's the translation layer. You need to take a week of scattered activity, half-finished tasks, blocked items, and ad-hoc meetings, and turn it into something that reads as structured, purposeful, and professional. That translation is genuinely cognitively expensive. It's not the kind of thinking that produces value, but it requires enough focus that you can't just phone it in.

A Claude skill is perfect for this because the translation layer is exactly what good prompt engineering handles.

The Skill Structure

The skill takes a simple text dump as input. No special formatting required. Just a brain dump of everything I did that week: tasks I completed, things that are blocked, things I'm working on next week, and any metrics worth including.

The output is a formatted status report with five consistent sections: Executive Summary (three sentences), Completed This Week (with brief context on each item), In Progress (with current status and next action), Blockers and Dependencies (flagged clearly), and Next Week's Priorities.

Here's a condensed version of the core prompt structure:

You are a professional technical writer specializing in engineering status reports.

Given a set of raw weekly notes from a software engineer, produce a clean,
professional status report in the following format:

## Executive Summary
[2-3 sentences summarizing the week's impact, not just activity]

## Completed This Week
[Bulleted list, each item with a brief sentence of context]

## In Progress
[Each item with current status and specific next action]

## Blockers
[Flagged items with what's needed to unblock]

## Next Week
[Top 3-5 priorities with brief rationale]

Rules:
- Write in third person ("The team completed..." or "Work continued on...")
- Lead with business impact where possible, not technical detail
- If notes are ambiguous, make a reasonable inference and note it with [inferred]
- Keep total length under 400 words

The Before and After

Before: 45 minutes of staring, writing, editing, second-guessing the tone, checking the word count, wondering if I'd forgotten anything important.

After: I spend 10 minutes on Friday afternoon writing a quick brain dump in a notes app. No formatting, no structure required. Paste it into the skill. Get a draft back in about 20 seconds. Spend 5 minutes reviewing and tweaking. Done.

The 10 minutes I spend writing notes is actually more valuable than the 45 minutes I used to spend polishing prose. The notes capture what actually happened. The skill handles the presentation.

What It Took to Set Up

Twenty minutes, genuinely. Most of that was writing three example reports in my actual style so I could calibrate the output. The first draft of the prompt was too formal. I added a line specifying "conversational but professional, not corporate-speak" and it got much better. After two weeks of using it, I made one small tweak to how it handles blocked items. That's it.

If building your own isn't how you want to spend your time, there are ready-to-use reporting skills on SkillsLib that do exactly this. Some are tailored for engineering teams, some for project management, some for client-facing work. Browse and pick one close to your context, then customize from there.

The Friday afternoon status report is still happening. I've just stopped being the one who writes it.