How do I install the Skill Update skill?

Run npx skillmds@latest add dvcrn/skill-update 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 Skill Update safe to use?

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

Which AI agents work with Skill Update?

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 Skill Update free to use?

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

Who published Skill Update?

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

Skill Update by dvcrn — Agent Skill

Name: Skill Update
Rating: 4.2 (5 reviews)
Author: dvcrn

File contents

Safe Skill Updates

Core principle: Never update without user understanding and approval.

Updates can break things:

Changed file locations → data loss
Removed features → broken workflows
New requirements → unexpected behavior
Changed data formats → incompatible state

References:

Read preview.md — Diff and impact analysis
Read migrate.md — Data migration strategies

Update Flow

Check — Are updates available?
Preview — What changes? How does it affect user?
Explain — Present changes step-by-step
Confirm — User explicitly approves
Backup — Save current state
Update — Apply new version
Verify — Confirm everything works

Checking for Updates

npx clawhub outdated           # List skills with updates
npx clawhub info <slug>        # Show available versions

Proactive notification: When user mentions a skill, check if update exists. Mention it once, don't nag.

Preview Before Update

⚠️ Never update without showing impact first.

For each changed file:

Show what's different (added/removed/modified)
Explain how it affects user's workflow
Flag breaking changes prominently

Breaking change indicators:

File/folder structure changes
Removed instructions or features
New required setup steps
Changed data format expectations

User Validation

Present changes in digestible format:

"Skill X has v2.0.0 available. Changes:

⚠️ Breaking: Config now in config.md (was in SKILL.md) Added: New templates/ folder with examples Removed: Old legacy.md no longer needed

Migration needed: Your saved preferences need to move. I can help migrate. Proceed?"

Only update after explicit "yes".

Backup Strategy

Before ANY update:

Copy current skill folder to ~/.clawhub/backups/<slug>-<version>-<timestamp>/
Note the backup location in response
If update fails → offer restore

Handling Migrations

When data format changes:

Detect user's current data (preferences, saved state)
Explain what needs to migrate
Propose migration steps
Execute only with approval
Verify migrated data works

See migrate.md for patterns.

Rollback

If update causes problems:

"Something's not working? I have a backup from before the update.
Want me to restore skill X to v1.2.3?"

Keep backups for at least 7 days or until user confirms new version works.

Updates should feel safe, not scary. User stays in control.

---name: skill-updatedescription: Safely update skills with preview, migration support, and user validation. Never lose data or break workflows.---## Safe Skill Updates**Core principle:** Never update without user understanding and approval.Updates can break things:- Changed file locations → data loss- Removed features → broken workflows- New requirements → unexpected behavior- Changed data formats → incompatible state**References:**- Read `preview.md` — Diff and impact analysis- Read `migrate.md` — Data migration strategies---### Update Flow1. **Check** — Are updates available?2. **Preview** — What changes? How does it affect user?3. **Explain** — Present changes step-by-step4. **Confirm** — User explicitly approves5. **Backup** — Save current state6. **Update** — Apply new version7. **Verify** — Confirm everything works---### Checking for Updates```bashnpx clawhub outdated # List skills with updatesnpx clawhub info <slug> # Show available versions```**Proactive notification:** When user mentions a skill, check if update exists. Mention it once, don't nag.---### Preview Before Update⚠️ Never update without showing impact first.**For each changed file:**1. Show what's different (added/removed/modified)2. Explain how it affects user's workflow3. Flag breaking changes prominently**Breaking change indicators:**- File/folder structure changes- Removed instructions or features- New required setup steps- Changed data format expectations---### User ValidationPresent changes in digestible format:> "Skill X has v2.0.0 available. Changes:> > **⚠️ Breaking:** Config now in `config.md` (was in SKILL.md)> **Added:** New `templates/` folder with examples> **Removed:** Old `legacy.md` no longer needed> > **Migration needed:** Your saved preferences need to move.> I can help migrate. Proceed?"Only update after explicit "yes".---### Backup StrategyBefore ANY update:1. Copy current skill folder to `~/.clawhub/backups/<slug>-<version>-<timestamp>/`2. Note the backup location in response3. If update fails → offer restore---### Handling MigrationsWhen data format changes:1. Detect user's current data (preferences, saved state)2. Explain what needs to migrate3. Propose migration steps4. Execute only with approval5. Verify migrated data worksSee `migrate.md` for patterns.---### RollbackIf update causes problems:```"Something's not working? I have a backup from before the update.Want me to restore skill X to v1.2.3?"```Keep backups for at least 7 days or until user confirms new version works.---*Updates should feel safe, not scary. User stays in control.*

Frequently asked questions

Skill Update