Session Skills
Claude Code Skills

Stop worrying about
context running out.

Two skills that keep Claude on track — across sessions, across /clears, across days.
Start every session in 30 seconds. No re-explaining. Ever.
press → to start
Sarat.
Sound familiar?

Every session.
Blank slate.

There had to be a better pattern.
The solution

Two skills.
Two jobs.

/session-status Start of every session. Reads your live session log + latest handoff + git state. Returns a structured status block in under 90 seconds — where you are, what's done, what's next.
/session-handoff End of day. Writes .handoffs/YYYY-MM-DD.md — decisions locked, what shipped, deferred items, open questions. Folds in the session log and resets it for tomorrow.
Both files auto-create. Commits are optional. Zero setup friction.
The clever bit

Two recovery paths.
One system.

Mid-session /clear
  • session-status reads SESSION-STATE.md
  • Live journal — updated every task
  • Back in 30 seconds. No ceremony.
New day / fresh session
  • session-status reads .handoffs/YYYY-MM-DD.md
  • End-of-day permanent record
  • Full context from yesterday restored
SESSION-STATE.md is what makes /clear safe. The handoff is the permanent record. The live log handles everything in between.
The live journal

SESSION-STATE.md

⚡ SESSION LOG — updated every task
  • Tasks completed — what you finished this session
  • Decisions made — what was decided and why
  • Ideas captured — anything that surfaced mid-session
  • Next from here — what to pick up next
Lives in .planning/SESSION-STATE.md (auto-created). If context clears unexpectedly, /session-status reads this and resumes in 30 seconds — no handoff needed.
End of day

/session-handoff

Written once a day. Committing is optional — Claude reads it either way. Next session, /session-status reads this and you're back in 30 seconds.
The operational manual

Three lines in CLAUDE.md.
That's it.

Add to your CLAUDE.md
  • Every session, before any work: run /session-status first
  • When I say "wrap up" or "session handoff": run /session-handoff
  • After every significant task: update SESSION-STATE.md SESSION LOG
"let's start a session" /session-status runs — 30s orientation
"wrap up" / "session handoff" /session-handoff runs — saves to .handoffs/
Claude reads CLAUDE.md at session start. Say the phrase — the right skill runs automatically.
Your turn

Copy. Adapt. Use.

Both skill files are in the Skool post — under 100 lines each. Copy them into .claude/skills/ and adapt SESSION-STATE.md to your project.
No more context anxiety. /clear whenever you want. The system remembers.
One more thing — the skills format comes from Nate Herk. He runs AI Automation Society+ on Skool and this system wouldn't exist without what he shared there. If you're building on Claude and not already in, worth checking out.
Join the community →
Sarat.
More like this

Creator OS

AI tools, scripts, and workflows — documented as I learn.
What's inside Real systems I'm building and testing — shared as I go, not polished after the fact.
Who it's for Anyone using AI to build — tools, workflows, automations, and the thinking behind them.
Free to join.
Join Creator OS →
Sarat.
1 / 9
← → to move