Suggest commands should scan all skill/agent/instruction directories (not just .github/)

[wmmc88]

Summary

The suggest-awesome-github-copilot-skills, suggest-awesome-github-copilot-agents, suggest-awesome-github-copilot-instructions, and suggest-awesome-github-copilot-prompts commands only scan .github/ subdirectories for existing local assets. They miss user-level and alternative directories that GitHub Copilot CLI and VS Code actively use — including ~/.copilot/, .agents/, and .claude/ — leading to false "Not installed" results and duplicate suggestions.

Affected Commands

Command	Currently Scans	Misses
suggest-awesome-github-copilot-skills	.github/skills/	~/.copilot/skills/, .agents/skills/, .claude/skills/, ~/.claude/skills/
suggest-awesome-github-copilot-agents	.github/agents/	~/.copilot/agents/
suggest-awesome-github-copilot-instructions	.github/instructions/	~/.copilot/copilot-instructions.md, $HOME/.copilot/copilot-instructions.md, COPILOT_CUSTOM_INSTRUCTIONS_DIRS paths
suggest-awesome-github-copilot-prompts	.github/prompts/	(VS Code user-profile prompts)

Expected Behavior

Each suggest command should scan all directories where GitHub Copilot CLI and VS Code look for the respective asset type, per the official docs:

Skills (docs)

• Project-level: .github/skills/, .claude/skills/, .agents/skills/
• User-level: ~/.copilot/skills/, ~/.claude/skills/
• Additional: paths added via /skills add

Agents (docs)

• Repo-level: .github/agents/
• User-level: ~/.copilot/agents/
• Org/Enterprise-level: /agents in .github-private repo

Instructions (docs)

• .github/copilot-instructions.md
• .github/instructions/**/*.instructions.md
• $HOME/.copilot/copilot-instructions.md
• Paths from COPILOT_CUSTOM_INSTRUCTIONS_DIRS env var
• CLAUDE.md, GEMINI.md, AGENTS.md (in git root & cwd)

Prompts

• .github/prompts/**/*.prompt.md

Actual Behavior

All four commands only check .github/<type>/. For example, suggest-awesome-github-copilot-skills scans only .github/skills/ and misses skills installed at ~/.copilot/skills/ (the user-level location recommended in GitHub's own docs) and .agents/skills/. This causes skills that are already installed to show as "❌ Not installed".

Concrete example

A user has these skills installed:

• ~/.copilot/skills/github-issue-creator/ — not detected
• ~/.copilot/skills/teams-reply/ — not detected
• ~/.copilot/skills/fork/ — not detected
• .agents/skills/find-skills/ — not detected

The suggest command reports all as "❌ Not installed" and may suggest duplicates.

Reproduction Steps

1. Install a skill to ~/.copilot/skills/ (e.g., via a plugin or /skills add) or .agents/skills/
2. Run the suggest-awesome-github-copilot-skills command
3. Observe that the locally installed skill is not detected and may be suggested as "Not installed"

Impact

Medium — Misleading suggestions; users may install duplicate skills or miss that they already have equivalent functionality. The commands' primary purpose is to avoid duplicates and identify outdated skills, which is undermined when they don't scan all relevant directories.

Suggested Fix

Update the "Scan Local" step in each command to check all directories documented by GitHub for that asset type. For example, suggest-awesome-github-copilot-skills step 2 should change from:

2. Scan Local Skills: Discover existing skill folders in .github/skills/ folder

To:

2. Scan Local Skills: Discover existing skill folders in all known skill locations:
   • .github/skills/ (project-level)
   • .claude/skills/ (project-level, alternative)
   • .agents/skills/ (project-level, alternative)
   • ~/.copilot/skills/ (user-level)
   • ~/.claude/skills/ (user-level, alternative)

Similar changes should apply to the download/install steps, and equivalent updates for the agents, instructions, and prompts commands.

[wmmc88]

On second look, maybe the user-level scanning doesnt make sense if the prompts are meant to look at repository specific suggestions. But looking at a repo's .agents folder is probably still a valid ask?

[aaronpowell]

sure - if there's an improvement required, send a PR through for it