nightly-wrap
Skill0 starsChanged 5 months agoMITView on GitHub
the operator's end-of-day wrap. Use when the operator says "nightly wrap", "wrap up", "end of day", "before shift", or when a session starts between 8pm and 11:45pm. Captures what shipped, what got blocked, sets tomorrow's top 3, queues async-work for during the operator's night shift.
In this repository9 other files it gives its agents.
- coordinatorSkill
- decision-queueSkill
- discovery-sprintSkill
- hair-productSkill
- midday-pulseSkill
- morning-briefSkill
- permissionsSkill
- revenue-experimentSkill
- venture-triageSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Ask the operator concisely:
- Very specific: line 27
Update top-3.md with completion marks and roll a fresh entry for tomorrow.
- Very specific: line 41
Write to top-3.md with tomorrow's date.
- Distinctive: line 49
Not tasks. Questions. He'll come back with answers in the morning.
- Distinctive: line 53
If permissions are Tier 2 or 3 and the operator will be away from the system for 8+ hours, ask:
- Distinctive: line 55
Default recommendation: drop to Tier 1 overnight.
- Distinctive: line 59
If today is Saturday (last shift before Sunday off): "Tomorrow is a partner's day.
- Distinctive: line 91
Never end without a written tomorrow's top 3.
- Distinctive: line 92
Never skip the permissions check if tier > 1.
- Distinctive: line 93
If the operator has been working >12 hours today (e.g., school + ventures + shift), tell him explicitly that running on empty produces bad …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Nightly Wrap
the operator's night shift starts 12AM Tue-Sat. This wrap runs before he leaves for the office. Be efficient.
Read first
~/Vault/Vantage-OS/top-3.md(today's)~/Vault/Vantage-OS/ventures.md~/Vault/Vantage-OS/decisions.md~/Vault/Vantage-OS/experiments.md~/Vault/Vantage-OS/hair-product-state.md
Run this sequence
1. Capture today's outcomes
Ask the operator concisely:
- Which of today's top 3 actually shipped?
- Anything ship that wasn't on the list?
- Anything new blocking you?
Update top-3.md with completion marks and roll a fresh entry for tomorrow.
2. Set tomorrow's top 3
Propose them based on:
- Today's spillover
- Decisions with deadlines tomorrow or day after
- Hair-product next action
- Anything from
ventures.mdthat's been stuck >5 days
Maximum 3. Reject any attempt to add a 4th. Force a swap.
Each must have: venture, estimated time, definition of done.
Write to top-3.md with tomorrow's date.
3. Queue async work for the night shift
the operator works night shift solo at the day job. He's not at his computer for personal work, but he can think. Surface 1-2 specific thinking questions for tonight, e.g.:
- "Should the hair product be a single SKU or a 2-product line at launch?"
- "the partner's salon traffic - what's a realistic conversion rate for a hand-out flyer?"
Not tasks. Questions. He'll come back with answers in the morning.
4. Permissions check
If permissions are Tier 2 or 3 and the operator will be away from the system for 8+ hours, ask:
- "Want me to stay at current tier overnight, or drop to Tier 1 until you're back?"
- Default recommendation: drop to Tier 1 overnight.
5. Personal check
If today is Saturday (last shift before Sunday off): "Tomorrow is a partner's day. Anything I should remind you about for her?"
Output
# Nightly Wrap - [DATE]
## Shipped today
- ✓ ...
## Slipped
- ✗ ... → moved to [tomorrow / next week / parked]
## Tomorrow's top 3
1. ...
2. ...
3. ...
## Tonight's thinking questions
- [Q1]
- [Q2]
## Permissions
- Currently: Tier [N]
- Overnight recommendation: [Tier 1 / hold / raise]
## Notes for tomorrow's brief
- [Anything specific to surface in the morning]Rules
- Never end without a written tomorrow's top 3.
- Never skip the permissions check if tier > 1.
- If the operator has been working >12 hours today (e.g., school + ventures + shift), tell him explicitly that running on empty produces bad decisions.
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.