session-sunset
Skill11 starsChanged 7 days agoMITView on GitHub
End a session without Zero-State Amnesia; use at >75% of the seat's own window, a quiet point before a distant lane, a macro-semantic pivot, or human directive (never task completion/wait).
In this repository39 other files it gives its agents.
- architecture-pre-flightSkill
- blocked-task-stateSkill
- blog-postSkill
- context-recoverySkill
- create-skillSkill
- design-sweepSkill
- epic-createSkill
- epic-resolutionSkill
- epic-reviewSkill
- goal-scopingSkill
- guide-authoringSkill
- hostile-content-quarantineSkill
- ideation-sandboxSkill
- identity-firewallSkill
- industry-friction-radarSkill
- lane-intentSkill
- lead-roleSkill
- memory-miningSkill
- neo-app-authoringSkill
- neo-identity-updateSkill
- neural-linkSkill
- overviewSkill
- peer-namingSkill
- peer-roleSkill
- post-review-pickupSkill
- pr-reviewSkill
- pull-requestSkill
- release-notesSkill
- self-repairSkill
- structural-pre-flightSkill
- tech-debt-radarSkill
- ticket-createSkill
- ticket-intakeSkill
- ticket-triageSkill
- turn-memory-pre-flightSkill
- unit-testSkill
- update-roadmapSkill
- video-createSkill
- whitebox-e2eSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
If you meet a valid sunset condition, you MUST immediately use the view_file tool to read and strictly adhere to …
≈ “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
Session Sunset Skill
🛑 ANTI-TRIGGERS (Completion Bias Guard) 🛑 Task Completion ≠ Session Sunset. Unless the workflow's trigger 1 holds, you must halt and wait for the next turn (do NOT sunset) if you are:
- Halting for Peer Review: Waiting for cross-family PR review or human feedback. This is an active lifecycle state, not a boundary.
- Single Task Completion: Finishing one ticket/task while your context window is still healthy. Pick up the next task.
- Asynchronous Delays: Waiting for CI, test results, or A2A responses.
Sunsets are strictly reserved for the workflow's §1 triggers: Context Exhaustion or Cost, Macro-Semantic Pivots, or Explicit Human Directives.
If you meet a valid sunset condition, you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/session-sunset/references/session-sunset-workflow.md before terminating. This prevents Zero-State Amnesia.
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.