Runtime Lifecycle
Use when verification depends on agent runtime phases, queued input, tool-call lifecycle, save points, retry, abort, compaction, or branch behavior.
Install
npx skills add rohitg00/agentbrain --skill runtime-lifecyclegit clone --depth 1 https://github.com/rohitg00/agentbrain.git /tmp/agentbrain
mkdir -p ~/.claude/skills
cp -r /tmp/agentbrain/skills/runtime-lifecycle ~/.claude/skills/runtime-lifecyclePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# runtime-lifecycle Lifecycle stage: VERIFY ## Trigger Use when an artifact, adapter, handoff, runtime smoke run, scheduled job, or long-running goal claims behavior across turn boundaries, queued messages, tool execution, compaction, retry, abort, branch switching, or session persistence. ## When not to use Do not use for ordinary artifact checks where the claim is fully proven by static files, schemas, tests, or docs and no runtime phase, queue, tool, or persistence boundary affects trust. ## Inputs - Runtime or adapter under review. - Current Agent Brain command and state. - Transcript, logs, events, runtime smoke artifact, or handoff evidence. - Tool calls, queued input, writes, approvals, aborts, retries, compactions, or branch changes involved. - Expected durable artifact and validation command. ## Procedure 1. Classify the phase at the start and end: idle, active turn, tool preflight, tool execution, save point, retry, abort, compaction, branch, or unknown. 2. Separate durable session state, in-flight turn snapshot, queued input, future configuration, and pending writes. 3. Check queued input delivery. Steering, follow-up, and next-turn messages are not approval for an in-flight side effect unless the runtime proves that delivery boundary. 4. Map each side-effecting tool through requested arguments, validation or approval, execution, result shaping, final persisted evidence, and ordering caveats.
Details
- Skill name
runtime-lifecycle- Repository
- rohitg00/agentbrain
- Path
skills/runtime-lifecycle/SKILL.md- License
- MIT
- Repo updated
- 26 May 2026
FAQ
What does the Runtime Lifecycle skill do?
Use when verification depends on agent runtime phases, queued input, tool-call lifecycle, save points, retry, abort, compaction, or branch behavior.
How do I install the Runtime Lifecycle skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add rohitg00/agentbrain --skill runtime-lifecycle. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Runtime Lifecycle popular?
It lives in rohitg00/agentbrain, which has 43 GitHub stars and 9 forks.
Related skills
Activity Recap
43rohitg00/agentbrain
Use when the user needs a standup-ready summary of recent project activity from local evidence.
Adapter Capability Probe
43rohitg00/agentbrain
Use when a command, adapter, or runtime smoke depends on proving an agent runtime's capabilities before trusting command routing, writes, shell access, or validation claims.
Agent Output Verifier
43rohitg00/agentbrain
Use when agent-produced work needs a safety, evidence, and reliability check before handoff, merge, or trust.
Lfe Archivist
44StChiotis/Library-First-Engineering
Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.
Daily Summary
44jiahao-shao1/sjh-skills
Produce daily/yesterday work summary (日报) by aggregating Claude Code sessions, Git commits, and Notion task data — git log alone cannot do this. Args: today (default), yesterday, 24h, YYYY-MM-DD. Triggers: 'daily summary', 'what did I do today', 'yesterday summary', '日报', '今天干了什么', '工作总结', '某天做了什么'. Not for weekly reports or summarizing files.
Issue Tree Builder
33AnugamChakra/think-like-a-strategy-consultant
Builds a MECE issue tree that breaks a business problem into clean, non-overlapping, fully-covering branches drilled deep enough to reach testable hypotheses. Use this skill whenever the user wants to decompose or break down a problem, asks "build me an issue tree", "is this MECE", "map out the possible causes", "what are all the drivers of X", or is staring at a big messy problem and needs structure. Trigger it for both diagnostic problems (why did something happen) and solution problems (how could we achieve a goal). Use it even when the user doesn't say "issue tree" — if they need to struct
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.