Skills not invocable as slash commands and not listed in /skills for plugin installed on the repo level,

[Yasiu]

Describe the bug

When a plugin is auto-installed via repo declaration (.github/copilot/settings.json -> enabledPlugins), its skill(s) do not show up as slash command (e.g. /<skill_name>) and are not listed when using /skills.
However the skills can still be invoked by natural language proving that they are loaded into the context, e.g. "Please call the <skill_name>".

Meanwhile, the agent from the same plugin correctly appears in /agent.

The above works correctly for plugins installed on user level.

Affected version

GitHub Copilot CLI 1.0.68

Steps to reproduce the behavior

1. Create a plugin with at least one skill and one agent; publish it to a (local or remote) marketplace.
2. Declare it in a consumer repo's .github/copilot/settings.json under enabledPlugins.
3. Open a copilot session from that repo - auto-install triggers, plugin installed
4. Run /skills - the plugin's skill is not listed.
5. Type /<skill_name> - that is not available.
6. Run /agent - the plugin's agent is listed correctly.
7. Ask the agent in natural language to call the skill - the agent invokes the skill and it executes successfully, proving it is loaded and functional.

Expected behavior

For the skills comming from repo enabled plugins:

• /skills should list all skills that are actually loaded and usable in the session
• skills should be invokable as slash command, i.e. /<skill_name> should be possible

Additional context

• OS: Windows 11
• CPU Architecture: x64