How do I install the Restart Claude skill?

Run npx get-skill add tomevault-io/restart-claude in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Restart Claude skill do?

Use when the user asks to restart Claude Code, or after changing settings/hooks/keybindings. It is listed under Coding & Dev Tools on SkillMD.

Is Restart Claude safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Restart Claude?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Restart Claude free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Restart Claude?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Restart Claude by tomevault-io — Agent Skill

Name: Restart Claude
Author: tomevault-io

File contents

Restart Claude Code Skill

Restart Claude Code session - sends /exit and lets activity-monitor daemon handle the restart.

When to Use

After changing Claude Code settings, hooks, or keybindings
When Claude needs to reload configuration
To clear temporary state without upgrading
User explicitly asks to restart

Pre-Restart Checklist

Before sending /exit, complete these steps in order:

1. Stop background tasks

Check for running background agents (Task tool). If any are active, stop them to avoid orphaned work.

2. Sync memory

Update memory files (state.md, sessions/current.md, etc.) to preserve important context that would otherwise be lost on restart.

3. Write a session handoff summary

Write a brief message covering:

What was being worked on (active tasks, user requests in progress)
Current state (what's done, what's pending, any blockers)
What the next session should pick up (if anything)

4. Send the handoff summary

Determine who to notify:

If actively collaborating with a user: Send the summary to that user's channel via C4 (their reply via path). This keeps the user informed AND records the context into C4 conversation history.
If no active user conversation: Send the summary to the web console channel. This still records it into C4 so the new session's startup hook (c4-session-init) will include it in the conversation context.

The goal is twofold: (a) the user knows what's happening, and (b) the handoff summary appears in C4 conversation history, so the new session can seamlessly continue the work.

5. Enqueue /exit

node ~/zylos/.claude/skills/comm-bridge/scripts/c4-control.js enqueue --content "/exit" --priority 1 --block-queue-until-idle

How It Works

Enqueue /exit: Puts /exit into the control queue (priority=1, block_queue_until_idle)
Block subsequent messages: block_queue_until_idle prevents other messages from being dispatched
Deliver when idle: Dispatcher delivers /exit to tmux when Claude is idle
Daemon restart: activity-monitor detects exit and restarts Claude

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: restart-claudedescription: Use when the user asks to restart Claude Code, or after changing settings/hooks/keybindings.---# Restart Claude Code SkillRestart Claude Code session - sends /exit and lets activity-monitor daemon handle the restart.## When to Use- After changing Claude Code settings, hooks, or keybindings- When Claude needs to reload configuration- To clear temporary state without upgrading- User explicitly asks to restart## Pre-Restart ChecklistBefore sending `/exit`, complete these steps **in order**:### 1. Stop background tasksCheck for running background agents (Task tool). If any are active, stop them to avoid orphaned work.### 2. Sync memoryUpdate memory files (state.md, sessions/current.md, etc.) to preserve important context that would otherwise be lost on restart.### 3. Write a session handoff summaryWrite a brief message covering:- **What was being worked on** (active tasks, user requests in progress)- **Current state** (what's done, what's pending, any blockers)- **What the next session should pick up** (if anything)### 4. Send the handoff summaryDetermine who to notify:- **If actively collaborating with a user:** Send the summary to that user's channel via C4 (their `reply via` path). This keeps the user informed AND records the context into C4 conversation history.- **If no active user conversation:** Send the summary to the web console channel. This still records it into C4 so the new session's startup hook (c4-session-init) will include it in the conversation context.The goal is twofold: (a) the user knows what's happening, and (b) the handoff summary appears in C4 conversation history, so the new session can seamlessly continue the work.### 5. Enqueue /exit```bashnode ~/zylos/.claude/skills/comm-bridge/scripts/c4-control.js enqueue --content "/exit" --priority 1 --block-queue-until-idle```## How It Works1. **Enqueue /exit**: Puts `/exit` into the control queue (priority=1, block_queue_until_idle)2. **Block subsequent messages**: block_queue_until_idle prevents other messages from being dispatched3. **Deliver when idle**: Dispatcher delivers `/exit` to tmux when Claude is idle4. **Daemon restart**: activity-monitor detects exit and restarts Claude---> Converted and distributed by [TomeVault](https://tomevault.io/claim/zylos-ai) — claim your Tome and manage your conversions.

Frequently asked questions

Restart Claude