How do I install the Claude Vigil skill?

Run npx skillmds@latest add vvkmnn/claude-vigil 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 Claude Vigil safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claude Vigil?

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 Claude Vigil free to use?

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

Who published Claude Vigil?

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

Claude Vigil by vvkmnn — Agent Skill

Name: Claude Vigil
Author: vvkmnn

Claude Vigil

File checkpoint and recovery — auto-quicksaves before destructive commands, INVOKE before implementing a plan or starting risky multi-file changes. Also use when user asks to undo changes or compare current state to a prior checkpoint.

vvkmnn 719dc2e 2.5 KB Updated Sep 17, 2026

File contents

Vigil Plugin

File recovery. Saves checkpoints before dangerous operations, diffs changes, restores files safely.

Hooks

Hook	When	Action
PreToolUse(Bash)	Destructive command detected	Auto-quicksaves affected files (rm, mv, git reset, etc.)

Token cost: 0 on safe commands, ~30 on destructive.

Commands

Command	Description
`/save-vigil <name> [files]`	Create a named file checkpoint
`/restore-vigil [name]`	Restore files from a checkpoint

Workflows

Before Implementing a Plan

After exiting plan mode, before writing any code:

vigil_save(name="before-<plan-name>") — snapshot the project
Implement the plan
If something goes wrong: vigil_diff(name="before-<plan-name>") then vigil_restore(name="before-<plan-name>")

Before Risky Changes

Before refactors or multi-file changes:

vigil_save(name="before-refactor") — named checkpoint
Make changes safely
If something breaks: vigil_diff first, then vigil_restore

Recovery

Always diff before restoring:

vigil_list() — see available checkpoints
vigil_diff(name="checkpoint") — preview what would change
vigil_restore(name="checkpoint") — restore files
Displaced files are preserved in .claude/vigil/artifacts/

Storage Management

Vigil has 3 named slots + 1 rotating ~quicksave:

~quicksave is ONE rotating slot — overwritten on each destructive command
Named checkpoints persist until deleted
Run vigil_list() periodically to check capacity
When nearing capacity (2+ named checkpoints), offer to clean up the oldest with vigil_delete(name="oldest")
vigil_restore preserves displaced files in .claude/vigil/artifacts/ — ask the user before cleaning those up

MCP Tools Reference

Tool	Purpose
`vigil_save`	Create named checkpoint (SHA-256 + gzip dedup)
`vigil_list`	List available checkpoints with metadata
`vigil_diff`	Preview changes since checkpoint
`vigil_restore`	Restore files from checkpoint
`vigil_delete`	Remove a checkpoint and free storage

Requires

claude mcp add vigil -- npx claude-vigil-mcp

---name: claude-vigildescription: File checkpoint and recovery — auto-quicksaves before destructive commands, INVOKE before implementing a plan or starting risky multi-file changes. Also use when user asks to undo changes or compare current state to a prior checkpoint.---# Vigil PluginFile recovery. Saves checkpoints before dangerous operations, diffs changes, restores files safely.## Hooks| Hook | When | Action ||------|------|--------|| **PreToolUse(Bash)** | Destructive command detected | Auto-quicksaves affected files (rm, mv, git reset, etc.) |Token cost: 0 on safe commands, ~30 on destructive.## Commands| Command | Description ||---------|-------------|| `/save-vigil <name> [files]` | Create a named file checkpoint || `/restore-vigil [name]` | Restore files from a checkpoint |## Workflows### Before Implementing a PlanAfter exiting plan mode, before writing any code:1. `vigil_save(name="before-<plan-name>")` — snapshot the project2. Implement the plan3. If something goes wrong: `vigil_diff(name="before-<plan-name>")` then `vigil_restore(name="before-<plan-name>")`### Before Risky ChangesBefore refactors or multi-file changes:1. `vigil_save(name="before-refactor")` — named checkpoint2. Make changes safely3. If something breaks: `vigil_diff` first, then `vigil_restore`### RecoveryAlways diff before restoring:1. `vigil_list()` — see available checkpoints2. `vigil_diff(name="checkpoint")` — preview what would change3. `vigil_restore(name="checkpoint")` — restore files4. Displaced files are preserved in `.claude/vigil/artifacts/`### Storage ManagementVigil has 3 named slots + 1 rotating `~quicksave`:- `~quicksave` is ONE rotating slot — overwritten on each destructive command- Named checkpoints persist until deleted- Run `vigil_list()` periodically to check capacity- When nearing capacity (2+ named checkpoints), offer to clean up the oldest with `vigil_delete(name="oldest")`- `vigil_restore` preserves displaced files in `.claude/vigil/artifacts/` — ask the user before cleaning those up## MCP Tools Reference| Tool | Purpose ||------|---------|| `vigil_save` | Create named checkpoint (SHA-256 + gzip dedup) || `vigil_list` | List available checkpoints with metadata || `vigil_diff` | Preview changes since checkpoint || `vigil_restore` | Restore files from checkpoint || `vigil_delete` | Remove a checkpoint and free storage |## Requires```claude mcp add vigil -- npx claude-vigil-mcp```

Frequently asked questions