pluginslisted

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 actionable report. Actions: sync (default, mutating), audit (read-only dry run), converge (explicit scope consolidation). Use when: 'sync plugins', 'update my plugins', 'are my plugins current', 'check plugin drift', 'converge plugin scopes', or before relying on a plugin that might be stale.
melodic-software/claude-code-plugins · ★ 13 · AI & Automation · score 73

Install: claude install-skill melodic-software/claude-code-plugins

## Variables Arguments: `$ARGUMENTS` ## Scope Guarantees that the plugins which actually load, for the machine's user scope, and for any repo you're standing in with its own project/local-scope installs, are the latest published versions of everything the marketplace offers, and surfaces any state where something older or unintended is what really runs. Distinct from what Claude Code's own background `autoUpdate` does (see [context/scope-semantics.md](context/scope-semantics.md)): `autoUpdate` silently refreshes marketplace data and bumps already-installed plugins post-startup. It never installs a new catalog plugin, never checks `enabledPlugins` completeness, never detects or reports scope divergence, and only runs once per session start on its own schedule, not on demand. This skill covers exactly that gap. Distinct from `claude-config`'s `audit` skill's plugin-drift check: that check compares a project's committed `enabledPlugins` against a marketplace's *upstream* `marketplace.json` (orphan/new/rename plugin names). This skill compares the *local, already-installed* state (`installed_plugins.json`, per-scope `enabledPlugins`) against the *local* marketplace catalog, a different axis (install/scope completeness, not settings-vs-upstream drift). **Never silently fixes drift it finds.** `sync` mutates only via the documented CLI actions below, and never writes a committed `.claude/settings.json`: its Step 5 enables automatically only at `user` and `local` scope, and re