# Evening Ops Skill

## Purpose
Consolidated evening and overnight operations for Alfred (orchestrator). Covers 6:00 PM – 2:00 AM Bolivia time.

## evening-report
**Schedule**: 6:00 PM daily | **Agent**: Alfred

Compile end-of-day report for Clayton:
1. Tasks completed today — list with agent attribution
2. Tasks carried over to tomorrow
3. Revenue metrics — leads contacted, proposals sent, deals progressed
4. Outreach stats — emails sent, responses received, meetings booked
5. Any issues requiring Clayton's attention
6. Tomorrow's top 3 priorities
7. Deliver summary via Telegram — concise, actionable

## weekly-review
**Schedule**: Friday 6:00 PM | **Agent**: Alfred

Compile the weekly review for Clayton:
1. Revenue generated this week
2. Leads contacted and conversion metrics
3. Deals closed or progressed
4. Projects delivered or milestones hit
5. Agent performance summary — task completion rates, errors
6. Blockers resolved this week
7. Key learnings and insights
8. Priorities for next week
9. Deliver via Telegram

## nightly-backup
**Schedule**: Midnight daily | **Agent**: Alfred

Run workspace backup:
1. Commit any uncommitted changes in the workspace repo
2. Push to GitHub
3. Verify WARP.md and TODO.md are current
4. Log backup status
5. Report any failures via Telegram

## memory-consolidation
**Schedule**: 2:00 AM daily | **Agent**: Alfred

Review all sessions and daily notes from today:
1. For each session, extract: important decisions, context, lessons learned, project updates
2. Update relevant knowledge base files in `knowledge/projects/`, `knowledge/areas/`, or `knowledge/resources/`
3. Update `knowledge/tacit-knowledge.md` if any new preferences, patterns, or rules were established
4. Update `MEMORY.md` with a distilled summary of the day
5. Create tomorrow's daily note from template (`knowledge/daily-note-template.md`) with carried-over open sessions and priorities
6. Only capture what future sessions need to know — no trivial summaries