Skip to content

[BUG] Vscode Copilot installation breaks skills install from skills.sh #2156

@cortopy

Description

@cortopy

Description

Since the refactor into skills, I noticed that VScode github agents are unable to find skills I have installed under .agents.

The thing is when installing skills with skills.sh the command considers VScode as compatible with the .agents directory and so it installs skills there.

The problem is that BMAD installs Github Copilot into .github. This isn't incorrect as such. But agents that load bmad skills from .github can't then find skills from .agents and search in bizarre places, like BMAD folders.

My fix for now is to choose "codex" as target for bmad, even though I don't use "codex" so that the bmad skills are installed in ".agents".

I don't know what the solution would be but it'd be great if BMAD was less opaque about this and made it explicit that most harnesses (including vscode) recognise .agents.

It's weird that choosing cortex installs in .agents even though cortex has .cortex but github copilot installs in .github even though .agents are also supported

Skills.sh makes this installation far less opaque, where in addition to the Universal path you can also pick the custom directory. For example, in the screenshot I have, you can see "Universal" includes Codex and Github copilot. Then if you want, you can also choose "Cortex code" to install in .cortex/skills as an alternative, and so on

Image

Steps to reproduce

Install BMAD with Github copilot as target

Expected behavior

I'd like to install Github Copilot in the .agents directory, but I don't know if that's everybody's preference so:

As a user, it shouldn't be a surprise where skills are installed so that it doesn't conflict with other configs I may have.

Actual behavior

I can't choose where BMAD is installed

Screenshots

No response

Which module is this for?

BMad Method (BMM) - Core Framework

BMad Version

6.2.2

Which AI IDE are you using?

Copilot CLI / GitHub Copilot

Operating System

macOS

Relevant log output

Confirm

  • I've searched for existing issues
  • I'm using the latest version

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions