[walcz-de]

What

Adds an opt-in exclusion list so that a synced repository can be used while a single skill in it stays hidden.

Patterns use path.Match and are matched against the skill name (skill or repoName/skillName). A * does not cross /, so superpowers/* hides a whole repository and */using-* hides matching skills in any repository.

Excluded skills are skipped by ListSkills, and so by the search index and by any system prompt built from the list. They are also skipped by SearchSkills, ReadSkill and the resource methods. Files on disk are not touched, so git pulls keep working.

Why

Git-synced skills are read-only, and deleting files in the clone breaks the next pull. So there was no way to drop one skill and keep the rest of the repository. Our case: a meta-skill that tells the model to invoke a skill before every answer distracted smaller local models in an agent with all skills enabled.

Configuration

• library: NewFileSystemManager(dir, repos, WithExcludedSkills(...)). Without the option it reads SKILLSERVER_EXCLUDE_SKILLS, so embedders pick up the variable without code changes.
• CLI: --exclude-skills flag or the SKILLSERVER_EXCLUDE_SKILLS env var (comma-separated).
• Invalid patterns are rejected at construction. NewFileSystemManager stays source-compatible (variadic options).

README documents the flag and has a new "Excluding Skills" section.

Tests

8 new specs in pkg/domain/exclude_test.go:

• an excluded skill is not listed, not found by search, and cannot be read;
• a sibling skill in the same repo still works;
• files stay on disk;
• glob patterns work;
• the default is unchanged;
• the exclusion survives an index rebuild;
• invalid patterns are rejected.

With the filter switched off, 5 of them fail. go test ./... passes.

[walcz-de]

Friendly ping on this one. We use SKILLSERVER_EXCLUDE_SKILLS to hide a meta-skill that distracts smaller local models, without disabling the whole repository. If the glob-based approach is not what you want, I can change it to an explicit list.