Skip to content
Skills Library
AI & agents · Automation

wright

/wright

Update Claude Code marketplace plugins from inside a session — all of them, or one by fuzzy name. Use when the user wants to update plugins, refresh a plugin, or asks how to update mad-skills / superpowers / a specific plugin without the interactive picker.

Repository
mad-skills ↗
Licence
MIT
Last repository change
03.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
4
Scripts
2
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 03.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/update-plugins.py, scripts/update-plugins.test.js

What it does and when to use it

Update Claude Code marketplace plugins from inside a session — all of them, or one by fuzzy name. Use when the user wants to update plugins, refresh a plugin, or asks how to update mad-skills / superpowers / a specific plugin without the interactive picker.

Arguments

/wright <plugin-name>, --dry-run (both optional)
Original author description

Update Claude Code marketplace plugins from inside a session — all of them, or one by fuzzy name. Use when the user wants to update plugins, refresh a plugin, or asks how to update mad-skills / superpowers / a specific plugin without the interactive picker.

How it works

  1. Output Formatting
  2. Argument
  3. Pre-flight
  4. Flow
  5. Notes
  6. Report to User
Original SKILL.md headings · 193 lines, 1,290 words
SKILL.md preview
---
name: wright
description: Update Claude Code marketplace plugins from inside a session — all of them, or one by fuzzy name. Use when the user wants to update plugins, refresh a plugin, or asks how to update mad-skills / superpowers / a specific plugin without the interactive picker.
argument-hint: <plugin-name>, --dry-run (both optional)
allowed-tools: Bash
---

# Wright - Plugin Updater

When this skill is invoked, IMMEDIATELY output the banner below before doing anything else.
Pick ONE tagline at random — vary your choice each time.
CRITICAL: Reproduce the banner EXACTLY character-for-character, including the diagonal `/` glyph before the name.

```
{tagline}

       /$$ /$$      /$$ /$$$$$$$  /$$$$$$  /$$$$$$  /$$   /$$ /$$$$$$$$
      /$$/| $$  /$ | $$| $$__  $$|_  $$_/ /$$__  $$| $$  | $$|__  $$__/
     /$$/ | $$ /$$$| $$| $$  \ $$  | $$  | $$  \__/| $$  | $$   | $$   
    /$$/  | $$/$$ $$ $$| $$$$$$$/  | $$  | $$ /$$$$| $$$$$$$$   | $$   
   /$$/   | $$$$_  $$$$| $$__  $$  | $$  | $$|_  $$| $$__  $$   | $$   
  /$$/    | $$$/ \  $$$| $$  \ $$  | $$  | $$  \ $$| $$  | $$   | $$   
 /$$/     | $$/   \  $$| $$  | $$ /$$$$$$|  $$$$$$/| $$  | $$   | $$   
|__/      |__/     \__/|__/  |__/|______/ \______/ |__/  |__/   |__/   
```

Taglines:
- 🔧 Tightening every bolt in the toolbox...
- 🛠️ The wright is in — fixing up your plugins!
- ⚙️ Refitting the fleet, one plugin at a time...
- 🪚 A little maintenance never hurt anybody!
- 🧰 Checking the workshop for stale tools...
- 🔩 Bringing everything up to spec!
- 🏗️ Overhaul in progress...
- 📐 Measure twice, update once!

---

## Output Formatting

After the banner, display parsed input:
```
┌─ Input ────────────────────────────────────────
│  Target:   {plugin name or "all installed"}
│  Flags:    {parsed flags or "none"}
└────────────────────────────────────────────────
```

Pre-flight results:
```
── Pre-flight ───────────────────────────────────
  ✅ {dep}           {version or "found"}
  ⚠️ {dep}           not found → {fallback detail}
  ❌ {dep}           missing → stopping
──────────────────────────────────────────────────
```

Status icons: ✅ done · ❌ failed · ⚠️ degraded · ⏳ working · ⏭️ skipped

---

Update installed Claude Code plugins by orchestrating the `claude plugin`
CLI — the CLI does the real work (refreshing marketplace sources, including
the GCS-backed official one, resolving versions, populating the cache); this
skill adds only what the CLI itself lacks on its own: updating everything in
one call, and targeting one plugin by fuzzy name instead of its exact
`plugin@marketplace` id.

## Argument

Parse the optional argument and flag from the request:
- *(empty)* — target every installed plugin
- `<name>` — fuzzy-matched against installed plugins (e.g. `super` → `superpowers`)
- `--dry-run` — resolve targets and print what would run, without executing
  anything. The CLI has no check/preview mode of its own, so this can only
  list targets and their current versions, not the versions available.

## Pre-flight

| Dependency | Type | Check | Required | Resolution | Detail |
|-----------|------|-------|----------|------------|--------|
| claude | cli | `claude --version` | yes | stop | This skill runs inside a Claude Code session — if the CLI itself isn't on PATH something is very wrong; stop and report |
| python3 | cli | `python3 --version` | yes | url | Install from https://www.python.org/downloads/ — the engine script is Python (reuses `difflib` for fuzzy name matching rather than reimplementing it) |

For each row, in order:
1. Run the Check command
2. If found: continue silently
3. If missing: apply Resolution strategy
   - **stop**: notify user with Detail, halt execution
   - **url**: notify user with Detail (install link), halt execution
4. After all checks: summarize what's available

## Flow

Engine: `skills/wright/scripts/update-plugins.py`. Runs the updates by
default; `--dry-run` previews only. Run via Bash, resolving the skill root
the same way every other skill in this plugin does:

```bash
for SKILL_ROOT in \
  "${CLAUDE_PLUGIN_ROOT:-}" \
  "$HOME/.claude/plugins/marketplaces/slamb2k" \
  "$(dirname "$(readlink -f "$0")")/.."
do
  [ -f "$SKILL_ROOT/skills/wright/scripts/update-plugins.py" ] && break
done

python3 "$SKILL_ROOT/skills/wright/scripts/update-plugins.py" [<query>] [--dry-run]
```

1. **Update (default).** Runs `claude plugin marketplace update` (every
   marketplace, or just the one marketplace for a single fuzzy-matched
   target), then `claude plugin update <id>` per target, and reports a
   `PLUGIN / BEFORE / AFTER / STATUS` table by diffing `claude plugin list`
   before and after. The final line is
   `WRIGHT_RESULT applied=true updated=<n> names=<…> failed=<n> failed_names=<…> marketplaces_failed=<…>`.
   **One failure never stops the run:**
   - If the bulk refresh fails, each needed marketplace is refreshed on its own.
   - Plugins whose marketplace still can't be refreshed are **skipped**.
   - A plugin whose `claude plugin update` fails is recorded as **failed**.
   - Every other plugin is still updated. The script exits `0` when everything
     succeeded and `2` when the run was partial, and prints each failure with
     its reason plus a retry hint for each unreachable marketplace.
2. **Preview (`--dry-run`).** Resolves and lists the targets and their
   current versions without touching anything, ending with
   `WRIGHT_RESULT applied=false targets=<n>`.
3. **No installed plugins:** the script exits non-zero with
   `no installed plugins found` on stderr — relay that directly.
4. **Unmatched query:** the script only matches an exact base name or a
   substring (unique, or narrowed by closeness among genuine substring
   candidates) — it deliberately has no catch-all fuzzy fallback across the
   whole install list, because that tier used to match clearly-unrelated
   queries (e.g. `nonexistent-xyz` → `context7`) often enough to be worse
   than admitting no match. On a miss it exits non-zero with
   `no installed plugin matches '<query>' — installed: <comma-separated
   names>` on stderr. **Use that list yourself**: if the intended plugin is
   reasonably inferable from context (a near-miss spelling, a name you
   recognize from the conversation), say which one you picked and why, then
   re-run with the exact name; if it's genuinely ambiguous, ask the user
   rather than guessing.

Fuzzy matching (exact base name → unique/closest-among-candidates substring)
is the entire reason this is Python rather than bash: reusing `difflib`
beats hand-rolling string-distance matching in shell.
`ponytail: no dry-run version-delta preview — the CLI has no check mode, so
--dry-run can only show current versions, not what's available. Upgrade path:
none needed unless the claude CLI itself grows a preview mode to build on.`

**Restart to apply.** The CLI updates the install on disk, but this running
session keeps the old code until it restarts — tell the user to restart the
session (or their client) so the new versions actually load, naming what
changed from the `names=` list.

## Notes

- Superpowers and the other `claude-plugins-official` plugins are covered
  the same way as any other plugin here: `claude plugin marketplace update`
  refreshes the GCS-backed manifest their marketplace lives in.
- Fuzzy match is exact-base → unique-substring → closest; an ambiguous or
  absent query stops with a clear message rather than guessing wrong.
- `scripts/update-plugins.test.js` runs the engine against a fake `claude`
  CLI on `PATH` to cover the partial-failure paths (bad marketplace, failed
  plugin update, bulk-only refresh failure, single target);
  `tests/evals.json` covers the skill-level behavior.

## Report to User

```
┌─ Wright · Report ──────────────────────────────
│
│  ✅ Update complete            (⚠️ Partial update — exit 2)
│
│  🔧 Target:   {plugin name or "all installed"}
│
│  📊 Plugin            Before      After       Status
│     {name}            {version}   {version}   ↑ updated
│     {name}            {version}   {version}   = current
│     {name}            {version}   {version}   ⏭ skipped
│     {name}            {version}   {version}   ✗ failed
│
│  ❌ Not updated                (only when failed > 0)
│     • {name}: {reason}
│     • hint: {retry hint for each failed marketplace}
│
│  ⚡ {n} updated — restart your session to apply {names}
│     (or: "All already current. Nothing to restart.")
│
└─────────────────────────────────────────────────
```

Status is always shown as symbol **and** word — never colour alone. On a
partial run, keep the list of updated plugins, and put the failures with their
reasons in the report; don't retry them unasked. If a marketplace fails with a
git error, the hint's `git -C ~/.claude/plugins/marketplaces/<m> pull --ff-only`
is a safe fix to offer — it only fast-forwards that marketplace's clone.

If `--dry-run`, replace the report with the script's target list and note
that nothing was executed — no report box needed for a preview.
Files in this package (4)
  • SKILL.md 10 KB
  • scripts/update-plugins.py 8 KB
  • scripts/update-plugins.test.js 5 KB
  • tests/evals.json 3 KB

Versions

The database has no other skills named wright.

Database snapshot: 13.11.2026 · package version 80f8fdfc347b (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

  • 100update-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.
  • 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…
  • 100import-plugins
    Bring plugins the user already installed in Claude Code or Codex into Kiro, or import one straight from a marketplace GitHub URL. Use when the user mentions Claude Code plugins, Codex plugins, a plugin marketplace, or asks to bring, move, port or migrate their plugins to Kiro.…
  • 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.
  • 100plugin-marketplace
    Guide for creating and managing Claude Code plugin marketplaces. Use when setting up a marketplace, validating marketplace.json, or distributing plugins.
  • 100plugin-marketplace-creator
    Create and configure Claude Code plugin marketplaces hosted on GitHub. Use this skill when users want to set up a new plugin marketplace repository, add plugins to an existing marketplace, configure team distribution settings, or troubleshoot marketplace issues. Triggers include…

Feedback and reports

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