archubbuck/suggest-awesome-github-copilot-agents
assets/plugins/awesome-copilot/skills/suggest-awesome-github-copilot-agents/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add archubbuck/workspace-architect suggest-awesome-github-copilot-agentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 4:40 AM133.3s1 file scanned
SKILL.md
- 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
- Fetch Available Custom Agents: Extract Custom Agents list and descriptions from awesome-copilot README.agents.md. Must use
fetchtool. - Scan Local Custom Agents: Discover existing custom agent files in
.github/agents/folder - Extract Descriptions: Read front matter from local custom agent files to get descriptions
- 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>) - 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)
- Analyze Context: Review chat history, repository files, and current project needs
- Match Relevance: Compare available custom agents against identified patterns and requirements
- Present Options: Display relevant custom agents with descriptions, rationale, and availability status including outdated agents
- Validate: Ensure suggested agents would add value not already covered by existing agents
- 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.
- 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
#fetchtool to download assets, but may usecurlusing#runInTerminaltool to ensure all content is retrieved - Use
#todostool to track progress
- Download new agents to
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 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 |
Local Agent Discovery Process
- List all
*.agent.mdfiles in.github/agents/directory - For each discovered file, read front matter to extract
description - Build comprehensive inventory of existing agents
- Use this inventory to avoid suggesting duplicates
Version Comparison Process
- 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>
- Pattern:
- Fetch the remote version using the
fetchtool - Compare entire file content (including front matter, tools array, and body)
- Identify specific differences:
- Front matter changes (description, tools)
- Tools array modifications (added, removed, or renamed tools)
- Content updates (instructions, examples, guidelines)
- Document key differences for outdated agents
- Calculate similarity to determine if update is needed
Requirements
- Use
githubRepotool 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:
- Include them in the output table with ⚠️ status
- Document specific differences in the "Suggestion Rationale" column
- Provide recommendation to update with key changes noted
- When user requests update, replace entire local file with remote version
- Preserve file location in
.github/agents/directory
Related Skills
archubbuck/frontend-design
development
VerifiedTrustedCommunity
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
15SKILL.mdUpdated May 5, 2026
archubbuck/claude-api
tools
VerifiedTrustedCommunity
Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).
15SKILL.mdUpdated Apr 30, 2026
archubbuck/xlsx
development
VerifiedTrustedCommunity
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
11SKILL.mdUpdated May 6, 2026
archubbuck/webapp-testing
tools
VerifiedTrustedCommunity
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
11SKILL.mdUpdated May 6, 2026