Skip to content
Skills Library
AI & agents · Automation

update-plugins

/update-plugins

Check which Claude Code marketplaces and plugin installs (user, project and local scope, across all project folders) are out of date, recommend what to update, and update what the user confirms. Use when the user asks to update plugins, check for plugin updates, or sync plugin versions across repos.

Author
lttr ↗
Licence
MIT
Last repository change
22.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/check-plugins.sh, scripts/update-plugins.sh

What it does and when to use it

Check which Claude Code marketplaces and plugin installs (user, project and local scope, across all project folders) are out of date, recommend what to update, and update what the user confirms. Use when the user asks to update plugins, check for plugin updates, or sync plugin versions across repos.

Original author description

Check which Claude Code marketplaces and plugin installs (user, project and local scope, across all project folders) are out of date, recommend what to update, and update what the user confirms. Use when the user asks to update plugins, check for plugin updates, or sync plugin versions across repos.

How it works

  1. Prerequisites
  2. Workflow
  3. Failures
Original SKILL.md headings · 45 lines, 413 words
SKILL.md preview
---
name: update-plugins
description: Check which Claude Code marketplaces and plugin installs (user, project and local scope, across all project folders) are out of date, recommend what to update, and update what the user confirms. Use when the user asks to update plugins, check for plugin updates, or sync plugin versions across repos.
disable-model-invocation: true
allowed-tools: Bash(${CLAUDE_SKILL_DIR}/scripts/check-plugins.sh), Bash(${CLAUDE_SKILL_DIR}/scripts/check-plugins.sh:*)
---

# Update plugins

Every plugin install is recorded in `~/.claude/plugins/installed_plugins.json` with its scope and, for local and project scope, its project folder. Each install stays on its own version until it is updated from that folder, so `claude plugin update` in one repo leaves the others behind. The user usually doesn't know what is outdated where. Find out, recommend, and ask before changing anything.

## Prerequisites

- `bash` 3.2 or newer (macOS default is fine; on Windows, Git Bash), `jq`, `git`

## Workflow

1. Run the read-only check:

   ```bash
   ${CLAUDE_SKILL_DIR}/scripts/check-plugins.sh
   ```

   It prints two tab-separated tables:
   - `# marketplaces`: name, last update date, and whether the local clone is `up to date`, `behind remote`, `remote unreachable` or `not a git clone`.
   - `# installs`: status, scope, plugin, installed version, latest version in the local clone, project folder. Statuses: `outdated`, `current`, `dir missing`, `latest unknown`, `not in marketplace`, `ahead of clone`.

2. Report, most useful first:
   - **Marketplaces behind remote.** "Latest" comes from the local clone, so recommend refreshing these first; it may reveal more updates.
   - **Outdated installs**, grouped by scope (user, then local, then project), and within a scope by plugin with version jump and folder count. Name the folders only when there are few.
   - **Stale records** (`dir missing`) and `not in marketplace` (plugin removed or renamed upstream), as one short line each. These can't be updated.
   - Skip `current` entirely.

3. Ask what to do with numbered options, e.g. refresh marketplaces, update everything outdated, only user scope, only one plugin. Recommend one. Do nothing until the user answers.

4. Do what the user picked:
   - Refresh marketplaces: `claude plugin marketplace update <name>` for each chosen one. There is a single clone per marketplace whatever scope declared it, so this changes the catalog for every project. Then rerun the check and report newly outdated installs before updating anything.
   - Update installs: pipe the chosen rows from the check into the update script, selecting with `awk` on status, scope, plugin or project:

     ```bash
     ${CLAUDE_SKILL_DIR}/scripts/check-plugins.sh \
       | awk -F'\t' '$1 == "outdated" && $2 == "user"' \
       | ${CLAUDE_SKILL_DIR}/scripts/update-plugins.sh
     ```

5. Report the result. Running sessions in updated folders need a restart to load the new versions.

## Failures

A `FAILED` update usually means the plugin needs a marketplace-declared command confirmed, which requires a TTY. Don't retry with `-y`: that would accept a command nobody reviewed. Tell the user to run it themselves: `! cd <dir> && claude plugin update <plugin> --scope <scope>`.
Files in this package (3)
  • SKILL.md 3 KB
  • scripts/check-plugins.sh 3 KB
  • scripts/update-plugins.sh 1 KB

Versions

The database has no other skills named update-plugins.

Database snapshot: 13.11.2026 · package version 4310ba95e5ba (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90upkeep
    Keep a project's plugins current — refresh the marketplaces, update installed plugins that have a newer version, and offer plugins new to the marketplaces the project uses, then hand over /reload-plugins. Use on /upkeep, when the upkeep notice says updates or new plugins exist,…
  • 100refresh-plugin-cache
    This skill should be used when the user asks to "refresh the plugin cache", "update plugin cache", "sync plugin cache", "update installed plugins", "check for plugin updates", "are my plugins up to date", "is the plugin cache fresh", or "verify plugin versions". Scoped to…
  • 100update-plugin
    Refreshes the domain-expert marketplace catalog and updates installed Domain Expert plugins (domain-expert-core plus any per-domain plugin such as database, security, devops, os) to their latest versions. Also handles migrating off the old pre-marketplace monolithic…
  • 84plugins
    Bring a machine's plugin fleet current on demand: marketplace refresh, update the plugins that actually load (including in-repo project/local-scope installs), install new catalog plugins per policy, detect scope divergence, and surface (never silently fix) drift, with a terse…
  • 100claude-plugins
    Reference for building and distributing Claude Code plugins — plugin.json and marketplace.json structure, bundling commands, agents, skills and hooks, versioning, and publishing a marketplace. Use when creating or packaging a plugin, setting up a marketplace, or debugging why a…
  • 95plugin-writer
    Create new Claude Code plugins from scratch with proper directory structure (.claude-plugin/plugin.json, skills/, agents/), or add existing plugins to marketplace.json. Use when creating a plugin, setting up plugin metadata, configuring MCP servers, or adding plugins to a marketplace.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.