system-boot
/system-boot
Auto-activating session startup - reads memory, orients Claude, announces status. Triggers on session start or when user says "continue", "weiter", "resume".
- Author
- primeline-ai ↗
- Repository
- evolving-lite ↗
- Licence
- MIT
- Last repository change
- 05.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Auto-activating session startup - reads memory, orients Claude, announces status. Triggers on session start or when user says "continue", "weiter", "resume".
Triggers from the description
Original author description
Auto-activating session startup - reads memory, orients Claude, announces status. Triggers on session start or when user says "continue", "weiter", "resume".
How it works
- 1. Read Memory
- 2. Orient
- 3. Announce
- 4. Pick One Task
- Continue Trigger
- Session End
SKILL.md preview
---
name: system-boot
description: Auto-activating session startup - reads memory, orients Claude, announces status. Triggers on session start or when user says "continue", "weiter", "resume".
---
# System Boot
On every session start, perform this bootup sequence:
## 1. Read Memory
Read `${CLAUDE_PLUGIN_ROOT}/_memory/index.json` for:
- `active_project`: Which project the user was working on
- `last_session`: When the last session was
If `active_project` is set, read `${CLAUDE_PLUGIN_ROOT}/_memory/projects/{active_project}.json` for:
- `progress`: Array of recent progress entries
- `next_step`: What was planned next
- `failures`: Known blockers or failures
## 2. Orient
Based on memory:
- What was the last progress entry?
- Are there any known failures or blockers?
- What was suggested as the next step?
## 3. Announce
Output a compact status line:
```
Evolving Lite | Session {n} | Tier {tier} | {experience_count} experiences
Last: {last_progress_summary}
Next: {next_step}
```
If this is the first session ever (no progress), announce with a short, visible
cold-start sequence so the system does not feel inert on day 1:
```
Evolving Lite v1.0 | First session
[1/3] Loading {prewarmed_count} pre-warmed experiences ... ok
[2/3] Tier 1 (Safety) active: context warnings, bash security, hook sentinels
[3/3] Self-Star Doctor: wiring verified (run /health for the full board)
Ready. The system learns from your corrections automatically and self-tunes its
delegation routing from your sessions (see "Self-Evolution is ON" in the README).
```
The Self-Star Doctor also runs a quick wiring + preflight check automatically on this
first session. If it reports a missing prerequisite (most often Kairn), surface that to
the user and point them at `/health` and `pip install kairn-ai`.
## 4. Pick One Task
If the user hasn't specified what to work on, suggest the `next_step` from memory. Don't start multiple tasks - pick one.
## Continue Trigger
When the user says "continue", "weiter", "weitermachen", "fortsetzen", or "resume":
1. Read the most recent session summary from `${CLAUDE_PLUGIN_ROOT}/_memory/sessions/`
2. Load the plan if one was referenced
3. Continue immediately - no questions, just pick up where we left off
## Session End
When a session ends naturally (user says goodbye, or Stop hook fires):
- The session-summary hook handles progress logging automatically
- No manual action needed from the user
Versions
The database has no other skills named system-boot.
Database snapshot: 13.11.2026 · package version d257e9e3676f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90start
Hydrate session context from last handoff. Triggers: resume, pick up where I left off, continue from last session, what was I working on, session status, what's the state. Use for deep hydration beyond the auto-injected summary. - 100m0-handoff
Use when the user says m0 handoff, before I compact, end of session, save session state, resume where we left off, or continue in Cursor or Claude Code. Writes or reads a compact_checkpoint so a cold start becomes a continuation. - 100resume-claude-session
Use when the user asks Codex to continue, resume, or take over work from a Claude Code session by session name or session id (UUID or UUID prefix). Examples include "continue the claude session called feature-x" or "/resume-claude-session a3b5c9f2". Do not use for ordinary Codex… - 100resume-codex-session
Use when the user asks Claude to continue, resume, or take over work from a Codex session by session name or session id (UUID or UUID prefix). Examples include "continue the codex session called feature-x" or "/resume-codex-session 019dc08e". Do not use for ordinary Claude… - 86resume-claude
Continue work from a local Claude Code session in Muse Code. Use when the user asks to resume, continue, or recover unfinished Claude Code work, with or without a session ID or log path; call read_skill for bundled:resume-claude before reading its transcript. Explicit /import requests use import. - 100continue
Resume work from a prior session by reading phase progress files in .claude/memory/ and active plans. Use this when starting a new session on in-progress work, or when the user says "continue", "pick up where I left off", "resume", or "what was I working on".