Skip to content

Project Skills from a parent directory don't work #1158

@shufan

Description

@shufan

Describe the bug

I authored an Agent Skill that I have been using extensively as a "User" skill in %USERPROFILE%.claude\skills\review-ado-pr\SKILL.md and everything has been working great.

Then, I wanted to test out its usage as a "Project" skill, and in particular from the root of a repo. This worked great from Claude Code, but when attempting to use it from Copilot CLI the skill would be listed by /skills list, but it would never be invoked by the agent, and when trying to manually activate it, the agent would complain:

● The skill "review-ado-pr" is not available in this environment.

  The available code review related skills are:

    - receiving-code-review - For handling feedback you've received on your code
    - requesting-code-review - For verifying your own work before merging
    - code-review (task agent) - For reviewing local code changes (staged/unstaged or branch diffs)

  These skills work with local Git changes, not Azure DevOps PR URLs directly. I don't have access to Azure DevOps
  APIs to fetch PR content from that URL.

Affected version

GitHub Copilot CLI version 0.0.396

Steps to reproduce the behavior

  1. Create a project skill at a root directory
  2. Launch Copilot CLI from a subdirectory of that root directory
  3. Use /skills list to see that the project skill should be "available"
  4. Try and manually trigger that skill and notice that the agent seems to think it's not available.

Expected behavior

A project skill in a root directory should be fully functional from Copilot CLi launched from a subdirectory of that root directory. This is a common scenario for skills that are useful across an entire repo.

Additional context

No response

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions