skillshare v0.25.4 Release Notes
TL;DR
- Same-named skills from different tracked repos can both reach a tool. Copy-mode targets accept
target_naming: prefixed, which names a tracked skill<repo>-<name>. - Targets that share a skills folder and undo each other are reported, now also when their mode or naming differs, and the dashboard shows the clash where you change it.
- A skills source folder named
.skillshareor.claudeis read again. Since 0.24.4 it was skipped as a whole, solistwas empty andsyncremoved links. - Moving an installed skill to another folder keeps its source, and
install <path> --tracktakes a local git repository.
Prefixed target naming
Under standard naming, two tracked repos that each ship a prototype skill collide, and one of them is skipped. With prefixed, each skill inside a tracked repo is named <repo>-<name>, in the copied folder and in the copy's name:, so both reach the tool. A name that already starts with the repo name is not prefixed again (_bmad/skills/bmad-ux stays bmad-ux). Local skills keep their standard name, and the source is never changed.
skillshare target claude --mode copy --target-naming prefixed
skillshare sync- It works in copy mode only. A target that resolves to
prefixedoutside copy mode fails validation;status,doctorandtarget listflag it before you sync, andtarget addgives a new target copy mode when it would inheritprefixed. - Switching between
flat,standardandprefixedrenames managed entries in place and copies them again so theirname:matches. If a local skill already holds the new name, the skill stays under its old entry anddiffsays so. - The dashboard, the TUI naming picker and the JSON schemas offer
prefixed; the dashboard disables it outside copy mode and says why.
Shared skills folders
Two targets that write the same skills folder with a different mode or naming undo each other on every sync. Only include and exclude were compared before, so this got the generic shared-folder hint. sync and doctor now warn that the settings differ, and the dashboard's target page warns under the control whose change causes it and offers the other target's value. The Sync page's notice lists which settings differ.
Sources
- A skills source folder named like a tool folder is read again. Since 0.24.4, a
sources.skillsfolder whose own name is a target folder name, such as.skillshareor.claude, was skipped as a whole:listshowed no skills andsyncremoved links it had made before. Folders with those names inside the source are still skipped. (#511) - An agents source in a hidden folder is read. A
sources.agentsfolder such as~/.agentsfound no agents.
Install and collect
- Moving an installed skill keeps its source. After an installed skill was moved with
mv, for example into a group folder, the dashboard's Install missing and a bareskillshare installinstalled it again at its old path, leaving two copies that both synced. They now recognize the moved copy (same name, files unchanged since install, only one such copy) and move its install record to the new folder. (#510) install <path> --trackaccepts a local git repository, including a bare one, and clones it likefile:///path.skillshare install ~/code/team-skills --trackinstall --track --forcekeeps the existing repo until the new clone is in place, so a failed clone no longer loses it.collectpicks up only skills. Folders without aSKILL.mdare left out.
Smaller changes
- Switching a target from copy back to merge replaces its copies with links, except copies you edited and folders you made yourself, which are kept until
sync --force. - A
SKILL.mdthat starts with a UTF-8 BOM is read, so files saved by Notepad keep their name and are no longer flagged byauditas hidden Unicode. target <name> --mode copy --target-naming standardapplies both flags; only--modewas saved before.- Skills skipped by naming checks are listed with their reason, and the duplicate-name line no longer prints on every sync.
- AGENTS.md targets update immediately in the dashboard after a target or
config.yamlchange. - Tighter Skills toolbar and a pinned Hub header in the dashboard.