skillshare v0.21.14 Release Notes

TL;DR

1. Sync any single file, renamed per target. extras init --file syncs one file instead of a whole folder, and --as gives it another name at the target, such as Pi's APPEND_SYSTEM.md.
2. Pin a skill to a tag or commit from its URL. A GitHub, GitLab or Bitbucket URL that names a branch, tag or commit installs that version, and update keeps it.
3. Pin hub entries. A hub entry whose source names a ref installs that revision for everyone.
4. One Hubs page. Browsing a hub and building your own are the same page, and entries can come from any repository URL.
5. Backups grouped by day, with a per-folder restore and a faster Backup page.

Sync any single file

Single-file extras worked before, but only the dashboard's AGENTS.md tab could create one, so they looked like an AGENTS.md feature. Any file can now be an extra from the CLI:

skillshare extras init pi-prompt --source ~/dotfiles/prompts --file system.md \
  --target ~/.pi/agent --as APPEND_SYSTEM.md
skillshare sync extras

--as names the file at every target; --add-target <path> --as <name> gives one target its own name. init only writes the config: it does not create the source file or sync, and says so when the file is missing. The extras init wizard asks whether to sync a folder or a single file, and extras list shows the full source and target file paths.

To pick several files from one folder, create one extra per file with the same --source. Each syncs only its own file. This works in global mode; in a project each extra has its own source folder.

On the dashboard, the first Extras tab is now Folders & files and lists every extra except shared AGENTS.md files. Add extra can create a single file, with a file name per target and merge, copy or import mode.

Thanks to the reporter of #300.

Pin a skill to a tag or commit from its URL

The branch, tag or commit after tree/ or blob/ in a GitHub URL (-/tree/ on GitLab, src/ on Bitbucket) is now the version that gets installed:

skillshare install github.com/team/skills/tree/v1.2.0/skills/foo

skillshare update keeps the pin, and --branch still overrides the URL. Branch names with / are matched against the remote's branches and tags, and tree/HEAD/ links use the default branch. A ref the remote no longer has, such as tree/master/ after a rename to main, now fails the install instead of quietly installing the default branch.

Skills installed earlier from a tree/<ref>/ URL got the default branch, and update and installs from config keep them there.

Thanks to @harisonw for #293.

Pin hub entries

A hub index entry whose source names a ref installs that revision for everyone, from skillshare search --hub and the dashboard:

{ "name": "reviewer", "source": "github.com/owner/repo/tree/v1.2.0/skills/reviewer" }

Move the pin by editing the ref in the index. Pinned skills from the same repository and ref still share one clone.

One Hubs page

Browsing a hub and building your own are now one page. Your hub is shown the way others will see it and edited in place. Entries can be added from any repository URL, with a branch or tag picked from the remote, and skills added from installed ones keep the version they were installed from.

Previewing a draft from the old builder opened an empty "pick a hub" page; that is gone with the merge.

Backups

Settings → Backup groups folder backups by day, one compact row per backup. Opening a row lists each folder with its file count, size and its own Restore button. The page opens faster, and says what it is doing while backups load and while Back up now runs.

Smaller changes

• llms.txt: the docs site serves llms.txt and llms-full.txt for AI assistants, linked from the footer.
• Counts of one read "1 skill", not "1 skills", in every language.
• After skillshare upgrade, the dashboard no longer looks stuck while it re-downloads UI files it had just fetched.
• Project mode: the note that said Settings → Backup is hidden is gone; the tab is there, scoped to the project.