Installs into .claude/skills of the current project.
Are you the author of Session Start?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/xcota-session-start)
---
name: session-start
description: "Use when starting a new working session or when context needs fresh boot."
version: 1.0
user_invocable: true
---
# /session-start β Boot Camomile Context
Boot context for a new working session. Progressive loading: minimal at start, expand by task.
## Steps
0. **Check what the start hook already poured in.** `.claude/hooks/session-start.sh` runs at every launch and prints a `--- State ---` block (state, priorities, today's note, checkpoints, sensors and the π€/π gates). If that block is in context, skip steps 1, 2, 4 and 5 β those files are already read, re-reading them wastes the boot budget. No block (a subagent, another entry point, or the hook failed) β do the steps by hand. If the block says the folder is not set up yet, follow its line and stop.
1. If `state/current.md` exists, read it β what's happening across all contexts right now. If it's absent (or `context/identity.md` still has `{{ }}` placeholders), the folder isn't set up yet β don't fabricate state. Say it to the person in ONE plain line, in the language they write in, and stop:
> This folder isn't set up yet β just type `/start` and I'll do the rest. No commands or steps needed from you.
Say it in the language the person writes in. Never write the word "vault" to the person β it is a folder.
2. Read `context/priorities.md` β current focus and active work
3. Read `context/anti-patterns-index.md` β load the **LIVE watch-list** (active failure modes). Full `context/anti-patterns.md` is reference β pull by AP-ID when a task touches that domain.
4. Check if `daily/{today's date}.md` exists β read last 20 lines for today's events
5. Scan `state/sessions/` β any active checkpoints to continue?
6. If the task is system architecture, agent runtime, or sync β read `context/agent-runtime.md`
## Output
Display a compact dashboard:
In plain words, in the language the person writes in, with no paths and no jargon:
```
=== Camomile ===
In focus now: {top priorities from priorities.md}
Where we stopped: {active contexts from current.md}
What I remember not to repeat: {top 3 anti-patterns}
Today: {key events if daily note exists}
Can be continued: {available session checkpoint, if any}
===
```
Drop an empty line entirely β shorter is better than a row of dashes.
## Rules
- Total context after boot should be 15-25K tokens, not more
- Do NOT load all of knowledge/ β only load specific files when the task demands it
- Do NOT load project context unless working on that project
- If user wants to continue a session: read the checkpoint, load its context
- After displaying dashboard, ask "What are we working on?" if not obvious