Guides · Updated November 19, 2026

How to update an agent skill and see what changed

By Tineessa Nelson, Use This Skill

To update an agent skill, replace its folder with the newer version from its source: gh skill update does this for skills installed with GitHub CLI, npx skills update for the skills CLI, and re-running your npx degit command with --force for a plain copy. Read what changed before you accept it. Of 1,972 public skills we track, 301 changed in the 30 days to November 19, 2026.

An update is a new version of instructions your agent will follow, and sometimes new scripts it will run. The commands below are quick; the step that matters is reading the change first.

How often do agent skills change?

We cloned all 47 GitHub repositories in this directory's November 16 crawl on November 19, 2026, and counted the commits that touched each skill's folder, at its current path, on the default branch.

Window (to November 19, 2026) Skills whose folder changed Repositories
Last 7 days (since November 12) 110 of 1,972 23 of 47
Last 30 days (since October 20) 301 of 1,972 35 of 47
Last 90 days (since August 21) 849 of 1,887 42 of 44
No commit in 90 days 1,038 of 1,887 2 repositories with no change at all

Source: Use This Skill directory (data/skills.json, crawl of November 16, 2026); each repository cloned on November 19 with history back to August 2026 and read by script. Three repositories (85 skills) were left out of the 90-day row because the clone did not reach back to August 21. Of the 1,038 skills with no commit in 90 days, 851 sit in one repository, ComposioHQ/awesome-claude-skills, whose latest commit is from July 24, 2026.

Most changed skills had one commit in the 30 days (the median), but a few move fast: reverse-engineer-anything (morluto/rea) had 149, e2e (tester-army/e2e) 130 and kordoc 99. Of the 301 that changed:

  • 268 had their SKILL.md edited, so the instructions themselves changed.
  • 30 had a script changed (a .py, .sh, .js, .ts or similar file), which is code the agent may run.
  • 113 had other files changed: reference notes, data files, templates and assets.
  • 33 changed without any edit to SKILL.md, so reading SKILL.md alone would have missed the update.

Do proven skills change after they are proven?

Yes. A proof runs the same brief three times without a skill and three times with it, and records the exact commit of the skill it used. On each skill page that commit is shown next to the result. We compared that commit with the skill's folder on GitHub today for the 37 proven skills that are in the November 16 crawl. Ten have changed since they were proven:

Skill Proven Commits since What changed
design-taste-frontend Oct 24 57 SKILL.md edited; 32 files removed and 1,625 added, 1,600 of them under assets/
ui-ux-pro-max Oct 19 12 SKILL.md and data files: 19 changed, 7 added
brainstorming Oct 21 2 SKILL.md and scripts/start-server.sh
mcp-builder Oct 21 1 SKILL.md, one reference file edited, one added
vercel-react-view-transitions Oct 21 1 SKILL.md and AGENTS.md
improve-codebase-architecture Oct 24 1 SKILL.md
grilling Oct 24 1 SKILL.md
systematic-debugging Oct 19 1 Five test and log files removed; SKILL.md unchanged
ui-styling Oct 24 1 Two scripts
design-system Nov 1 1 Three scripts edited and one test added

Source: data/proofs.json (skillCommit and provenAt for each proof) compared by script with each repository's default branch on November 19, 2026. The other 27 proven skills are unchanged since their proof. We have not re-run any proof on the newer versions, so we cannot say whether the results still hold.

When you update a proven skill, the proof describes the version you had, not the one you are installing. For a large change such as design-taste-frontend's, treat the new version as a different skill and judge it again, for example with the method in how to test whether a skill actually helps.

Which command updates a skill?

It depends on how you installed it.

How you installed it How to update Notes
gh skill install (GitHub CLI) gh skill update, or gh skill update name for one skill Compares the tree SHA in SKILL.md front matter with the repository. Asks before updating; --all skips the prompt; --dry-run only reports. Pinned skills are skipped unless you pass --unpin.
npx skills add (skills CLI) npx skills update, or name the skills -p for project skills only, -g for global only, -y to skip the scope prompt.
npx degit or a manual copy Run the same degit command again with --force degit's help describes --force only as allowing a non-empty destination, so delete the folder first if you want files removed upstream to go too.
Committed in your repository Re-copy with any of the above, then review the change with git diff before you commit The commit history shows what each update brought in.
Codex $skill-installer Codex's skills page describes no separate update command Re-install, or manage the skill through one of the tools above.
Part of a plugin Update the plugin, not the skill on its own See plugin vs skill.

GitHub CLI checks agent folders for Copilot, Claude, Cursor, Gemini, Antigravity and Grok, in both project and user scope, according to its manual. If you installed a skill some other way, gh skill update in interactive mode asks for its source repository and adds the metadata it needs, so later updates work on their own.

Do I need to restart the agent after updating?

Usually not in Claude Code or Codex.

Claude Code's documentation says it watches ~/.claude/skills/, the project's .claude/skills/ and a .claude/skills/ inside an --add-dir directory, and picks up an added, edited or removed skill within the current session. Two exceptions: run /reload-skills if the top-level skills folder did not exist when the session started, and note that "live change detection covers SKILL.md text only". For a skill folder that is also a plugin, changes to hooks/, .mcp.json, agents/ and output-styles/ need /reload-plugins. Watching is off in bare mode.

Codex's documentation says it "detects skill changes automatically" and to restart Codex if an update does not appear.

How do I see what changed before I update?

  • With GitHub CLI, run gh skill update --dry-run to list the skills that have updates without changing any files.
  • On GitHub, open the skill's folder and its history, and compare the commit you installed (gh skill records it; a proof page shows it) with the latest one. Read script changes first: they are what runs on your computer.
  • In your repository, commit the skills folder before updating, update, then run git diff on that folder. You see every changed line, including files that are not SKILL.md, which matters for the 33 skills above that changed without a SKILL.md edit.

Should I check a skill again after updating it?

Yes, if the update touched scripts or added files. The weekly scan reads each skill as it was on scan day, and 84 skills in this directory had commits after the November 16 scan, in 18 repositories; 8 of those changes touched scripts.

Updates rarely flip a scan result. Across the last two weekly scans, two skills changed status, both toward clear: argent-ios-device-setup went from review to clear on November 9, and open-source (browser-use) from flagged to clear on November 16. But a scan describes one version, so check the one you are installing.

The live skill check reads a public GitHub repository or folder. For a skill that is already in this directory, a link to the default branch returns the weekly scan result; to check the newest version, paste a link that names the commit, such as github.com/owner/repo/tree/<commit>/path/to/skill. The same check is available inside Claude, Cursor or any MCP client through the check_skill tool in the connector.

Should I pin a skill instead of updating it?

Pin the skills a team depends on, so that the version everyone reviewed is the version everyone runs. With GitHub CLI, install with --pin and a tag or commit; with degit, add # and a tag, branch or commit to the source. Pinned skills are skipped by gh skill update, so you upgrade when you choose. How to install a skill from GitHub covers pinning in more detail, and how to share skills with your team covers keeping a team on one version.

We did not install or update any of these skills for this page; the counts come from the repositories' public history.

Questions

Will updating a skill overwrite my own edits?

It can. GitHub CLI's manual says gh skill update --force re-downloads a skill and overwrites locally modified files with their original content, though it does not delete extra files you added. Re-running degit with --force writes over files of the same name. Keep your changes in a separate skill, or commit the skills folder so git shows you what an update replaced and lets you restore it.

Can gh skill update handle a skill I copied by hand or installed with another tool?

Yes, in interactive mode. The manual says gh skill update asks for the source repository of a skill that has no GitHub metadata, then re-downloads it with the metadata added so later updates work on their own. With --all, or when nothing can prompt, it skips those skills with a notice.

How often should I update my skills?

There is no fixed rule, and most skills do not change often: 1,671 of the 1,972 public skills we track had no commit to their folder in the 30 days to November 19, 2026. Checking monthly with gh skill update --dry-run, or whenever a skill starts behaving differently, is a reasonable rhythm. Pin the skills your team depends on and move the pin on purpose.