Support subfolders for skills to better organize them

[cathysull]

Describe the feature or problem you'd like to solve

Support subfolders for skills to better organize them

Proposed solution

Got the below message when trying to move all my "testing" related skills into a subfolder under the skills folder. I have over 10 skills I've created and the flat folders are getting messy fast.

Support subfolders: C:\Users<me>.copilot\skills\testing

"The Copilot CLI currently does not support subfolders under the skills\ directory.** It only scans the immediate children of ~/.copilot/skills/ for SKILL.md files. Nesting them in a testing\ subfolder breaks discovery. This would be a good feature request — being able to organize skills into categories. You could file that via /feedback in the CLI if you'd like."

Example prompts or workflows

No response

Additional context

No response

[markhilkert]

+1, this would be great for sharing skills without worrying about conflicting skill names

[joannanowakowska]

Agreed — it would also be helpful to distinguish between skills created by you or your team and those reused from other sources

[paolomainardi]

I just agree with this, nested skills are super useful, and they are already supported by other coding agents, at least in opencode, having this feature makes the skill way more portable.

[alexalok]

they are already supported by other coding agents, at least in opencode

codex supports that as well

[BrysAdamed]

+1 for that.

Also it would be nice if we could specify more paths then just ~/.github/skills. We have a nested subfolder with frontend that specify it's own skills and when I work on both frontend and backend then the frontend skills gets ignored.

[suewonjp]

Can you give higher priority to this particular feature?

Many organizations have a situation where multiple teams share one repository due to various historical and business reasons.
Those multiple teams should cram their particular agent skills (to solve their respective domain problems) into the same folder .github/skills, which is clearly a problematic situation that may easily cause headaches.

[alex-moshilov-sndk]

+1
I just agree with this.

[dariuszzzlukasik]

+1

[RRRajput]

+1

[himanshuguptan]

+1, and also support for same skill names across different directory paths

[copilot-cli-bot]

This appears to be resolved as of GitHub Copilot CLI v1.0.86. Please update to that release or a newer stable version. We're closing this as completed. If it still happens, please comment with your version and reproduction steps.