skillshare v0.19.18 Release Notes

Release date: 2026-05-22

TL;DR

1. Tracked repos with a root-level SKILL.md now work end-to-end — install reports the correct skill count, metadata persists, and the repo appears in status / list output
2. GitLab SSH URLs with nested subgroups produce a clean tracked-repo name — git@gitlab.example.com:org/subgroup/my-skills.git --track now installs as _my-skills, matching the HTTPS subgroup behavior

This is a patch release — bug fixes only, no new commands or flags.

Single-Skill Tracked Repos (root-level SKILL.md)

Some tracked repos ship as a single skill — the SKILL.md lives at the repository root rather than inside a nested folder. Prior to v0.19.18, installing such a repo with --track was technically allowed but left a trail of inconsistent output:

• Found 0 skill(s) even though sync would later pick the skill up.
• .metadata.json gained no tracked entry, breaking cross-machine recovery (skillshare install -p on a teammate's machine wouldn't restore the repo).
• The repo was missing from skillshare status and skillshare list, both text and --json output.
• A Run skillshare sync to distribute skills next-step hint printed even when no skill was discovered.

v0.19.18 fixes all four. After install:

$ skillshare install github.com/team/my-skill --track
✓ Cloned to _my-skill
Found 1 skill(s)

Next Steps
  Run 'skillshare sync' to distribute skills to all targets
  Run 'skillshare update _my-skill' to update this repo later

$ skillshare status --json | jq '.tracked_repos'
[
  { "name": "_my-skill", "skill_count": 1, "dirty": false }
]

The same fix applies in project mode (-p). If you previously installed a single-skill tracked repo and noticed it missing from status output, re-running skillshare install is not required — the metadata is reconciled on the next mutating command (install / update / uninstall). Refs: #163

GitLab SSH Subgroup Name Resolution

GitLab SSH URLs with nested subgroups now resolve to a clean repository name:

skillshare install git@gitlab.example.com:org/subgroup/my-skills.git --track
# Installs as _my-skills/ (previously: a directory name containing the subgroup path)

The behavior now matches HTTPS subgroup installs (https://gitlab.example.com/org/subgroup/my-skills.git), which already extracted the trailing segment correctly. No config change is required — any GitLab host (the built-in gitlab.com / jihulab.com detection plus anything you've added under gitlab_hosts:) benefits from the fix.

Changelog

• 9163d3b chore: release v0.19.18
• a61a0e3 fix(install): include root SKILL.md in tracked repo discovery
• 1307873 fix(install): normalize SSH subgroup repo names
• 210605e fix(install): persist metadata for tracked repos with root-level SKILL.md