* feat(update): flag and protect skills edited since install A skill installed from a repository and then edited by hand looked exactly like an untouched one: check said up to date, and update either reported it current or silently reinstalled it over the edit (#621). Install already records each file's hash, so check now compares a remote skill's files with those hashes and reports "modified", and update skips such a skill until --force (CLI single, --all/--group, dashboard). --force, the dashboard's Force Retry on the skipped row, or the confirmation on the skill page discards the edit and reinstalls. Two hash paths had to be made reliable for this to be trusted: the dashboard's folder-wide target edit refreshed hashes by basename, so a nested skill looked edited after skillshare's own change, and a skill whose files cannot be hashed now counts as modified instead of being overwritten. * fix(server): keep earlier local edits when a target change rewrites SKILL.md Changing a skill's targets in the dashboard rewrites its SKILL.md, and both the folder-wide and the single-skill handler then re-hashed the whole directory as the new baseline. An edit the user had already made to any file in the skill was absorbed into that baseline, so the skill stopped counting as modified and the next update overwrote the edit without --force. Both handlers now move only SKILL.md's recorded hash, and only when the file still matched it before the rewrite. skillshare's own target edit no longer reads as a local change, and an earlier edit still does. The whole-directory refresh helpers lost their last callers and are removed.
8.2 KiB
sidebar_position
| sidebar_position |
|---|
| 3 |
check
Check for available updates to tracked repositories and installed skills without applying changes.
skillshare check # Check all repos and skills
skillshare check my-skill # Check a single skill
skillshare check a b c # Check multiple skills
skillshare check --group frontend # Check all skills in frontend/
skillshare check x -G backend # Mix names and groups
skillshare check --json # Machine-readable output
When to Use
Before Updating
Preview what would change before running update:
skillshare check # See what has updates
skillshare update --all # Apply updates
skillshare sync # Distribute changes
CI/CD Pipeline
Check for stale skills in CI:
result=$(skillshare check --json)
# Parse JSON to detect outdated skills
What It Does
check inspects your source directory and reports update status for:
- Tracked repositories — Fetches from origin, shows how many commits you're behind
- Installed skills (with metadata) — Compares installed version against the remote HEAD
- Stale skills — Detects skills whose subdirectory was deleted from the upstream repository
- Locally modified skills — Compares the files of a skill installed from a repository with the files recorded at install time, and reports
"status": "modified"when you edited, added, or deleted any of them - Local-path installs — Compares the files at the path you installed from with the files recorded at install time (see Local-Path Installs)
- Local skills — Marks skills without install metadata as "local source" (nothing to compare)
- Skill-level
targetsvalidation — Warns about unknown target names in SKILL.mdtargetsfrontmatter fields
Unlike update, check never modifies any files.
Local-Path Installs
A skill installed from a directory on disk (skillshare install /path/to/skill) records that path and the hash of every file it copied. check re-hashes the files at that path and reports:
- up to date — the files match what was installed
- update available — a file was changed, added, or removed at the source path
- error — the source path no longer exists (
local source not found: <path>)
This is useful for skills that another application ships and updates, such as a skill inside an app bundle:
skillshare install /Applications/Surge.app/Contents/Resources/Skills/surge
# After the app updates:
skillshare check surge # → Update available
skillshare update surge # Re-copies from the path and runs the security audit
skillshare sync
Skills installed before file hashes were recorded keep the "local source" status until they are updated or reinstalled. In project mode, a relative path (such as ./vendor/my-skill) is resolved against the project root.
When the dashboard installs the root of a directory that also contains child skills, it copies only that root's SKILL.md. check then compares only SKILL.md, and update re-copies only SKILL.md.
Example Output
$ skillshare check
! _shared-rules 3 commits behind
! _design-system uncommitted changes
! commit update available · github.com/anthropics/skills
! old-helper stale — no longer in the upstream repository
! Updates available for 1 repo, 1 skill, 2 up to date, 1 local skipped, 1 stale · 3.4s
Next
skillshare update --all pull the updates
skillshare update --all --prune remove stale skills
Check Specific Skills
You can check one or more skills by name instead of scanning everything:
skillshare check my-skill # Single skill
skillshare check skill-a skill-b # Multiple skills
With follow_source_links: true, you can also check a followed Git checkout by its link name, for example skillshare check _dev-skills.
Use --group / -G to check all updatable skills in a group directory:
skillshare check --group frontend # All skills under frontend/
skillshare check -G frontend -G backend # Multiple groups
skillshare check my-skill -G frontend # Mix names and groups
If a positional name matches a group directory (not a repo or skill itself), it is automatically expanded:
skillshare check frontend # Auto-detected as group
Skills without metadata (local-only) are skipped when expanding groups.
Options
| Flag | Description |
|---|---|
--group, -G <name> |
Check all updatable skills in a group (repeatable) |
--project, -p |
Check project-level skills (.skillshare/) |
--global, -g |
Check global skills (~/.config/skillshare) |
--json |
Output as JSON (for scripting/CI) |
--help, -h |
Show help |
:::tip Auto-detection
If neither --project nor --global is specified, skillshare auto-detects: if .skillshare/config.yaml exists in the current directory, it defaults to project mode; otherwise global mode.
:::
JSON Output
skillshare check --json
{
"tracked_repos": [
{"name": "_team-skills", "status": "up_to_date", "behind": 0, "branch": "main"},
{"name": "_shared-rules", "status": "behind", "behind": 3, "branch": "develop"}
],
"skills": [
{"name": "pdf", "source": "anthropics/skills", "version": "a1b2c3d",
"status": "up_to_date", "installed_at": "2024-06-01T10:00:00Z"},
{"name": "commit", "source": "anthropics/skills", "version": "x9y8z7w",
"status": "update_available", "installed_at": "2024-05-15T08:30:00Z"},
{"name": "old-helper", "source": "anthropics/skills", "version": "d4e5f6g",
"status": "stale", "installed_at": "2024-03-10T09:00:00Z"},
{"name": "my-review", "source": "anthropics/skills", "version": "a1b2c3d",
"status": "modified", "installed_at": "2024-06-01T10:00:00Z",
"message": "local changes since install"},
{"name": "local-skill", "source": "", "version": "",
"status": "local", "installed_at": "2024-04-20T12:00:00Z"}
]
}
Skills with "status": "error" include a message field when the reason is known, for example "message": "local source not found: /path/to/skill".
Status Indicators
| Icon | Meaning |
|---|---|
✓ |
Up to date |
⬇ |
Update available (tracked repo: commits behind; skill: newer version) |
⚠ |
Stale — subdirectory deleted or renamed upstream |
! |
Has uncommitted changes (tracked repo) or local changes since install (skill) |
• |
Local source (no install metadata to compare) |
:::info Stale skills
When a skill's subdirectory was renamed or deleted upstream, check reports it as stale. Use update --prune to clean up stale skills.
:::
:::info Locally modified skills
A skill you edited after installing it is reported as modified, even when upstream has a newer version; its message then ends with update available upstream. update leaves it alone until you run skillshare update <name> --force, which discards your changes and reinstalls it.
:::
:::tip Monorepo awareness
For skills installed from a subdirectory, check only reports "update available" when that specific directory changed — not when unrelated parts of the repo have new commits.
:::
Project Mode
skillshare check -p # Check all project skills
skillshare check -p my-skill # Check specific project skill
skillshare check -p --group frontend # Check project group
skillshare check -p --json # JSON output for project
Agent Support
skillshare check agents scopes the check to agents only, reporting drift and update status for .md files in the agents source directory:
skillshare check agents # Check all agents
skillshare check agents --json # JSON output for agents
skillshare check agents -p # Check project agents
Without the agents argument, check operates on skills only (default behavior). See Agents for background.