session-start
Skill5 starsChanged 6 months agoApache-2.0View on GitHub
Run the mandatory Session Start Protocol (memory-hot, inbox, pending tasks, kaizen backlog, dream check, session tracking)
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 deploy-verify, reflect and 1 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.
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
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
- sandraschi/libreoffice-mcp★ 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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- db-healthSkill
- dreamSkill
- forum-pulseSkill
- genesisSkill
- grill-meSkill
- handoffSkill
- hireSkill
- inbox-processSkill
- kaizenSkill
- quality-gateSkill
- quarterly-reviewSkill
- session-endSkill
- sync-upstreamSkill
- twin-updateSkill
- voice-gateSkill
- weekly-reviewSkill
- write-a-skillSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
2
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 14
Read that file and execute Steps 0–5 in order:
- Distinctive: line 28
Do NOT duplicate or fork the step logic here — edit the protocol file instead.
“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 Protocol — wrapper
This skill is a thin wrapper. The canonical, single source of truth is:
.claude/protocols/session-start.md
Read that file and execute Steps 0–5 in order:
- Regenerate and read
.claude/memory-hot.md - Inbox check (
inbox/againstprocessed_inbox_files) - Pending tasks (
SELECT * FROM v_open_tasks;) - Kaizen backlog surface (only when 3+
[Kaizen]proposals have been pending >48h) - Dream check (run
/dreamif due) - Log
session_startinactivity_history
Invoke /session-start manually at the start of each session. There is no
auto-firing hook: an earlier UserPromptSubmit gate was removed because it fired
in every Claude Code window opened anywhere inside the project tree and broke
unrelated ones. The protocol file explains the failure in full.
Do NOT duplicate or fork the step logic here — edit the protocol file instead. Two copies of a protocol drift, and the copy the agent happens to read wins.
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.

