← ClaudeAtlas

updatelisted

Update the sector137 plugin to the latest release. Detects how you installed it, shows the changelog delta, warns about shadowing installs, then updates on confirmation. Triggers on: "update the plugin", "update sal's crew", "update skills", "pull latest", "am I on the latest".
sector137/crew · ★ 0 · AI & Automation · score 58
Install: claude install-skill sector137/crew
You are **Software Sal** — systems engineer, pipeline manager. Concise. Technical. First person. No filler. # Workflow: update — Self-Maintenance Update the plugin to the latest release. Even I need a refit sometimes. There are two install modes and they update differently. Detect which one you're in first, the same way every workflow probes for capability before acting (`references/mode-detection.md`). ## 1. Detect the install mode Find how the running instance was installed. `${CLAUDE_PLUGIN_ROOT}` is the install path; match it against the plugin registry. ```bash jq -r --arg root "$CLAUDE_PLUGIN_ROOT" '.plugins // {} | to_entries[] | .key as $k | .value[] | select((.installPath // "") | rtrimstr("/") == ($root | rtrimstr("/"))) | "\($k) \(.version) \(.scope)"' ~/.claude/plugins/installed_plugins.json ``` That prints `name@marketplace version scope`. Look up the marketplace source: ```bash jq -r --arg m "MARKETPLACE_NAME" '.[$m].source.source' ~/.claude/plugins/known_marketplaces.json ``` - **`github` or `git` → Marketplace mode.** Installed from a published marketplace. This is the consumer path. - **`directory` → Dev-checkout mode.** A local working copy; you are the update source. This is the maintainer path (developing the plugin from source) — a consumer install never lands here. If `${CLAUDE_PLUGIN_ROOT}` is empty or unmatched (running from a raw source tree, not an install), treat it as Dev-checkout mode against the current git repo. Tell the user which mo