How to Back Up Claude Skills and Version AI Skills

What You Are Actually Backing Up

Search intent for backup Claude Skills is informational with a practical risk: people have built useful AI workflows and do not want to lose them. The backup target is not just a Markdown file. It is the repeatable behavior you rely on when Claude Code, Codex, or another agent does work for you.

A skill backup should preserve three things: the instruction entrypoint, the supporting context, and the history of how the workflow changed. Without all three, you may have a file that looks correct but no longer produces the answer you trusted.

Backups are only real after you have restored from them.

Step 1: Inventory Every Skill Source

Start by listing the places where skills and reusable prompts live today. Most people discover more locations than they expected: personal Claude Code folders, project folders, old repos, shared docs, chat snippets, and a previous laptop.

1. Check personal Claude Skills in ~/.claude/skills.
2. Check project skills in active repos under .claude/skills.
3. Check saved prompts that should become skills before they disappear.
4. Mark each workflow as personal, project-specific, or shared with a team.
5. Pick the current version when duplicate folders do the same job.

If you are not sure what belongs in personal vs project scope, use the Claude Code skills folder guide before you standardize the backup.

Choose a Backup Method Before You Copy Files

The right backup method depends on whether you need a one-time safety copy, reviewable history, or a portable library that follows you across tools. Do not choose based only on what is fastest today.

Step 2: Back Up the Whole Skill Folder

A Claude Skill can be a single SKILL.md, but many useful skills become multi-file packages. They may include examples, templates, reference documents, scripts, or assets. Backing up only the entrypoint can silently break the skill.

# Create a dated archive of personal Claude Skills
mkdir -p ~/ai-skill-backups
tar -czf ~/ai-skill-backups/claude-skills-2026-07-19.tgz -C ~/.claude skills

# Inspect the archive before trusting it
tar -tzf ~/ai-skill-backups/claude-skills-2026-07-19.tgz | head

For project skills, back up the whole repo or copy the project skill folders into the same archive with clear labels. If a project skill depends on repo documentation, keep that relationship visible in the backup note.

The folder is the unit of backup for AI skills.

Step 3: Add Version History, Not Just Storage

Storage answers "where is the file?" Version history answers "what changed, who changed it, and how do I get back?" That difference matters when a small edit makes a skill worse.

mkdir -p ~/ai-skills-versioned
cp -R ~/.claude/skills/* ~/ai-skills-versioned/
cd ~/ai-skills-versioned
git init
git add .
git commit -m "Back up Claude Skills before library cleanup"

Use commit messages that explain behavior changes, not just file movement. "Tighten support escalation skill output" is more useful than "update skill." When a skill starts producing weaker answers, the history should help you identify the change that caused it.

Step 4: Move From Backup to a Portable Library

Backups protect against loss. A portable library protects against rebuilds. If your skills live only on one laptop, every new machine, repo, or agent turns into another migration project.

Prompttly is a skill manager for AI agents — one library for your skills and prompts that syncs into Claude Code, Codex, ChatGPT, and Claude, so your setup follows you across every machine, repo, and tool.

In that model, the cloud library is the source of truth and local folders are working copies. Claude Code and Codex can use real skill folders, while ChatGPT and Claude can reach the same workflows with // commands. If a skill improves, the next machine should receive the current version instead of a stale export.

Versioning is how a skill becomes dependable instead of lucky.

Step 5: Run a Restore Test

Most people test backups after something has already gone wrong. Do it while the original files are still available. Pick one important skill, restore it into a temporary location or another machine, and run the same real task you use in production.

1. Restore one complete skill folder from the backup.
2. Confirm the folder contains SKILL.md and every referenced support file.
3. Run a realistic prompt that should activate the skill.
4. Compare the output with the known-good version.
5. Record the restore steps where future you can find them.

If you are setting up a replacement laptop, pair this with the new-computer Claude Code transfer checklist. If two machines will stay active, use the Claude Skills sync guide instead of relying on one-off archives.

Backup Checklist for AI Skills

• Complete folders: Save SKILL.md, examples, templates, references, scripts, and assets together.
• One source of truth: Decide whether the canonical copy lives in Git, a cloud library, or a skill manager.
• Version notes: Describe behavior changes so rollback is possible.
• Duplicate cleanup: Merge overlapping skills before backing up five stale variants.
• Restore proof: Test at least one high-value skill from backup.
• Tool coverage: Confirm important skills can still reach the agents where you use them.

Common Backup Mistakes

The highest-risk backup mistakes are the ones that look successful at a glance. A folder exists, an archive opens, or a repo has files, but the workflow is still incomplete.

• Backing up only SKILL.md: Multi-file skills lose the examples and templates that make them reliable.
• Keeping five similar versions: Backups should reduce uncertainty, not preserve every stale duplicate forever.
• Skipping restore tests: An untested archive is a guess.
• Mixing project secrets into shared backups: Keep sensitive or repo-specific details scoped correctly.
• Using storage without ownership: Team skills still need someone responsible for updates.

Related Resources

Start from the resources hub for the full Claude Skills series. Use how to share Claude Skills with your team when backups become a team library, global skills across projects when duplicated repo skills need cleanup, and the free Claude Skill Creator when an old prompt should become a reusable skill before you version it.

People Also Ask About Backing Up Claude Skills