Support `path` field when using wildcard name

[Krakor92]

Motivation / use case

It would be super nice to have the ability to install every skills that belong to a single directory only (e.g., skills/engineering/, skills/productivity). Unfortunately, wildcard name = "*" necessarily matches all skills from the repo root, and the path field is silently ignored. The only workaround is listing every skill individually, but it defeats the purpose of wildcards and doesn't scale when the repo adds new skills.

Desired behaviour

The path field should work on wildcard dependencies to scope which subdirectory is scanned for skills.

[[skills]]
name = "*"
source = "mattpocock/skills"
path = "skills/engineering"
exclude = ["resolving-merge-conflicts"]

This should discover and install only skills under skills/engineering/, excluding resolving-merge-conflicts.

Acceptance criteria

• path on a wildcard dependency scopes which subdirectory is scanned
• Omitting path behaves exactly as before
• Documentation clarifies that path works on both named and wildcard skills

[sentry-pierre]

I checked the code and can confirm this is exactly how it works today.

• packages/dotagents/src/config/schema.ts defines wildcardSkillDependencySchema without a path field, so a path on a wildcard entry is silently dropped.
• packages/dotagents-lib/src/skills/resolver.ts calls discoverAllSkills on the repo root with no subdirectory scoping.

Your acceptance criteria cover the right surfaces — schema, resolver behavior, and docs. Merci for the clear report. A maintainer can take it from here.

[ahfoysal]

Hi! I’d like to work on this. I plan to add the optional path field to the wildcard dependency schema and resolver input, scope wildcard discovery to that directory while preserving existing behavior when path is omitted, and update the documentation.

I’ll add regression tests covering scoped discovery, exclusions within the selected path, and backward compatibility without path. Would that implementation scope match your expectations?

[Krakor92]

Yeah sure, but it's not for me to decide if you can or cannot work on this, I have no agency over this project 😅
Feel free to link a PR I guess, maintainers will eventually look at it at some point.