Expose the /debug-live skill through MCP /prompts

[bendtherules]

I am having a few issues related to discovery of the /debug-live skill. But also all of them can be solved easily by exposing the skill through the mcp prompts feature.

1. It is not auto-registered within VSCode copilot.
   The skill exists at both ~/.vscode/extensions/ozzafar.debugmcpextension-2.2.0/skills/debug-live/ and ~/Library/Application Support/Code/User/skills/debug-live/, but it never appears in the agent's loaded skill list and skill-lock.json. It's unclear whether the runtime doesn't scan those paths, or whether something else prevents it from being discovered.
2. Similarly, for other agents, you would either need to install the skill in the well-known directories like .agents/ or specifically for each agent. That doesn't make a lot of sense it's too easy to break. I know that we already have helper commands to do this, but it's always going to be limited to a few popular agents.
3. Instead of all this duplicate effort, I suggest simply exposing it as a prompt through MCP's native prompt support directly. This will make it compatible with all MCP consumers who understand the prompt feature (including VSCode). The tools can then also refer back to that prompt, suggesting that agents should first read the prompt to understand how to use the tool properly.

I'm not sure what the reason was to go for route one and two instead of going for third option. I suppose it was a intentional decision. So I'd like to understand if there was any specific reason behind not using MCP prompts?

[ozzafar]

hi @bendtherules!
The issue with MCP prompt is that it's not triggerable (like skill) in all harnesses.
Therefore I think your #2 suggestion is actually the best option, to register it in .copilot/ with .agents/ as fallback to other agents which should honor this path.

[bendtherules]

Yeah, that sounds fair. But maybe also expose through mcps looking forward? Although that might cause duplicate slash commands.