mcpField
U
updating-bostonaholic-skills

updating-bostonaholic-skills

github.com/bostonaholicAgent workflows246 installsUpdated today
Repository

About updating-bostonaholic-skills

A skill that updates existing installations of the bostonaholic skills collection after a single confirmation. It plans changes first, applies only the confirmed plan, backs up refreshed copies, and leaves unsupported or retired copies untouched rather than installing or deleting skills.

Key features

  1. 01Previews an update plan
  2. 02Applies only a confirmed plan ID
  3. 03Backs up refreshed copies
  4. 04Stops when blockers require action
  5. 05Leaves excluded installs untouched

Use cases

  1. 01Update existing collection installations
  2. 02Review planned changes before applying
  3. 03Identify harnesses requiring user action

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/bostonaholic/skills --skill updating-bostonaholic-skills

After installing, type/updating-bostonaholic-skillsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
blockers-and-failures.md
scripts/
update.mjs

Details

From the project README

Updating bostonaholic skills

Brings each existing install up to the latest release, after one confirmation. It never installs into a harness that lacks the collection, and never adds a skill to a copy directory that did not hold it.

<skill-dir> is this skill's directory. The script needs node and git (check with command -v node git); it uses claude and codex where installed.

Rules

  • Confirm once. Show the whole plan. No answer is no change.
  • Apply only the confirmed id. A changed plan exits 3 and runs nothing.
  • Stop at blockers. Exit 4 means a harness needs the user's action first.
  • Never delete a skill. A retired or unrecognized copy is only reported.
  • Refreshed: the Claude Code and Codex plugins, the Cursor plugin clone (git pull --ff-only on its own branch, not the release tag), and any collection-named real copy in ~/.gemini/antigravity-cli/skills, ${XDG_CONFIG_HOME:-~/.config}/opencode/skills, ~/.cursor/skills, and ~/agent-data/workflows, whatever installed it. Each old copy is backed up.
  • Not touched: ~/.claude/skills, ~/.agents/skills, and project-level skills CLI installs. Point the user at the update command in INSTALL.md's "One skill" section.

Steps

  • Run node "<skill-dir>/scripts/update.mjs" plan and show its whole output; it changes nothing.
    • Exit 4: report each Blocked line, say what blockers and failures advises, stop.
    • Nothing to do.: report the left: lines and stop.
  • Ask the user to confirm the plan, or run apply with DRY_RUN=true first.
  • Run node "<skill-dir>/scripts/update.mjs" apply <plan-id> with the confirmed Plan id.
    • Exit 3: the machine changed; run the plan again and confirm again.
    • Exit 1: it names the failed step and the steps not run; report the stderr and what the reference advises, and do not retry blindly.
  • Run the plan again and expect Nothing to do.. A Claude Code or Codex step that still shows a gap means its marketplace serves an older version than the release; report that gap.
  • Report each step run, each left: line, and the backup directory.
  • Tell the user which harnesses to restart:
    • Claude Code: a new session, or /reload-plugins.
    • Codex: a new thread.
    • Antigravity, OpenCode, Cursor (plugin and skills): restart the app.
    • Grok Bot: no restart is documented; confirm under Settings > Plugins > Yours.

Comments

Markdown supported