How do I install the Upgrade Claude skill?

Run npx skillmds@latest add tomevault-io/upgrade-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.

Is Upgrade Claude safe to use?

SkillMD's automated safety review verdict for this skill is WARNING. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Upgrade 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 Upgrade Claude free to use?

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

Who published Upgrade Claude?

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

Upgrade Claude by tomevault-io — Agent Skill

Name: Upgrade Claude
Author: tomevault-io

File contents

Upgrade Claude Code Skill

Upgrade Claude Code to the latest version - sends /exit, waits for exit, upgrades, and lets activity-monitor restart.

When to Use

User explicitly asks to upgrade Claude Code
New Claude Code version is available
Need to apply Claude Code updates

Pre-Upgrade Checklist

Before launching the upgrade script, 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. Launch the upgrade script

IMPORTANT: Must use nohup ... & pattern!

nohup node ~/zylos/.claude/skills/upgrade-claude/scripts/upgrade.js >> ~/zylos/logs/upgrade.log 2>&1 &

How It Works

Enqueue /exit: Puts /exit into the control queue (priority=1, block_queue_until_idle) — dispatcher handles idle detection and message blocking
Wait for exit: Monitors Claude process until it exits (up to 120s); aborts if timeout
Upgrade: Runs native installer (curl -fsSL https://claude.ai/install.sh | bash)
Daemon restart: activity-monitor detects exit and restarts Claude automatically

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

---name: upgrade-claudedescription: Upgrade Claude Code to the latest version with graceful shutdown and auto-restart. Use when the user asks to upgrade or when a new Claude Code version is available. Use when this capability is needed.---# Upgrade Claude Code SkillUpgrade Claude Code to the latest version - sends /exit, waits for exit, upgrades, and lets activity-monitor restart.## When to Use- User explicitly asks to upgrade Claude Code- New Claude Code version is available- Need to apply Claude Code updates## Pre-Upgrade ChecklistBefore launching the upgrade script, 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. Launch the upgrade script**IMPORTANT: Must use `nohup ... &` pattern!**```bashnohup node ~/zylos/.claude/skills/upgrade-claude/scripts/upgrade.js >> ~/zylos/logs/upgrade.log 2>&1 &```## How It Works1. **Enqueue /exit**: Puts `/exit` into the control queue (priority=1, block_queue_until_idle) — dispatcher handles idle detection and message blocking2. **Wait for exit**: Monitors Claude process until it exits (up to 120s); aborts if timeout3. **Upgrade**: Runs native installer (`curl -fsSL https://claude.ai/install.sh | bash`)4. **Daemon restart**: activity-monitor detects exit and restarts Claude automatically---> Converted and distributed by [TomeVault](https://tomevault.io/claim/zylos-ai) — claim your Tome and manage your conversions.

Frequently asked questions

Upgrade Claude