メニュー
Use when the user asks to restart Claude Code, or after changing settings/hooks/keybindings.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/zylos-ai/zylos-core --skill restart-claudeコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
C4 communication bridge — central gateway for ALL external communication (Telegram, Lark, etc.). Use when replying to users via the "reply via" path, sending proactive messages to external channels, querying recent conversations or checkpoint status (prefer c4-db.js CLI; sqlite3 OK for unsupported queries), fetching conversation history for Memory Sync, or creating checkpoints after sync. Incoming messages are queued by channel bots and delivered to Claude via a PM2 dispatcher daemon. Session-start hooks automatically provide conversation context and can trigger Memory Sync when unsummarized conversations exceed the configured threshold.
Guidelines for managing zylos components via CLI and C4 channels. Use when installing, upgrading, or uninstalling components, or when user asks about available components.
Guardian service that monitors the active runtime agent's state and automatically restarts it if stopped. Use when checking agent liveness state or understanding the auto-restart mechanism.
SKILL.md を表示中
SOC 職業分類に基づく
| name | restart-claude |
| description | Use when the user asks to restart Claude Code, or after changing settings/hooks/keybindings. |
Restart Claude Code session - sends /exit and lets activity-monitor daemon handle the restart.
Before sending /exit, complete these steps in order:
Check for running background agents (Task tool). If any are active, stop them to avoid orphaned work.
Update memory files (state.md, sessions/current.md, etc.) to preserve important context that would otherwise be lost on restart.
Write a brief message covering:
Send the full handoff summary to the internal void channel via C4:
cat <<'EOF' | node ~/zylos/.claude/skills/comm-bridge/scripts/c4-send.js "void" "session-handoff"
<handoff summary>
EOF
The void channel is record-only: the message is stored in C4 conversation
history (so the restarted session's startup hook, c4-session-init, includes
it in startup context) but is never delivered to any real channel or display
surface.
Do not send the full handoff summary to the active external user channel
(Telegram, Lark, Feishu, HXA, etc.). Handoff summaries are operational context
for the next agent session and may contain task state from outside the current
conversation. If the user is actively waiting, send only a short user-facing
notice to their current reply via path, without internal task inventory or
cross-channel context.
node ~/zylos/.claude/skills/comm-bridge/scripts/c4-control.js enqueue --content "/exit" --priority 1 --block-queue-until-idle
/exit into the control queue (priority=1, block_queue_until_idle)/exit to tmux when Claude is idle