We're excited to announce Skill Versioning & Releases—a version history for every skill, with the safety and control you already expect from shipping code.
The Problem: Skills Drifted
Until now, a skill was just one editable thing. You tweaked it, saved it, and whatever you saved was instantly live in everyone's Claude Code. That sounds convenient until:
- A "quick edit" breaks the skill for the whole team mid-afternoon.
- You want to go back to last week's version—and there's nothing to go back to.
- A half-finished draft accidentally becomes what everyone runs.
There was no history, no rollback, and no line between "I'm experimenting" and "this is what we run in production."
The Fix: Releases, Borrowed From Git
Skill versioning gives every skill a familiar mental model:
| Git | Skill versioning |
|---|---|
| Working directory | Draft — the live, always-editable skill |
| A commit | Release — a frozen, immutable snapshot |
git commit | New Release — freeze the draft into a release |
A stable tag | The stable pointer — the one release everyone runs |
git restore | Restore to draft — bring an old release back to edit |
A skill always has one editable draft. A release is a named, immutable snapshot of that draft—a title (required) plus optional release notes. Releasing copies the draft; your draft keeps living and drifting ahead, just like a working directory after a commit.
Stable Is What Everyone Runs
One release per skill is marked stable. That's the version Claude Code actually loads for your team. Your draft can be a mess of in-progress edits—it doesn't matter, because the stable release is what gets served.
The first release you ever cut auto-promotes to stable, so a skill becomes servable the moment it has its first release.
Promote to Ship, Promote to Roll Back
The stable pointer is movable. Promote points it at any release:
- Point it at your newest release → that's a normal ship.
- Point it at an older release → that's an instant rollback.
Either way it only moves the pointer. Your draft and your full release history are untouched. Broke something? Promote last week's release and you're back to safe in one click.
Restore an Old Release to Keep Building
Promote changes what runs. Restore to draft changes what you edit. Restore copies a chosen release's snapshot back into your live draft so you can evolve a known-good version forward—say, take v2, restore it, and build it into v6. (Because it overwrites your current draft, we confirm before it runs.)
These are independent actions: v2 can be the stable release and be restored into your draft at the same time.
No Surprise Drafts in Production
Here's the safety guarantee that makes all of this trustworthy: an unreleased skill is never served.
If a skill has no promoted stable release, Claude Code simply skips it—it does not fall back to your draft. So a half-written skill can sit in your workspace all day without ever reaching your team. A skill becomes servable only once it has a stable release.
Testing Drafts Safely: Experimental Mode
Sometimes you do want to run a draft against real Claude Code sessions before releasing it. That's what Experimental mode is for, and it's protected by a two-key gate—both keys must be turned:
- Flag the skill experimental — a per-skill toggle (the skill list's 3-dots menu has Mark experimental).
- Turn on Experimental mode in the CLI — the "Experimental mode" toggle in
superclawd config, off by default.
Only when both are on does that skill serve its live draft—and only on that one machine. Every other machine, and every other skill, keeps running the frozen stable release. So one developer can iterate on one risky skill against real sessions while the rest of the team stays on stable.
When the draft is good: cut a New Release, Promote it, and unflag experimental.
The Versions Page
Version management lives on a dedicated Versions page for each skill (reachable from a Versions button on the skill, and from the skill-list menu). There you can:
- Cut a New Release (title + optional notes).
- See the full release list (
v1…vN) with dates and authors. - Promote any release—including an older one to roll back. A Stable badge marks the current one.
- Restore to draft from any release.
Skill badges tell you the state at a glance: Stable or Draft, plus an amber Experimental badge when a skill is flagged.
Admins, maintainers, and owners manage versions; members get a read-only view.
Example: A Safe Iteration Loop
- Edit your skill's draft freely all week.
- Flag it experimental and turn on Experimental mode on your machine to test the draft live.
- Happy with it? Cut Release v5 with notes describing what changed.
- Promote v5 to stable—now the whole team runs it.
- A bug slips through? Promote v4 to roll back instantly while you fix the draft.
History intact, team safe, no guesswork.
Get Started
Skill versioning is available now in all SuperClawd workspaces.
- Go to app.superclawd.com
- Open a skill and click Versions
- Cut your first Release and watch it auto-promote to stable
Want the full mechanics—the stable pointer, promote/rollback, restore-to-draft, and the two-key experimental gate? Read the docs at docs.superclawd.com.
Pro tip: Make a habit of cutting a release before each workday's edits. Future-you will love having a clean point to roll back to.