Skip to content

Skills in .copilot/skills/ are invisible to all Copilot surfaces except Squad #1126

Closed

Description

@diberry

Summary

Skills in .copilot/skills/ are invisible to all GitHub Copilot surfaces except Squad itself. The official Agent Skills spec places project-level skills in .github/skills/, .claude/skills/, or .agents/skills/ -- .copilot/skills/ at repo root is not a recognized location.

This means Squad-created skills don't work with:

  • GitHub Copilot cloud agent
  • Copilot CLI (outside Squad)
  • VS Code Copilot extension (agent mode)
  • @copilot coding agent on issues
  • Any future Copilot surface

Evidence -- Three Independent Sources Verified

Source Project skills (repo-level) Personal skills (user-level)
GitHub docs -- About Agent Skills .github/skills/, .claude/skills/, .agents/skills/ ~/.copilot/skills/, ~/.agents/skills/
GitHub docs -- Add Skills .github/skills/, .claude/skills/, .agents/skills/ ~/.copilot/skills/, ~/.agents/skills/
VS Code docs -- Agent Skills .github/skills/, .claude/skills/, .agents/skills/ ~/.copilot/skills/, ~/.claude/skills/, ~/.agents/skills/

.copilot/skills/ (repo root) does not appear in any official documentation.

Source of Confusion

~/.copilot/skills/ (home directory) is valid for personal skills. .copilot/skills/ (repo root) looks like the project-level equivalent -- but it isn't. The actual project-level path is .github/skills/.

The .github/skills/ path is the universal project-level location for the Agent Skills open standard, which Copilot, Claude, and other agents all share. .claude/skills/ exists as an alternative format, not as evidence that each tool gets its own repo-root directory.

Top Threats

1. Customer mental model confusion

.copilot/skills/ at repo root creates an internally consistent but incorrect mental model. Customers who learn ~/.copilot/skills/ (personal) will predict .copilot/skills/ (project) -- and nothing in their experience corrects them, because Squad makes it work via hardcoded paths. This teaches every new Squad user the wrong convention.

2. Skills invisible to current and future Copilot surfaces

Every Copilot surface -- cloud agent, CLI, VS Code, @copilot coding agent, code review -- discovers from .github/skills/. As GitHub ships more Copilot-powered experiences, the gap between what Squad customers expect and what actually works widens. Customers who invest in writing skills discover they are invisible everywhere except their local Squad session.

Prior Art

Proposed Fix

  1. Move project-level skills from .copilot/skills/ to .github/skills/
  2. Update squad.agent.md skill-aware routing to check .github/skills/ (primary) and .squad/skills/ (team-discovered patterns)
  3. Add a migration note or backward-compat shim for existing repos

This makes Squad skills portable across the entire Copilot ecosystem while preserving .squad/skills/ for team-discovered patterns.

Activity

  1. bradygaster commented on May 18, 2026

    @bradygaster
    Collaborator

    @diberry @spboyer @tamirdresher can we confirm this? we deliberately moved them to their currently location from .squad thinking they'd become available.

    also, i am not sure i want squad-created skills available to non-squad copilot functionality.

  2. diberry commented on May 18, 2026

    @diberry
    ContributorAuthor

    @bradygaster I'm not concerned with .squad skills. Only the other skills.

  3. dat-intellis commented on May 18, 2026

    @dat-intellis

    This comment in your description does not seem correct:

    "The .github/skills/ path is the universal project-level location for the Agent Skills open standard, which Copilot, Claude, and other agents all share."

    Should it have been .agents/skills/ perhaps? Which seems to be the broadest supported path in harnesses.

    Not sure if that is supported by Claude though - they seem pretty intent on only using .claude/skills. I think there might be an --add-dirs flag which could be utilised in that case.

  4. diberry commented on May 20, 2026

    @diberry
    ContributorAuthor

    @dat-intellis Thank you for that correction.

  5. added 6 commits that reference this issue on Jun 13, 2026
    233e519
    9de50de
    d83aed6
    33261f7
    d5924b8
    dd4cd90
  6. added a commit that references this issue on Jun 13, 2026
    40f78f2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions