end-of-day-reflection
Skill0 starsChanged 4 months agoMITView on GitHub
Pull the day's real activity — what shipped, what moved, what's stuck — and hand the owner a short read on what changed. End of the workday, as a routine or on demand. When the owner wants to close the day knowing what actually happened.
In this repository29 other files it gives its agents.
- devils-advocate-first-passSkill
- load-bearing-assumptionSkill
- pre-mortemSkill
- reversibility-checkSkill
- three-option-framingSkill
- boundary-setting-declineSkill
- cold-intro-structureSkill
- customer-reply-tone-matchSkill
- quote-follow-upSkill
- subject-line-not-filteredSkill
- inbox-triageSkill
- project-scaffoldingSkill
- quote-drafting-from-notesSkill
- vendor-invoice-categorizationSkill
- competitor-pricing-extractSkill
- customer-voice-extractSkill
- source-verificationSkill
- tactic-extractionSkill
- vertical-landscape-scanSkill
- discovery-call-note-captureSkill
- lead-qualificationSkill
- objection-handlingSkill
- proposal-drafting-frameworkSkill
- stack-the-deck-closeSkill
- dont-be-a-chatbotSkill
- honest-hedgingSkill
- lead-with-the-actionSkill
- specific-over-genericSkill
- write-like-the-userSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Keep it short. A reflection that takes ten minutes to read defeats the point.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
End-of-Day Reflection
At day's end the owner should know what changed without reconstructing it from memory. Pull the real activity — what got done, what moved forward, what's stuck — and hand back a short, honest read.
The technique
- Pull what actually happened from the day's real activity — sent emails, closed tasks, calls, approvals — not a vibe.
- Lead with what shipped: the things that are done and verified, named specifically.
- Name what moved but isn't finished, and what's stuck and why — the blockers are the part the owner needs most.
- Surface anything that needs the owner tomorrow — a decision waiting, a follow-up due, a deadline approaching.
- Keep it short. A reflection that takes ten minutes to read defeats the point; the owner wants the day in thirty seconds.
Do this, not that
Do: "Today: sent 3 quotes (Henderson, Diaz, the gutter job), closed the Miller invoice, booked Thursday's crew. Stuck: the supplier still hasn't confirmed the material price — that's blocking the Diaz start. Tomorrow needs you: call Dave back, and the Miller follow-up is due."
Don't: Hand back "It was a productive day with good progress across several areas!" — a feeling, not a read, that tells the owner nothing and surfaces no blocker.
Why this works
Owners carry the whole business in their head, and at the end of a busy day that head is full and unreliable. A reflection built from real activity — not memory, not vibes — lets them close the day knowing what actually changed and start tomorrow knowing what needs them. The blockers matter most: those are the things that quietly stall the business while everyone assumes they're handled.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

