Problem
Hi,
I'm using the CLI to install skills (npx skills add) and noticed that by default it places them under .agents/skills/. My question is whether there's an option — a CLI flag, an environment variable, or a config setting in some project file — that allows specifying .github/skills/ as the destination instead of (or in addition to) .agents/skills/.
I'm working with GitHub Copilot and would prefer to keep skills under .github/skills/ so they stay aligned with the structure Copilot expects/recognizes, rather than using the .agents/skills/ folder.
What I've tried so far:
Checked the README but didn't find an explicit option for this.
Even with --agent github-copilot, it still installed to .agents/skills/ instead of .github/skills/.
npx skills add https://github.com/github/awesome-copilot --skill conventional-commit --agent github-copilot
If there's already a way to do this and I just missed it, I'd appreciate a pointer. If not, I'm raising this as a feature suggestion.
Thanks in advance.
Proposed Solution
I'd suggest one of the following (or a combination):
Explicit destination flag: Add an --output or --target flag to manually specify the install folder, e.g.:
npx skills add <repo> --skill <name> --agent github-copilot --output .github/skills
Project config file: Support a config file (e.g. skills.config.json or a section in package.json) where the install path can be set once, avoiding the need to pass the flag on every command:
json {
"skillsPath": ".github/skills"
}
Either of these would solve the use case without changing the current default behavior.
Alternatives Considered
No response
Additional Context
No response
Problem
Hi,
I'm using the CLI to install skills (npx skills add) and noticed that by default it places them under .agents/skills/. My question is whether there's an option — a CLI flag, an environment variable, or a config setting in some project file — that allows specifying .github/skills/ as the destination instead of (or in addition to) .agents/skills/.
I'm working with GitHub Copilot and would prefer to keep skills under .github/skills/ so they stay aligned with the structure Copilot expects/recognizes, rather than using the .agents/skills/ folder.
What I've tried so far:
Checked the README but didn't find an explicit option for this.
Even with --agent github-copilot, it still installed to .agents/skills/ instead of .github/skills/.
npx skills add https://github.com/github/awesome-copilot --skill conventional-commit --agent github-copilot
If there's already a way to do this and I just missed it, I'd appreciate a pointer. If not, I'm raising this as a feature suggestion.
Thanks in advance.
Proposed Solution
I'd suggest one of the following (or a combination):
Explicit destination flag: Add an --output or --target flag to manually specify the install folder, e.g.:
npx skills add <repo> --skill <name> --agent github-copilot --output .github/skillsProject config file: Support a config file (e.g. skills.config.json or a section in package.json) where the install path can be set once, avoiding the need to pass the flag on every command:
Either of these would solve the use case without changing the current default behavior.
Alternatives Considered
No response
Additional Context
No response