Black Friday: Lock in your founding rate.Compare plans

Every Premium Skill for $19.9/month. Cancel anytime. See plans

Skip to content

Update, roll back and remove Agent Skills

Treat a Skill like any other dependency. Note where it came from, update it on purpose, and learn where the backup lands before you need it.

For
People who maintain Skills
Works with
Claude Code, Codex, Cursor
Time
8 min

The short answer

To update a Frontier Brief Skill, run its install command again with --force. The CLI first moves the current copy into .fable5/backups/ beside your Skills and prints the path. There is no separate update or uninstall command.

Keep a brief record

Months later, a teammate opens .claude/skills/ours-saas-product-site/ and wonders if it’s safe to edit. Four README lines answer that:

README.md
## Agent Skills used here
- ours-saas-product-site: installed from The Frontier Brief (/skills/ours-saas-product-site)
  version 1.2.0, Claude Code, project folder .claude/skills
  local edit: our palette, kept in references/colors.md

How to update an installed Skill

Updating means installing again with --force. The CLI fetches the newest version and swaps the whole folder, so review before and test afterwards:

  1. 1

    Check the Skill’s page for changes, above all to scripts, Dependencies and Outside costs.

  2. 2

    Rerun the install with --force and the same agent or target as before. Without the flag the CLI halts with “already exists. Add --force to replace it; the current copy is moved to a backup first.”

    Terminal
    npx --yes fable5-cli@latest install <slug> --force

    You should see: Installed <slug> <version> in … followed by The previous copy was moved to …

  3. 3

    Do your normal check: one run by name, one in plain words.

Edited the Skill yourself? After --force, those edits live only in the backup. Save them elsewhere first, or hold them in references/ so reapplying is easy.

Undo an update that went wrong

Each forced install parks the old copy next to your Skills, say in ~/.agents/skills/.fable5/backups/<slug>-<time>-<id>/. Agents never load it. To revert, delete the live <slug>/ folder, then move the backup into that place and rename it <slug>.

When an install breaks partway through, the CLI puts the old copy back on its own.

Uninstall a Skill

Removing one means deleting its folder. Then check your personal and project folders for a second copy under the same name. Claude Code ranks a personal copy above a project one, so a forgotten duplicate can make a later update seem ignored. Skill locations lists every folder.

Give the team one shared copy

Commit one checked copy into the repo’s Skills folder and list what it depends on, so the whole team runs one version. For a Frontier Brief Skill, add --target:

Terminal, from the repo root
npx --yes fable5-cli@latest install <slug> --target ./.claude/skills

Common questions

What’s the simplest way to update a Claude Skill?

Rerun The Frontier Brief install command with --force, or swap in a complete new folder at ~/.claude/skills/. Claude Code picks the change up in the open session.

Why is my updated Skill still doing the old thing?

Usually a same-named copy lives in another folder, or only SKILL.md was swapped. Search the personal and the project folders, then keep a single complete copy.

How can I undo a Skill update?

Delete the live <slug>/ folder, move the backup out of .fable5/backups/ and rename it <slug>. Each update prints the backup path.

How do I remove a Skill?

Delete its folder. Since The Frontier Brief CLI offers no uninstall command, check afterwards for any copy left behind under that name.

Sources

Did this guide help?