PluginBench
Skill
Official
Review
Audit score 70

suggest-awesome-github-copilot-agents

github/awesome-copilot

Finds and recommends GitHub Copilot Custom Agents from awesome-copilot, flagging duplicates and outdated versions.

What is suggest-awesome-github-copilot-agents?

This skill analyzes a repository's context, chat history, and existing .github/agents/ custom agents, then suggests relevant GitHub Copilot Custom Agents from the awesome-copilot repository that aren't already present. It also detects when locally installed agents are outdated compared to their awesome-copilot source and can install or update agents on request.

  • Fetches the list of available Custom Agents and descriptions from the awesome-copilot repository
  • Scans the local .github/agents/ folder and reads front matter to inventory existing custom agents
  • Fetches remote versions of locally installed agents and diffs them to detect outdated content
  • Analyzes repository context and chat history to match relevant agents to project needs
  • Outputs a structured comparison table with install status, similar local agents, and suggestion rationale
  • Downloads new agents or updates outdated ones into .github/agents/ only when explicitly requested

How to install suggest-awesome-github-copilot-agents

npx skills add https://github.com/github/awesome-copilot --skill suggest-awesome-github-copilot-agents
Prerequisites
  • Coding agent environment with fetch (or runInTerminal/curl), githubRepo, and todos tool access
  • Local repository using .github/agents/ folder convention for Custom Agent files (*.agent.md with YAML front matter)
Claude Code
Cursor
Windsurf
Cline

How to use suggest-awesome-github-copilot-agents

  1. 1.Open the repository in your coding agent and invoke the suggest-awesome-github-copilot-agents skill
  2. 2.Let it fetch the available Custom Agents list from the awesome-copilot README.agents.md using the fetch tool
  3. 3.It scans .github/agents/ in your repo and reads front matter to inventory existing custom agents
  4. 4.It fetches the remote version of each local agent and compares content to flag up-to-date, outdated, or missing agents
  5. 5.Review the resulting table showing each awesome-copilot agent, description, install status, similar local agent, and rationale
  6. 6.Tell the skill which specific agents to install or update; it will not act without this explicit request
  7. 7.On request, it downloads new agents into .github/agents/ or replaces outdated ones with the latest version, preserving file content as-is

Use cases

Good for
  • Discovering new Copilot Custom Agents relevant to a project's language, framework, or workflow needs
  • Auditing a repo's .github/agents/ folder to find outdated agents that need syncing with upstream
  • Avoiding duplicate agent installations by cross-checking against existing local agents before adding new ones
  • Bulk-reviewing agent coverage gaps based on recent chat history and development pain points
  • Updating an outdated custom agent file to match the latest version from awesome-copilot
Who it's for
  • Developers maintaining a library of GitHub Copilot Custom Agents in a repository
  • Teams standardizing on awesome-copilot agents who need to track upstream updates
  • Repo maintainers wanting to avoid duplicate or stale custom agent configurations

suggest-awesome-github-copilot-agents FAQ

Will it install agents automatically?

No. It only presents a suggestion table and waits for explicit user direction before downloading or updating any agent files.

How does it avoid suggesting duplicates?

It scans .github/agents/ for existing custom agent files, reads their front matter descriptions, and compares them against the awesome-copilot agent list before suggesting anything.

How does it detect outdated agents?

It fetches the remote version of each locally installed agent from the awesome-copilot raw GitHub URL and compares full file content, including front matter, tools array, and body, to find differences.

What happens to file content when an agent is updated?

The entire local file is replaced with the latest remote version as-is; the skill does not modify or adjust content.

What tools does this skill rely on?

It requires fetch (or curl via runInTerminal) to retrieve remote content, githubRepo to read the awesome-copilot repository, and todos to track progress during downloads/updates.

Full instructions (SKILL.md)

Source of truth, from github/awesome-copilot.


name: suggest-awesome-github-copilot-agents description: 'Suggest relevant GitHub Copilot Custom Agents files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing custom agents in this repository, and identifying outdated agents that need updates.'

Suggest Awesome GitHub Copilot Custom Agents

Analyze current repository context and suggest relevant Custom Agents files from the GitHub awesome-copilot repository that are not already available in this repository. Custom Agent files are located in the agents folder of the awesome-copilot repository.

Process

  1. Fetch Available Custom Agents: Extract Custom Agents list and descriptions from awesome-copilot README.agents.md. Must use fetch tool.
  2. Scan Local Custom Agents: Discover existing custom agent files in .github/agents/ folder
  3. Extract Descriptions: Read front matter from local custom agent files to get descriptions
  4. Fetch Remote Versions: For each local agent, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g., https://raw.githubusercontent.com/github/awesome-copilot/main/agents/<filename>)
  5. Compare Versions: Compare local agent content with remote versions to identify:
    • Agents that are up-to-date (exact match)
    • Agents that are outdated (content differs)
    • Key differences in outdated agents (tools, description, content)
  6. Analyze Context: Review chat history, repository files, and current project needs
  7. Match Relevance: Compare available custom agents against identified patterns and requirements
  8. Present Options: Display relevant custom agents with descriptions, rationale, and availability status including outdated agents
  9. Validate: Ensure suggested agents would add value not already covered by existing agents
  10. Output: Provide structured table with suggestions, descriptions, and links to both awesome-copilot custom agents and similar local custom agents AWAIT user request to proceed with installation or updates of specific custom agents. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
  11. Download/Update Assets: For requested agents, automatically:
    • Download new agents to .github/agents/ folder
    • Update outdated agents by replacing with latest version from awesome-copilot
    • Do NOT adjust content of the files
    • Use #fetch tool to download assets, but may use curl using #runInTerminal tool to ensure all content is retrieved
    • Use #todos tool to track progress

Context Analysis Criteria

🔍 Repository Patterns:

  • Programming languages used (.cs, .js, .py, etc.)
  • Framework indicators (ASP.NET, React, Azure, etc.)
  • Project types (web apps, APIs, libraries, tools)
  • Documentation needs (README, specs, ADRs)

🗨️ Chat History Context:

  • Recent discussions and pain points
  • Feature requests or implementation needs
  • Code review patterns
  • Development workflow requirements

Output Format

Display analysis results in structured table comparing awesome-copilot custom agents with existing repository custom agents:

Awesome-Copilot Custom AgentDescriptionAlready InstalledSimilar Local Custom AgentSuggestion Rationale
amplitude-experiment-implementation.agent.mdThis custom agent uses Amplitude's MCP tools to deploy new experiments inside of Amplitude, enabling seamless variant testing capabilities and rollout of product features❌ NoNoneWould enhance experimentation capabilities within the product
launchdarkly-flag-cleanup.agent.mdFeature flag cleanup agent for LaunchDarkly✅ Yeslaunchdarkly-flag-cleanup.agent.mdAlready covered by existing LaunchDarkly custom agents
principal-software-engineer.agent.mdProvide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.⚠️ Outdatedprincipal-software-engineer.agent.mdTools configuration differs: remote uses 'web/fetch' vs local 'fetch' - Update recommended

Local Agent Discovery Process

  1. List all *.agent.md files in .github/agents/ directory
  2. For each discovered file, read front matter to extract description
  3. Build comprehensive inventory of existing agents
  4. Use this inventory to avoid suggesting duplicates

Version Comparison Process

  1. For each local agent file, construct the raw GitHub URL to fetch the remote version:
    • Pattern: https://raw.githubusercontent.com/github/awesome-copilot/main/agents/<filename>
  2. Fetch the remote version using the fetch tool
  3. Compare entire file content (including front matter, tools array, and body)
  4. Identify specific differences:
    • Front matter changes (description, tools)
    • Tools array modifications (added, removed, or renamed tools)
    • Content updates (instructions, examples, guidelines)
  5. Document key differences for outdated agents
  6. Calculate similarity to determine if update is needed

Requirements

  • Use githubRepo tool to get content from awesome-copilot repository agents folder
  • Scan local file system for existing agents in .github/agents/ directory
  • Read YAML front matter from local agent files to extract descriptions
  • Compare local agents with remote versions to detect outdated agents
  • Compare against existing agents in this repository to avoid duplicates
  • Focus on gaps in current agent library coverage
  • Validate that suggested agents align with repository's purpose and standards
  • Provide clear rationale for each suggestion
  • Include links to both awesome-copilot agents and similar local agents
  • Clearly identify outdated agents with specific differences noted
  • Don't provide any additional information or context beyond the table and the analysis

Icons Reference

  • ✅ Already installed and up-to-date
  • ⚠️ Installed but outdated (update available)
  • ❌ Not installed in repo

Update Handling

When outdated agents are identified:

  1. Include them in the output table with ⚠️ status
  2. Document specific differences in the "Suggestion Rationale" column
  3. Provide recommendation to update with key changes noted
  4. When user requests update, replace entire local file with remote version
  5. Preserve file location in .github/agents/ directory