Keep skills updated - MasterSkills

Through your agent

You: any skill updates? Agent: Three changes: ↑ @acme/api-conventions v3 → v4 ＋ @acme/security-guidelines v2 — org-required, not installed − @acme/legacy-deploy v1 — removed by the org, delete it locally? Apply all?

One check surfaces all three kinds of drift:

Change	Meaning
Updates	A newer version of something you have installed
New required	A skill an admin marked required for the org that this machine is missing
Removed	A skill the org archived that is still installed locally

Nothing is applied until you say so — even the required skill waits for your yes.

From the CLI

masterskills update --check          # show what would change, apply nothing
masterskills update --check --json   # machine-readable — what agents use
masterskills update                  # apply updates
masterskills update @acme/api-conventions   # update specific skills only

Updates rewrite the skill in the central store, which refreshes every agent’s link at once. Downloads are hash-verified before anything is written, like installs.

Sync

masterskills update --check also reports this machine’s installed skills to the registry — that’s what keeps the panel’s install counts and the device’s last-seen time accurate. You can run the report alone:

masterskills sync

There is no background daemon. Checks happen when you (or your agent) run them — a natural fit for “any skill updates?” as an occasional habit.

⌘I