session-start
Skill1 starsChanged 3 months agoMITView on GitHub
Open a work session — reconstruct the exact project state from the deterministic scripts and repo memory (CONSTITUTION → BIBLE.md → HANDOFF.md) before changing anything, so work continues without drift. Counterpart to session-stop. Trigger: "session-start", "continue", "where were we", "new session", "catch me up", "weiter", start of a work session.
42 other projects use a version of this.
Adopted by
Most recently taken up by
- maiconlara/session-starttheir own version, first seen Nov 16, 2026
- fizz/claude-skillstheir own version, first seen Nov 16, 2026
- timursafiullin/aodtheir own version, first seen Nov 15, 2026
- beworkall/agent-skills-securitytheir own version, first seen Nov 15, 2026
- AlexZio00/sovereign-skillstheir own version, first seen Nov 14, 2026
- kimkon1011/orgiast-claude-rulestheir own version, first seen Nov 13, 2026
Used with
Projects with it also use session-end, deploy-verify and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jasonmichaelbell78-creatorSkillsession-end
Also in 12 projects that use this
danielarif26Skilldeploy-verify
Verify a Vercel deployment actually went live and serves the correct production domain. Self-improving: reads its own run history before checking and logs the outcome after. Use when the user asks "did you deploy?", "is it live?", "verify the deploy", "check vercel", or after any Vercel deploy. Part of the Agentic OS (Level 1 backbone).
Also in 3 projects that use this
Microsoft AzureSkillreflect
Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections ("no", "wrong"), praise ("perfect", "exactly"), or when discovering edge cases. Complements .squad/agents/{agent}/history.md and .squad/decisions.md.
Also in 4 projects that use this
ibahgatSkillautopilot
Run autonomous multi-stage execution loops until acceptance criteria pass or blockers are reached.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions42 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 42
- bitwize-music-studio/claude-ai-music-skills★ 668same name
- AlexZio00/sovereign-skills★ 158same name
- yahor-punko/mavericks-os★ 104same name
- Kanevry/session-orchestrator★ 53same name
- xcota/pos★ 32same name
- iamneilroberts/claude-skills★ 26same name
- albertomarturelo/sii★ 19same name
- IlyaGorsky/memory-toolkit★ 13same name
- mae616/ai-template★ 9same name
- freskhu/genesis★ 5same name
32 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- contextSkill
- project-stateSkill
- session-stopSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
1
Distinctive
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 27
Keep it to a few lines. The goal is "caught up and grounded", not a wall of output.
“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
session-start
Reconstruct the exact state before touching anything. Facts first (deterministic), reasoning second.
Steps
- Read the constitution chain (highest precedence first):
dev/base/CONSTITUTION.md, then this repo'sBIBLE.md(invariants + open decisions), then the newestHANDOFF.mdentry. If a family constitution /ECOSYSTEM.mdis referenced, read it before the repo's own docs. - Run the backbone (zero AI):
./scripts/state.sh— branch, ahead/behind, source/test counts, last commits, newest HANDOFF../scripts/gate.sh— is the tree already green? (don't fix yet, just know.)
- Layer in the plugin context (if available). The session hook may have injected a claude-mem
block (timeline, observation IDs, token stats). Treat it as background. If it contradicts
BIBLE.md,BIBLE.mdwins. If an observation names a file, function or flag, verify it against the code before building on it. - Report back, briefly: where we are, what the newest HANDOFF says is Next, and whether any
blocking decision is open in
BIBLE.mdor the gate is red. - Do not start substantive work while a blocking decision is open or the gate is red — resolve or surface that first.
Keep it to a few lines. The goal is "caught up and grounded", not a wall of output.
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.

