v0.20.25

Release Highlights

skillshare v0.20.25 Release Notes

TL;DR

1. Batch updates keep dot-directory skills healthy — skills installed from paths such as .claude/skills/... are no longer mistaken for upstream deletions.
2. Explicit dot-directory installs work — pointing install directly at .claude, .codex, or another target directory now discovers its skills and agents.
3. Project commands protect existing content — a missing project config no longer causes silent re-initialization when skills or agents are already present.
4. Windows can uninstall nested skills again — folder-based skill names no longer fail trash validation because of Windows path separators.

Reliable updates for dot-directory skills

Batch updates previously skipped skills whose repository path lived under a target directory such as .claude/skills or .codex/skills. Those skills could be reported as deleted upstream even though they were still present, incorrectly steering users toward --prune. Batch update now checks the requested skill path before declaring it missing.

skillshare update --all

Explicit target-directory installs

Repository-wide discovery still avoids target directories so synced copies are not treated as source skills. When you explicitly install from one of those directories, however, Skillshare now scans the requested location for both skills and agents instead of returning no results.

skillshare install user/repo/.claude

Safer recovery when project config is missing

If a project already contains skills or agents but its .skillshare/config.yaml is missing, project-mode commands now stop and explain how to recover. They no longer silently create an empty config that drops target settings and leaves stale links behind. Fresh projects and shared repositories that intentionally ignore the config continue to initialize automatically.

Restore the config from version control when possible, or explicitly create a new one:

skillshare init -p

Windows nested-skill uninstall

On Windows, uninstalling a nested skill could fail with trash name must not contain backslash because the resolved folder path used Windows separators. Nested names are now normalized before the skill is moved to trash, in both global and project mode, while path-traversal protection remains intact.

skillshare uninstall _skill

Contributors

@masonc15,@salmonumbrella