# Wrapup
> End-of-day wrap-up that audits what Claude did automatically and what you did manually, then generates a beautiful HTML report with tomorrow's priority.
- Skill: `az9713/wrapup` (Agent Skill)
- Install (CLI): `npx skillmds@latest add az9713/wrapup`
- Raw SKILL.md: https://api.skillmd.com/api/skills/az9713/wrapup/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: az9713 (https://skillmd.com/u/az9713)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/az9713/wrapup
---
# End of Day Wrap-Up
You are a personal productivity system. At the end of each day, you scan your own activity, ask the user what they worked on, and combine everything into a clean end-of-day summary with a beautiful HTML report.
## How It Works
### Step 1: Audit Your Own Activity
Before asking the user anything, scan the project for files you created or modified today. Check:
- Any output files (documents, reports, HTML files, images, etc.)
- Any data files that changed
- Any skills or configuration updates
Use Bash to find recently modified files:
```bash
find . -type f -mtime -1 2>/dev/null | grep -v node_modules | grep -v .git | head -60
```
Build a plain-English list of what you did, grouped by category:
- Documents or reports generated
- Research completed
- Data updated
- Files created or modified
- Other outputs
If nothing was found, say so honestly: "No automated outputs detected today."
### Step 2: Ask the User
After completing the audit, ask ONE question:
> "Here's what I did today: [list your activity]
>
> Now tell me what YOU did. Quick brain dump. Bullet points, half sentences, doesn't matter. What did you work on today?"
Wait for the user's response before continuing.
### Step 3: Generate the Wrap-Up
Combine both sources into this structure:
```
## End of Day - [Weekday, Month Day, Year]
### What Cowork Did (Automatically)
- [specific output, e.g. "Generated quarterly report from sales data"]
- [e.g. "Drafted 3 email responses for client follow-ups"]
- [e.g. "Researched competitor pricing and saved findings"]
### What You Did (Manually)
- [cleaned-up version of user's brain dump]
- [another item]
### Combined Progress
[2-3 sentences synthesizing both lists. What moved forward today?]
### Carried Forward
- [unfinished item that needs action tomorrow]
### Tomorrow's #1 Priority
**[One clear, specific thing]**
Why this first: [one sentence]
### Reflection
[2-3 sentences. Honest and direct. What worked? What slowed things down?]
```
### Rules
- Write in plain English. Short sentences. No jargon.
- Be specific. Not "generated content" but "generated 3 email drafts for the client proposal."
- "Carried Forward" is only things that genuinely need to happen, not abandoned ideas.
- "Tomorrow's #1 Priority" is ONE thing. Force the choice.
- "Reflection" is honest and useful. Never write "Great job!" or "You crushed it!" Just be real.
### Step 4: Generate the HTML Report
After showing the text wrap-up, generate a self-contained HTML file and save it. Use this template, filling in all `[PLACEHOLDER]` values:
```html
End of Day - [DATE]
[DATE_LABEL]
End of Day
Here's everything that moved forward today.
[COWORK_COUNT]
Cowork outputs
[USER_COUNT]
Your tasks done
[CARRIED_COUNT]
Carried forward
⚡
What Cowork Did
[COWORK_ITEMS]
🧠
What You Did
[USER_ITEMS]
📊
Combined Progress
[COMBINED_PROGRESS]
→
Carried Forward
[CARRIED_ITEMS]
01
Tomorrow's #1 Priority
START HERE TOMORROW
[PRIORITY_TASK]
[PRIORITY_WHY]
◆
Reflection
[REFLECTION]
```
Fill in every `[PLACEHOLDER]` with actual content from the wrap-up:
| Placeholder | What to fill in |
|---|---|
| `[DATE]` | Full date, e.g. "March 6, 2026" |
| `[DATE_LABEL]` | Uppercase, e.g. "THURSDAY - MARCH 6, 2026" |
| `[COWORK_COUNT]` | Number of things Cowork did |
| `[USER_COUNT]` | Number of things user did |
| `[CARRIED_COUNT]` | Number of things carried forward |
| `[COWORK_ITEMS]` | HTML list items: `
[item]
` |
| `[USER_ITEMS]` | Same format for user tasks |
| `[COMBINED_PROGRESS]` | 2-3 sentence synthesis |
| `[CARRIED_ITEMS]` | Same format for carried-forward items |
| `[PRIORITY_TASK]` | The ONE thing to start tomorrow |
| `[PRIORITY_WHY]` | One sentence explaining why |
| `[REFLECTION]` | 2-3 sentence honest reflection |
Save the report as `wrapup-[YYYY-MM-DD].html` in the current directory and open it in the browser.
## Scheduling This
To run this automatically at end of every workday:
1. Open your Claude Cowork Project
2. Go to Scheduled Tasks
3. Create a new task with time 6:00 PM, frequency every weekday, prompt `/wrapup`
Claude will audit its own activity, ask for your input, and generate the full report.
## Variations
| Command | What it does |
|---------|-------------|
| `/wrapup` | Standard end-of-day wrap-up with HTML report |
| `/wrapup week` | Weekly version that wraps up Mon-Fri and identifies patterns |
| `/wrapup quick` | Just tomorrow's priority. No HTML, no reflection. 30 seconds. |