skillshare v0.18.6 Release Notes

Release date: 2026-04-01

TL;DR

1. Registry cleanup after uninstall — batch uninstall from the Web UI now correctly removes nested skill entries from registry.yaml
2. Sync prunes stale registry entries — skillshare sync automatically cleans up registry entries for skills that no longer exist on disk
3. UI polish — uninstall page search, path display, and update page cleanup

Registry Cleanup After Uninstall

Batch uninstall from the Web UI was not removing registry.yaml entries for nested/grouped skills (e.g. frontend/vue/vue-best-practices). The API handler was matching against flat names (frontend__vue__vue-best-practices) but the registry stores path names with /. This caused stale entries to accumulate.

The handler now tracks the exact resolved path for each successfully removed skill, so registry entries are accurately cleaned up regardless of nesting depth.

Sync Prunes Stale Registry Entries

skillshare sync (CLI and Web UI) now automatically removes registry.yaml entries for skills that no longer exist in the source directory. This covers scenarios where skills were manually deleted from disk without using uninstall.

rm -rf ~/.config/skillshare/skills/some-old-skill
skillshare sync    # registry.yaml entry for some-old-skill is automatically removed

Skills hidden by .skillignore are preserved — only entries whose source directory is truly gone are pruned.

UI Polish

• Uninstall page search — plain text (e.g. matt) now works as a substring match, finding mattpocock/tdd. Glob patterns (*matt*, frontend/*) still work when * or ? is present
• Uninstall page path display — confirmation dialogs and result summaries show frontend/vue/vue-best-practices instead of frontend__vue__vue-best-practices
• Updates page — removed the redundant "0 repo(s) and 20 skill(s) already up to date" line when everything is already current

Changelog

• a570670 fix: registry cleanup after uninstall and sync, UI polish