Suggest awesome GitHub Copilot agents
Compare the repository's existing custom agents and current project needs with the GitHub awesome-copilot agent catalog, then recommend missing or outdated .agent.md files without installing or updating anything until the user explicitly asks.
When to invoke
- "Suggest awesome GitHub Copilot custom agents for this repo."
- "Which awesome-copilot agents should we add?"
- "Compare our .github/agents with awesome-copilot."
- "Find outdated local custom agents."
- "Update this custom agent from awesome-copilot."
Prerequisites and context
Use web access to read the awesome-copilot catalog and raw agent files. The catalog is at https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md; agent files are under https://github.com/github/awesome-copilot/tree/main/agents and raw files follow https://raw.githubusercontent.com/github/awesome-copilot/main/agents/{filename}.
Local custom agents live in .github/agents/ as *.agent.md files. Read YAML frontmatter from local files to extract description and tool configuration.
Analysis procedure
- Fetch the available custom agent list and descriptions from
https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md.
- List every local
.github/agents/*.agent.md file.
- Read local frontmatter and body to inventory descriptions, tools, and instructions.
- For each local filename that appears likely to exist upstream, fetch
https://raw.githubusercontent.com/github/awesome-copilot/main/agents/{filename}.
- Compare full local and remote content, including frontmatter, tools array, and body.
- Classify local agents as up-to-date, outdated, or local-only.
- Analyze repository context: languages (
.cs, .js, .py, and others), frameworks such as ASP.NET, React, Azure usage, project type, documentation needs, recent chat context, feature requests, code review patterns, and workflow requirements.
- Match catalog agents to gaps that would add value and are not already covered.
- Present a table only; include links to awesome-copilot agent files and similar local agents.
- Await a user request before installing or updating any agent.
Relevance criteria
| Signal |
Evidence to collect |
How it affects suggestions |
| Language |
File extensions, package manifests, build files |
Prefer agents that operate on actual stacks in the repo. |
| Framework |
ASP.NET, React, Azure, test frameworks, deployment files |
Suggest framework-specific agents only with matching evidence. |
| Project type |
Web app, API, library, tool, docs site |
Match agents to recurring tasks and operational needs. |
| Documentation |
README, specs, ADRs, docs folders |
Suggest documentation or architecture agents when docs work exists. |
| Chat history |
Recent pain points, feature requests, review themes |
Prioritize what the user is actively working on. |
| Existing coverage |
.github/agents/*.agent.md descriptions |
Avoid duplicates unless the local agent is outdated. |
Version comparison rules
| Comparison result |
Condition |
Output status |
| Up-to-date |
Entire local file exactly matches remote |
Already installed and up-to-date |
| Outdated |
Same filename exists remotely but content differs |
Installed but outdated (update available) |
| Not installed |
Remote catalog agent has no matching local file |
Not installed in repo |
| Local-only |
Local file has no matching remote |
Mention only when relevant to duplicate avoidance. |
For outdated agents, document specific differences: frontmatter description, tools array additions/removals/renames, or body content updates. The historical example principal-software-engineer.agent.md can differ because remote uses 'web/fetch' while local uses 'fetch'.
Installation and update rules
Do not install or update during the suggestion pass. When the user later requests specific agents:
- Download new agents into
.github/agents/.
- Replace outdated agents entirely with the latest remote version.
- Preserve file location in
.github/agents/.
- Do not adjust the downloaded content.
- Track progress while downloading or updating multiple assets.
Examples
Use links like these in the table when relevant:
| Awesome-Copilot Custom Agent |
Description |
Already Installed |
Similar Local Custom Agent |
Suggestion Rationale |
| amplitude-experiment-implementation.agent.md |
This custom agent uses Amplitude's MCP tools to deploy new experiments inside of Amplitude, enabling seamless variant testing capabilities and rollout of product features |
No |
None |
Would enhance experimentation capabilities within the product |
| launchdarkly-flag-cleanup.agent.md |
Feature flag cleanup agent for LaunchDarkly |
Yes |
launchdarkly-flag-cleanup.agent.md |
Already covered by existing LaunchDarkly custom agents |
| principal-software-engineer.agent.md |
Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation. |
Outdated |
principal-software-engineer.agent.md |
Tools configuration differs: remote uses 'web/fetch' vs local 'fetch' - update recommended |
Gotchas
- Do not install during recommendation: the first output is analysis only; wait for explicit user direction.
- Do not suggest duplicates: if a similar local agent already covers the need, report that instead of recommending another copy.
- Do not compare descriptions only: tools and body changes can make an agent outdated even when descriptions match.
- Do not reference prompt files: this skill is about custom agent
.agent.md files only.
Legacy VS Code instructions may mention #fetch, #runInTerminal, #todos, fetch, githubRepo, and curl; in this CLI skill, use available web or shell capabilities instead and do not expose unsupported tool names as frontmatter. The control words AWAIT, INSTALL, UPDATE, UNLESS, DIRECTED, and Download/Update mean wait for explicit user direction before changing local agents.
Output template
## Awesome GitHub Copilot agent suggestions
| Awesome-Copilot Custom Agent | Description | Already Installed | Similar Local Custom Agent | Suggestion Rationale |
| --- | --- | --- | --- | --- |
| `[agent-name.agent.md](https://github.com/github/awesome-copilot/blob/main/agents/agent-name.agent.md)` | `<description>` | `No | Yes | Outdated` | `<local filename or None>` | `<why it fits, duplicate rationale, or specific outdated differences>` |
Quality gate
References
1---2name: suggest-awesome-github-copilot-agents3description: Suggest relevant GitHub Copilot custom agent files from the github/awesome-copilot repository by comparing repository context with available agents, detecting already installed or outdated local .github/agents/*.agent.md files, and presenting a no-install table. Use when the user asks to suggest awesome GitHub Copilot custom agents, find agents to add, compare local agents with awesome-copilot, or update outdated custom agents.4---56<!-- Generated from harness/github-copilot/skills/suggest-awesome-github-copilot-agents/SKILL.md by harness/claude-code/scripts/convert_from_copilot.py. Edit the source, not this file. -->78# Suggest awesome GitHub Copilot agents910Compare the repository's existing custom agents and current project needs with the GitHub awesome-copilot agent catalog, then recommend missing or outdated `.agent.md` files without installing or updating anything until the user explicitly asks.1112## When to invoke1314- "Suggest awesome GitHub Copilot custom agents for this repo."15- "Which awesome-copilot agents should we add?"16- "Compare our .github/agents with awesome-copilot."17- "Find outdated local custom agents."18- "Update this custom agent from awesome-copilot."1920## Prerequisites and context2122Use web access to read the awesome-copilot catalog and raw agent files. The catalog is at `https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md`; agent files are under `https://github.com/github/awesome-copilot/tree/main/agents` and raw files follow `https://raw.githubusercontent.com/github/awesome-copilot/main/agents/{filename}`.2324Local custom agents live in `.github/agents/` as `*.agent.md` files. Read YAML frontmatter from local files to extract `description` and tool configuration.2526## Analysis procedure27281. Fetch the available custom agent list and descriptions from `https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md`.292. List every local `.github/agents/*.agent.md` file.303. Read local frontmatter and body to inventory descriptions, tools, and instructions.314. For each local filename that appears likely to exist upstream, fetch `https://raw.githubusercontent.com/github/awesome-copilot/main/agents/{filename}`.325. Compare full local and remote content, including frontmatter, tools array, and body.336. Classify local agents as up-to-date, outdated, or local-only.347. Analyze repository context: languages (`.cs`, `.js`, `.py`, and others), frameworks such as ASP.NET, React, Azure usage, project type, documentation needs, recent chat context, feature requests, code review patterns, and workflow requirements.358. Match catalog agents to gaps that would add value and are not already covered.369. Present a table only; include links to awesome-copilot agent files and similar local agents.3710. Await a user request before installing or updating any agent.3839## Relevance criteria4041| Signal | Evidence to collect | How it affects suggestions |42| --- | --- | --- |43| Language | File extensions, package manifests, build files | Prefer agents that operate on actual stacks in the repo. |44| Framework | ASP.NET, React, Azure, test frameworks, deployment files | Suggest framework-specific agents only with matching evidence. |45| Project type | Web app, API, library, tool, docs site | Match agents to recurring tasks and operational needs. |46| Documentation | README, specs, ADRs, docs folders | Suggest documentation or architecture agents when docs work exists. |47| Chat history | Recent pain points, feature requests, review themes | Prioritize what the user is actively working on. |48| Existing coverage | `.github/agents/*.agent.md` descriptions | Avoid duplicates unless the local agent is outdated. |4950## Version comparison rules5152| Comparison result | Condition | Output status |53| --- | --- | --- |54| Up-to-date | Entire local file exactly matches remote | `Already installed and up-to-date` |55| Outdated | Same filename exists remotely but content differs | `Installed but outdated (update available)` |56| Not installed | Remote catalog agent has no matching local file | `Not installed in repo` |57| Local-only | Local file has no matching remote | Mention only when relevant to duplicate avoidance. |5859For outdated agents, document specific differences: frontmatter `description`, tools array additions/removals/renames, or body content updates. The historical example `principal-software-engineer.agent.md` can differ because remote uses `'web/fetch'` while local uses `'fetch'`.6061## Installation and update rules6263Do not install or update during the suggestion pass. When the user later requests specific agents:64651. Download new agents into `.github/agents/`.662. Replace outdated agents entirely with the latest remote version.673. Preserve file location in `.github/agents/`.684. Do not adjust the downloaded content.695. Track progress while downloading or updating multiple assets.7071## Examples7273Use links like these in the table when relevant:7475| Awesome-Copilot Custom Agent | Description | Already Installed | Similar Local Custom Agent | Suggestion Rationale |76| --- | --- | --- | --- | --- |77| [amplitude-experiment-implementation.agent.md](https://github.com/github/awesome-copilot/blob/main/agents/amplitude-experiment-implementation.agent.md) | This custom agent uses Amplitude's MCP tools to deploy new experiments inside of Amplitude, enabling seamless variant testing capabilities and rollout of product features | No | None | Would enhance experimentation capabilities within the product |78| [launchdarkly-flag-cleanup.agent.md](https://github.com/github/awesome-copilot/blob/main/agents/launchdarkly-flag-cleanup.agent.md) | Feature flag cleanup agent for LaunchDarkly | Yes | `launchdarkly-flag-cleanup.agent.md` | Already covered by existing LaunchDarkly custom agents |79| [principal-software-engineer.agent.md](https://github.com/github/awesome-copilot/blob/main/agents/principal-software-engineer.agent.md) | Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation. | Outdated | `principal-software-engineer.agent.md` | Tools configuration differs: remote uses `'web/fetch'` vs local `'fetch'` - update recommended |8081## Gotchas8283- **Do not install during recommendation**: the first output is analysis only; wait for explicit user direction.84- **Do not suggest duplicates**: if a similar local agent already covers the need, report that instead of recommending another copy.85- **Do not compare descriptions only**: tools and body changes can make an agent outdated even when descriptions match.86- **Do not reference prompt files**: this skill is about custom agent `.agent.md` files only.8788Legacy VS Code instructions may mention `#fetch`, `#runInTerminal`, `#todos`, `fetch`, `githubRepo`, and `curl`; in this CLI skill, use available web or shell capabilities instead and do not expose unsupported tool names as frontmatter. The control words `AWAIT`, `INSTALL`, `UPDATE`, `UNLESS`, `DIRECTED`, and `Download/Update` mean wait for explicit user direction before changing local agents.8990## Output template9192```markdown93## Awesome GitHub Copilot agent suggestions9495| Awesome-Copilot Custom Agent | Description | Already Installed | Similar Local Custom Agent | Suggestion Rationale |96| --- | --- | --- | --- | --- |97| `[agent-name.agent.md](https://github.com/github/awesome-copilot/blob/main/agents/agent-name.agent.md)` | `<description>` | `No | Yes | Outdated` | `<local filename or None>` | `<why it fits, duplicate rationale, or specific outdated differences>` |98```99100## Quality gate101102- [ ] The awesome-copilot README agents catalog was fetched from `https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md`.103- [ ] Local `.github/agents/*.agent.md` files were listed and their frontmatter descriptions were read.104- [ ] Remote versions were fetched from `https://raw.githubusercontent.com/github/awesome-copilot/main/agents/{filename}` for comparable local agents.105- [ ] Each local match was classified as up-to-date, outdated, or local-only.106- [ ] Recommendations are grounded in repository languages, frameworks, project type, documentation needs, or chat context.107- [ ] Duplicates are avoided or explicitly marked as already covered.108- [ ] The response contains only the requested table and analysis, with no installation unless the user asked for it.109110## References111112- [Awesome Copilot agents catalog](https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md)113- [Awesome Copilot agents folder](https://github.com/github/awesome-copilot/tree/main/agents)
paulasilvatech