* test(install): reproduce loss of pulled tracked records Exercise the two-machine push and pull sequence and reconciliation states so missing tracked clones cannot silently erase shared install intent. * fix(reconcile): preserve tracked records missing local clones Pull transfers tracked repository metadata but not ignored clones. Keep the missing records during global reconciliation so another install and push cannot erase shared intent or accepted audit findings on every machine. * test(reconcile): isolate tracked record fixtures Use the shared sandbox fixture for both reconciliation tests so their home and configuration paths remain isolated from the invoking environment. * fix(reconcile): retain all sourced tracked declarations Legacy tracked members and unfollowed source links can hide declarations from the local walk. Preserve sourced tracked records regardless of their path so unrelated installs cannot erase them or their audit acceptances. Document restoring a missing checkout before uninstalling it and cover migration, link collisions, aliases, and explicit removal. * test(reconcile): drop fixtures existing tests already pin The tracked-record unit test also seeded a missing plain record and a live plain record. TestReconcileGlobalSkills_PrunesStaleEntries already pins both outcomes: a sourced plain record whose folder is gone is pruned, and one on disk survives. The tracked record with no source still catches a fix that keeps everything or skips the prune. The two-machine test passed HOME and SKILLSHARE_CONFIG to RunCLIEnv, which already sets both from the sandbox for each child process. Separate homes, XDG paths, client overrides and git config remain. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(reconcile): retain tracked entry for unavailable link Expect sourced tracked declarations to survive reconciliation with either source-link policy, so the test matches the cross-machine retention contract. * fix(config): prune legacy tracked members Retain only sourced tracked repository declarations during reconciliation. Migrated member records are not restorable as repositories and retaining them would leave permanent misleading install requests and audit acceptances. * fix(reconcile): preserve tracked intent across followed links A source link can exist before a tracked repository declaration is pulled. Preserve that declaration when the linked folder is not a checkout so later reconciliation does not discard its record and audit acceptances. * test(reconcile): cover grouped followed declarations A followed group can contain the path of a pulled legacy repository declaration, which must retain its tracked intent while its key migrates. * fix(test): scope collision fixture runner correctly Keep the isolated CLI runner in the collision subtest that uses it so the integration test package can compile. * docs(manifest): clarify tracked checkout recovery A retained declaration cannot restore a checkout while another folder or source link occupies its destination, and restoration requires a reachable source. State those prerequisites in each manifest translation. * fix(config): prune members under recorded repositories A migrated underscore-named member can otherwise survive a missing checkout as a repository declaration. Check recorded ancestor paths while preserving ambiguous grouped declarations and unrelated aliases. * docs(manifest): restore fresh-clone project guidance Explain that project declarations without local install records remain available so teammates can install them after cloning. * refactor(reconcile): drop the tracked-intent walker policy Restore baseline normalization for present paths while retaining absent repository declarations through the shared metadata predicate. Isolate the reconcile fixtures without building a CLI and share native-client overrides without changing the original two-machine record and audit regression. Validation: gofmt, git diff --check and context-router check only. Runtime, builds and tests were not executed under the source-only gate. * fix: forget linked checkout records and declarations without checkouts Extend the metadata and uninstall owners to remove a declaration without reading or moving its occupant, contacting its source, or changing trash and gitignore. A failed metadata save makes every metadata-only result fail. Clean up global unlink records in CLI and API, preserve existing-path name precedence, report record-only results truthfully, and list declarations in the dashboard API with noCheckout. Keep project removal behavior unchanged. Remove the obsolete grouped-link walker-policy assertion while preserving grouped absent declarations and the original record/audit A/B regression. Validation: source-only five-pass review, gofmt, git diff --check and the context-router check. No runtime, builds, tests or frontend tooling ran. Stop at commit 15 for the mandatory Luna checkpoint before UI and docs work. * fix(server): reload metadata before removing declarations Preserve CLI records and audit acceptances written while the dashboard is open. Resolve new declarations from disk and refuse stale-cache saves after a reload failure, retaining unlink success when its link already moved. * feat(dashboard): remove a tracked repository record without a checkout Show declaration-only rows without checkout actions or status promises. Reuse Uninstall with record-specific confirmation and feedback, keep real-checkout force handling, and refresh the missing-entry list after repository removal or unlink. * docs: explain kept declarations and how to remove them Document direct global declaration removal and optional restore in English and all four translations, including occupied paths and normalization after reconcile. Keep built-in guidance accurate and use the existing API removal result for dashboard success feedback after concurrent CLI changes. * fix(dashboard): confirm restored checkouts after forceable refusals A tracked declaration can be restored through the CLI while its dashboard row still says there is no checkout. Treat a forceable uninstall refusal as evidence of the current checkout and promote the existing confirmation to its dirty or unreadable-status warning before allowing explicit force. Author stale-row regressions for both forceable codes before the source repair, and retain nonforceable failure and actual-result success feedback. Validation: five serial source review passes, git diff --check, and the context-router check. Tests, builds, runtime and frontend tooling were not run under the source-only gate. * test(server): persist overview declarations before routed request The overview fixture added declarations only to the in-memory skills store, which the real request's config reload replaced with on-disk metadata. The hosted unit, offline, and Nix jobs consequently returned no tracked rows. Save the complete fixture through MetadataStore before serving the request and fail setup on a save error. Keep the middleware, assertions, and production behavior unchanged. * fix(server): prefer exact declarations before checkout shorthand Removing a missing _team declaration from the dashboard could resolve the different org/_team checkout by basename and trash it instead. Reload metadata before declaration lookup, give exact declarations priority, and preserve checkout resolution before non-exact declaration fallback. Add routed absent/occupied regressions and checkout precedence guards, and persist existing checkout fixtures so the metadata reload keeps their state. Validation: gofmt, git diff --check, and context-router check passed. Tests were authored but not run under the source-only fleet restriction. * fix: preserve removal intent and report partial failures Bind dashboard record-only removal to its canonical declaration and refuse restored checkouts before checkout resolution or force. Refresh the row and require another confirmation before moving a restored checkout to trash. Keep unresolved uninstall inputs and their reasons in JSON failed results, including all-invalid requests, partial successes and dry runs. Report unlink metadata cleanup failures as partial results, refresh completed unlinks and show localized warnings. Keep CLI and dashboard guidance aligned. Regression tests were authored before source changes and remain unrun under the source-only task restriction. Static formatting, diff and router checks passed; no build, product runtime, frontend tooling or test suite was run. * fix(unlink): log partial metadata cleanup failures Write the unlink result after global metadata cleanup so load and save failures retain their diagnostic and report partial success. Preserve the successful link removal, warning, target and exit policy, and the existing link, project unlink and native removal failure behavior. Add the corrupt-metadata regression before the fix; leave it unrun under the source-only authorization. Formatting, diff and context-router checks pass; runtime verification remains with the coordinator. * fix(unlink): forget records below the removed link name Reconcile can normalize a followed link's record to untracked, and linked collections can retain nested repository declarations. Clean the removed namespace through the existing metadata path owner in both unlink callers, including audit acceptances, while keeping declaration uninstall strict. Author CLI and route regressions before the source fix for normalized and nested records, sibling preservation, and subsequent bare install. Tests remain unrun under the source-only task restriction; static checks only. * fix(uninstall): refuse a restored checkout at execution A declaration selected while absent can become a checkout before removal runs. Recheck the resolved source-relative name in the shared metadata-only execution owner and refuse before touching metadata, regardless of force. Reuse the existing dashboard conflict response and refresh/reselection flow for this refusal, preserving the earlier record-only intent guard. CLI results already carry shared execution failures through text and JSON. Author restoration, force, absent/occupied control and client boundary regressions before production edits. Correct the unlink fixture name and response-key assertion found in serial static review. All tests remain unrun under the source-only restriction; formatting/diff/router checks pass. * refactor(server): consolidate repository uninstall result handling Resolve a declaration or checkout to one item and canonical name before using the existing uninstall, conflict, log and success response tail. Keep metadata-only removal unforced, preserve its error and cache recovery behavior, and report movedToTrash from the selected item. Preserve exact declaration precedence, record-only checkout refusals, ordinary checkout errors and project behavior without changing tests. Five serial source review passes, gofmt, diff checks and the context-router check completed. Tests and builds remain unrun under the source-only brief. * fix(unlink): preserve independent records and trash undo metadata Limit unlink's legacy group matching to members so a retained declaration such as team/_repo survives unlinking _team. Share snapshot and removal matching while keeping generic uninstall's legacy contract unchanged. Save the exact removed records, audit acceptances and target overrides through uninstall's existing trash sidecar owner before pruning metadata. Keep metadata on sidecar failure and preserve completed-unlink warnings, fresh reloads, cache refresh and project-mode behavior. Author owner, CLI and API regressions for namespace collisions, undo, partial failures and project/empty controls. Source-only verification: gofmt, diff check and context-router check passed; runtime tests, builds, frontend checks and final make check remain unrun for root-owned gates. * fix(install): preserve independent tracked declarations Limit declaration-only cleanup to the precise namespace and legacy members already used by unlink. Keep independently installed prefixed repositories, their audit acceptances, and overrides when forgetting a missing checkout. * fix(cli): explain missing tracked repository recovery by mode Offer global record removal when restoring an unreachable source is unwanted. Keep project recovery scoped to install -p, share the hint with doctor, and align update documentation in every existing locale. * refactor(uninstall): share declaration and unlink operations Keep declaration resolution and unlink metadata ordering in shared owners so CLI and API preserve the same scope and recovery behavior. Consolidate domain regressions while retaining caller translation coverage. Distinguish record-only removals in API and CLI operation logs and CLI JSON, including mixed batches and dry runs. Document outcome fields, warning semantics, and current API error codes across existing locales. --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Willie <egg358358@gmail.com>
14 KiB
sidebar_position
| sidebar_position |
|---|
| 3 |
uninstall
Remove one or more skills or tracked repositories from the source directory. Skills are moved to trash and kept for 7 days before automatic cleanup.
A global tracked declaration without a checkout can instead be removed as metadata only; see Tracked Repositories.
skillshare uninstall my-skill # Remove a single skill
skillshare uninstall a b c --force # Remove multiple skills at once
skillshare uninstall --all # Remove all skills
skillshare uninstall --group frontend # Remove all skills in a group
skillshare uninstall team-repo # Remove tracked repository (_ prefix optional)
When to Use
- Remove skills you no longer need (they move to trash for 7 days)
- Clean up a tracked repository you've stopped using
- Batch-remove an entire group of skills at once
- Remove all skills at once with
--all
$ skillshare uninstall css-review
frontend/css-review ~/.config/skillshare/skills/frontend/css-review · 1 file
✓ Uninstall frontend/css-review → trash, kept 7 days
Next
skillshare sync remove it from claude, cursor
skillshare trash restore frontend/css-review undo
What Happens
flowchart TD
TITLE["skillshare uninstall"]
S1["1. Resolve targets"]
S2["2. Pre-flight checks"]
S3["3. Confirm and move to trash"]
TITLE --> S1 --> S2 --> S3
Options
| Flag | Description |
|---|---|
--all |
Remove all skills from source (requires confirmation) |
--group, -G <name> |
Remove all skills in a group (prefix match, repeatable) |
--force, -f |
Skip confirmation and ignore uncommitted changes |
--dry-run, -n |
Preview without making changes |
--project, -p |
Use project-level config in current directory |
--global, -g |
Use global config (~/.config/skillshare) |
--json |
Output JSON and skip confirmation; dirty tracked repositories still require --force |
--help, -h |
Show help |
JSON Output
skillshare uninstall my-skill another-skill --json
{
"removed": ["my-skill", "another-skill"],
"failed": [],
"skipped": 0,
"dry_run": false,
"duration": "0.089s"
}
In global mode, the optional record_only array is the subset of removed names whose declarations were removed without a checkout. These names have no trash entry or trash undo; other successfully removed names move to trash. With dry_run: true, both arrays describe planned actions, and nothing has been removed. record_only is omitted when the subset is empty, including agent and project removals. CLI uninstall log entries also use the optional record_only subset; JSON previews add dry_run: true to the log.
Combine with --dry-run to preview:
skillshare uninstall --all --json --dry-run
Unresolved inputs are included in failed with their reasons, including dry runs and requests where no input resolves.
When every skill fails to uninstall, the command exits non-zero and the error field names each skill with its reason; when only some fail, they are listed in failed with their reasons and the command exits 0. uninstall agents --json exits non-zero when any agent fails, lists the failed names in failed, and gives each reason in error. JSON output works in project mode (-p) too.
Multiple Skills
Remove several skills in one command:
skillshare uninstall alpha beta gamma --force
When some skills are not found, the command skips them with a warning and continues removing the rest. It only fails if all specified skills are invalid.
Glob Patterns
Skill names support glob patterns (*, ?, [...]) for batch removal:
skillshare uninstall "core-*" # Remove all skills matching core-*
skillshare uninstall "test-?" --force # Single-character wildcard
skillshare uninstall "core-*" "util-*" # Multiple patterns
Glob matching is case-insensitive: "Core-*" matches core-auth, CORE-DB, etc.
:::note Top-level matching only
Glob patterns match against top-level directory names in the source folder. Nested skills (e.g. frontend/react-hooks) are not matched by "react-*" — use --group frontend to target skills within a subdirectory.
:::
--group refuses a followed source link such as _dev-skills, because it would move every skill out of the real checkout. Use skillshare unlink _dev-skills to remove the link entry, or name the skills (skillshare uninstall _dev-skills/foo) to trash them from the checkout.
If the linked folder itself contains SKILL.md, uninstall refuses that root skill: moving it would remove the link and hide all nested skills. Use unlink to remove only the link; the checkout stays untouched.
Remove All
Use --all to remove every skill from the source directory at once:
skillshare uninstall --all # Interactive confirmation
skillshare uninstall --all --force # Skip confirmation
skillshare uninstall --all -n # Preview what would be removed
--all cannot be combined with skill names or --group.
:::tip Shell glob protection
Running skillshare uninstall * without quotes causes your shell to expand * into file names in the current directory. skillshare detects this and suggests using --all instead. Always quote the wildcard ("*") or use --all.
:::
Group Removal
When you uninstall a directory that contains sub-skills, skillshare automatically detects it as a group and lists the contained skills before asking for confirmation:
Uninstalling group (5 skills)
─────────────────────────────────────────
- feature-radar
- feature-radar-archive
- feature-radar-learn
- feature-radar-ref
- feature-radar-scan
→ Name: feature-radar
→ Path: ~/.config/skillshare/skills/feature-radar
? Uninstall group feature-radar? moved to trash for 7 days Yes No
The --group flag removes all skills under a directory using prefix matching:
# Remove all skills under frontend/
skillshare uninstall --group frontend
# Also removes nested skills: frontend/react/hooks, frontend/vue/composables
skillshare uninstall --group frontend --force
# Preview what would be removed
skillshare uninstall --group frontend --dry-run
When group removal is applied (including auto-detected directory groups), each removed member is also removed from the managed skills: list in config (~/.config/skillshare/config.yaml or .skillshare/config.yaml in project mode).
You can combine positional names with --group, and even use -G multiple times:
# Mix names and groups
skillshare uninstall standalone-skill -G frontend -G backend --force
# Duplicates are automatically deduplicated
skillshare uninstall frontend/hooks -G frontend --force # hooks removed once
Tracked Repositories
For existing checkouts (including links to Git checkouts):
- Checks for uncommitted changes (use
--forceto override) - Fails with
failed to check git statuswhen skillshare cannot read the repo's git status; other items in the batch are still removed, and--forceskips the check - Automatically removes the entry from
.gitignore - The
_prefix is optional when uninstalling - A repo installed with
--intois named by its path, such asdevops/_team-skills - For
--intorepos, the final_is optional too:devops/team-skillsresolves todevops/_team-skills. An existing skill or folder at the typed path takes precedence; use the explicit_path to remove the repo. Ambiguous short names fail and require the full path. - A skill or folder inside a tracked repo cannot be removed on its own, even with
--force; the command fails withinside a tracked repo; uninstall the repo instead. Skills below a followed source link can still be removed one at a time
skillshare uninstall _team-skills # With prefix
skillshare uninstall team-skills # Without prefix (auto-detected)
skillshare uninstall _team-skills --force # Force remove with uncommitted changes
skillshare uninstall devops/_team-skills # Repo installed with --into devops
skillshare uninstall devops/team-skills # Same repo, unless this path already exists
- In global mode, an explicitly named tracked declaration with no checkout here (absent, a plain folder, or a link to a non-checkout) can be removed without contacting its source, even if the source is unreachable. Only its record and audit acceptances are removed: the occupant and
.gitignorestay untouched, no Git check runs, and nothing goes to trash.trash restorecannot undo this removal. Use the canonical_name or full recorded path, such asskillshare uninstall devops/_team-skills -g; shorthand can select an existing skill or folder. Globs,--all, and--groupdo not select declarations without checkouts.
Deleting a checkout by hand leaves its global declaration. To restore missing checkouts instead of dropping their declarations, run skillshare install -g with reachable sources and free destinations. If a later install or reconcile walks a plain folder or followed link to a non-checkout at a declared path, it normalizes the entry to an ordinary record (Tracked=false); ordinary uninstall then moves the occupant to trash. Absent paths and unfollowed or unavailable links are not normalized this way.
Examples
# Remove a single skill
skillshare uninstall my-skill
# Remove multiple skills
skillshare uninstall skill-a skill-b skill-c --force
# Remove all skills
skillshare uninstall --all
skillshare uninstall --all --force
skillshare uninstall --all -n # Preview
# Remove by group
skillshare uninstall --group frontend --force
# Preview removal
skillshare uninstall my-skill --dry-run
skillshare uninstall --group frontend -n
# Remove tracked repository
skillshare uninstall team-repo
# Mix names and groups
skillshare uninstall my-skill -G frontend --force
Safety
Uninstalled skills are moved to trash, not permanently deleted:
- Location:
~/.local/share/skillshare/trash/(global) or.skillshare/trash/(project) - Retention: 7 days, then automatically cleaned up
- Reinstall hint: If the skill was installed from a remote source, the reinstall command is shown
- Restore: Use
skillshare trash restore <name>to recover from trash
Single skill (verbose):
my-skill ~/.config/skillshare/skills/my-skill · 2 files
✓ Uninstall my-skill → trash, kept 7 days
Next
skillshare sync remove it from claude, cursor
skillshare trash restore my-skill undo
skillshare install github.com/user/repo/my-skill reinstall it later
Multiple skills (batch):
Failed
✗ bad-skill failed to move to trash: ...
Removed
✓ pdf skill
✓ tdd skill
✓ security group, 2 skills
! Uninstalled 3, 1 failed · 0.1s
Next
skillshare sync remove them from claude, cursor
skillshare trash list restore any of them within 7 days
Large batches use a condensed format:
Failed
✗ bad-a failed to move to trash: permission denied
✗ bad-b failed to move to trash: permission denied
Removed
✓ 920 uninstalled
! Uninstalled 920, 2 failed · 1.2s
Next
skillshare sync remove them from claude, cursor
skillshare trash list restore any of them within 7 days
To restore an accidentally uninstalled skill:
skillshare trash list # See what's in trash
skillshare trash restore my-skill # Restore to source
skillshare sync # Sync back to targets
After Uninstalling
Run skillshare sync to remove the skill from all targets:
skillshare uninstall old-skill
skillshare sync # Remove from Claude, Pi, etc.
Project Mode
Uninstall skills or tracked repos from the project's .skillshare/skills/:
skillshare uninstall my-skill -p # Remove a skill
skillshare uninstall a b c -p -f # Remove multiple skills
skillshare uninstall --all -p -f # Remove all project skills
skillshare uninstall --group frontend -p -f # Remove a group
skillshare uninstall team-skills -p # Tracked repo (_ prefix optional)
In project mode, uninstall:
- Moves the skill directory to
.skillshare/trash/(kept 7 days) - Removes the skill's entry from
.skillshare/config.yamlskills:list (for remote skills) - Removes the entry from
.skillshare/.gitignore(for remote/tracked skills) - Removes the skill's pin from
.skillshare/skills.lock.json(for a group, every pin under it) - For tracked repos: checks for uncommitted changes, and fails when the git status cannot be read (use
--forceto override both) - The
_prefix is optional — auto-detected - Repos installed with
--intowork as in global mode:devops/team-skills -presolves todevops/_team-skills, and a skill or folder inside a tracked repo cannot be removed on its own
skillshare uninstall pdf -p
skillshare sync
git add .skillshare/ && git commit -m "Remove pdf skill"
Agent Support
Use --kind agent to uninstall agents instead of skills:
skillshare uninstall --kind agent tutor # Remove an agent
skillshare uninstall --kind agent tutor reviewer -f # Remove multiple agents
skillshare uninstall --kind agent --all # Remove all agents
Agent uninstall follows the same trash-and-retain behavior as skills (moved to trash, kept 7 days). See Agents for background.
See Also
- install — Install skills
- list — List installed skills
- trash — Manage trashed skills
- Project Skills — Project mode concepts
- Agents — Agent concepts