skillshare v0.23.5 Release Notes

TL;DR

1. An include pattern that matches no skill is reported. Sync now says which target's include selects nothing and suggests the name that would work.

Include patterns that match no skill

Target include / exclude patterns match the source path name, with folders joined by __. With target_naming: standard, the target shows the bare SKILL.md name instead, so a skill at frontend/dev appears in the target as dev. A pattern written with that name selected nothing:

targets:
  claude:
    include: [dev]            # matches nothing

Sync then removed what a working pattern had linked, and only repeated the patterns back. It now warns about each include pattern that matches no skill, names the target, and suggests the source path name when one fits:

✓ claude: merged (0 linked, 0 local, 0 updated, 1 pruned)
→   include: dev
!   claude: include pattern "dev" matches no skill in the source (filters use the source path name; did you mean "frontend__dev"?)

The warning appears in skillshare sync and in the dashboard's sync results. --json output is unchanged, and filtering itself works as before. To keep the skill, use the suggested name:

targets:
  claude:
    include: [frontend__dev]

Contributors

@star-nebula