agentleFS
Sign inStart free
matthewdigiuseppematthewdigiuseppe/MStack/skills/mstack-upgrade/SKILL.md

mstack-upgrade

Skill17 starsChanged 3 months agoMITView on GitHub

Updates MStack — git pull plus setup for clone installs, or points marketplace installs at /plugin marketplace update. User-invoked only.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Git clone: run bash "${CLAUDE_PLUGIN_ROOT}/bin/mstack-upgrade", which pulls --ff-only, lists the changed skills and references, and re-runs …

    line 17
  2. Distinctive:

    Upgrading mid-paper unannounced: If a paper folder is in active use, surface the changeset first so the user can opt in.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/mstack:mstack-upgrade

Stage: power · Voice: maintenance

Procedure

  1. Detect the install: does ${CLAUDE_PLUGIN_ROOT}/.git exist?
  2. Git clone: run bash "${CLAUDE_PLUGIN_ROOT}/bin/mstack-upgrade", which pulls --ff-only, lists the changed skills and references, and re-runs setup for permissions and PATH. Summarize previous version → new version and what changed.
  3. Marketplace install (no .git; the plugin cache is a managed copy, not a repo): do not git pull; it cannot work there.
  4. Either way, the files on disk are not the loaded skills. Tell the user to run /plugin marketplace update mstack and then restart Claude Code, which is what reloads them. A pull alone changes nothing in the running session.

Outputs

  • Summary: install mode, previous → new version (from .claude-plugin/plugin.json), the changed skills and references, and the reload-and-restart step.

Anti-patterns

  • Upgrading mid-paper unannounced. If a paper folder is in active use, surface the changeset first so the user can opt in.
  • git pull in the plugin cache. A marketplace install is not a checkout; only /plugin marketplace update works there.
  • Reporting an upgrade as done after a pull. Until the plugin is updated and Claude Code restarted, the session is still running the old skills.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free