Back to Details

suggest-awesome-github-copilot-agents

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Suggest Awesome GitHub Copilot Custom Agents

推荐优质GitHub Copilot自定义代理

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.
分析当前仓库上下文，从GitHub awesome-copilot仓库中推荐本仓库尚未拥有的相关自定义代理文件。自定义代理文件位于awesome-copilot仓库的agents文件夹中。

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
  1. 获取可用的自定义代理：从awesome-copilot README.agents.md提取自定义代理列表和描述。必须使用
    fetch
    工具。
  2. 扫描本地自定义代理：发现
    .github/agents/
    文件夹中已有的自定义代理文件
  3. 提取描述信息：读取本地自定义代理文件中的front matter以获取描述
  4. 获取远程版本：对于每个本地代理，使用GitHub原始URL（例如
    https://raw.githubusercontent.com/github/awesome-copilot/main/agents/<filename>
    ）从awesome-copilot仓库获取对应的版本
  5. 版本对比：对比本地代理内容与远程版本，识别：
    • 已更新至最新版本的代理（完全匹配）
    • 过时的代理（内容存在差异）
    • 过时代理中的关键差异（工具、描述、内容）
  6. 上下文分析：查看聊天历史、仓库文件和当前项目需求
  7. 相关性匹配：将可用的自定义代理与识别出的模式和需求进行匹配
  8. 呈现选项：展示相关自定义代理的描述、推荐理由以及包含过时代理在内的可用状态
  9. 验证：确保推荐的代理能够提供现有代理未覆盖的价值
  10. 输出：提供结构化表格，包含推荐内容、描述、指向awesome-copilot自定义代理以及类似本地自定义代理的链接 等待用户请求后再进行特定自定义代理的安装或更新。除非收到明确指示，否则请勿进行安装或更新操作。
  11. 下载/更新资源：对于用户请求的代理，自动执行以下操作：
    • 将新代理下载至
      .github/agents/
      文件夹
    • 用awesome-copilot中的最新版本替换过时的代理
    • 请勿修改文件内容
    • 使用
      #fetch
      工具下载资源，但可使用
      #runInTerminal
      工具执行
      curl
      命令以确保获取全部内容
    • 使用
      #todos
      工具跟踪进度

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
🔍 仓库模式：
  • 使用的编程语言（.cs、.js、.py等）
  • 框架标识（ASP.NET、React、Azure等）
  • 项目类型（Web应用、API、库、工具）
  • 文档需求（README、规格说明、ADR）
🗨️ 聊天历史上下文：
  • 近期讨论和痛点
  • 功能请求或实现需求
  • 代码审查模式
  • 开发工作流要求

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
以结构化表格展示分析结果，对比awesome-copilot自定义代理与本仓库已有的自定义代理：
Awesome-Copilot自定义代理描述是否已安装类似的本地自定义代理推荐理由
amplitude-experiment-implementation.agent.md该自定义代理使用Amplitude的MCP工具在Amplitude内部部署新实验，实现无缝的变体测试能力和产品功能发布❌ 未安装无可增强产品内的实验能力
launchdarkly-flag-cleanup.agent.md用于LaunchDarkly的功能标记清理代理✅ 已安装launchdarkly-flag-cleanup.agent.md已由现有LaunchDarkly自定义代理覆盖
principal-software-engineer.agent.md提供首席级别的软件工程指导，专注于工程卓越、技术领导力和务实的实现。⚠️ 已安装但过时principal-software-engineer.agent.md工具配置存在差异：远程使用
'web/fetch'
，本地使用
'fetch'
- 建议更新

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
  1. 列出
    .github/agents/
    目录下所有
    *.agent.md
    文件
  2. 对于每个发现的文件，读取front matter以提取
    description
  3. 构建完整的现有代理清单
  4. 使用该清单避免推荐重复的代理

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
  1. 对于每个本地代理文件，构建GitHub原始URL以获取远程版本：
    • 格式：
      https://raw.githubusercontent.com/github/awesome-copilot/main/agents/<filename>
  2. 使用
    fetch
    工具获取远程版本
  3. 对比整个文件内容（包括front matter、工具数组和正文）
  4. 识别具体差异：
    • front matter变更（描述、工具）
    • 工具数组修改（添加、移除或重命名工具）
    • 内容更新（说明、示例、指南）
  5. 记录过时代理的关键差异
  6. 计算相似度以确定是否需要更新

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
  • 使用
    githubRepo
    工具从awesome-copilot仓库的agents文件夹获取内容
  • 扫描本地文件系统中
    .github/agents/
    目录下的现有代理
  • 读取本地代理文件中的YAML front matter以提取描述
  • 对比本地代理与远程版本以检测过时代理
  • 与本仓库中的现有代理进行对比以避免重复
  • 关注当前代理库覆盖的空白领域
  • 验证推荐的代理是否符合仓库的用途和标准
  • 为每个推荐提供清晰的理由
  • 包含指向awesome-copilot代理和类似本地代理的链接
  • 清晰标记过时代理并注明具体差异
  • 除表格和分析内容外，请勿提供任何额外信息或上下文

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
当识别出过时代理时：
  1. 在输出表格中标记⚠️状态
  2. 在“推荐理由”列中记录具体差异
  3. 提供更新建议并注明关键变更点
  4. 当用户请求更新时，用远程版本替换整个本地文件
  5. 保留文件在
    .github/agents/
    目录中的位置