Suggest Awesome Github Copilot Instructions
Discover missing or outdated GitHub Copilot instruction files by comparing your repo against the awesome-copilot catalog.
Overview
Suggest Awesome GitHub Copilot Instructions is an agent skill most often used in Build (also Ship review, Operate iterate) that audits `.github/instructions/` against the awesome-copilot catalog and recommends additions
Install
npx skills add https://github.com/github/awesome-copilot --skill suggest-awesome-github-copilot-instructionsWhat is this skill?
- Fetches the live instruction index from awesome-copilot README.instructions.md via #fetch
- Scans `.github/instructions/` and reads local front matter including applyTo patterns
- Fetches remote raw instruction files from GitHub for one-to-one version comparison
- Flags duplicates already present and surfaces outdated local copies that need updates
- Suggests relevant new instructions matched to repository context and chat history
- 5-step process: fetch catalog, scan local, extract descriptions, fetch remote versions, compare
Adoption & trust: 8.5k installs on skills.sh; 34.6k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You rely on Copilot in a real repo but do not know which awesome-copilot instruction packs you lack or whether local copies are behind upstream.
Who is it for?
Repos adopting or standardizing GitHub Copilot with `.github/instructions/` and a need to stay aligned with the community catalog.
Skip if: Teams not using GitHub Copilot instruction files, or when you only need one hand-written instruction with no catalog cross-check.
When should I use this skill?
You want relevant GitHub Copilot instruction suggestions from awesome-copilot based on repo context, without duplicating existing files and while catching outdated instructions.
What do I get? / Deliverables
You get a prioritized list of relevant instruction files to add plus clarity on which existing files should be refreshed from awesome-copilot.
- List of suggested awesome-copilot instruction files to add
- Report of local instructions that match, duplicate, or need updates versus remote
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Copilot instruction files are authored in the repo during product build; this skill is the canonical shelf for curating that agent context. Agent-tooling is where IDE and Copilot behavior is configured via `.github/instructions/` and related guidance files.
Where it fits
After cloning a monorepo, map missing awesome-copilot packs for API and testing conventions before the team codes against Copilot.
Before a release, verify review-related instruction files match upstream so Copilot suggestions align with your PR checklist.
When awesome-copilot adds new security instructions, diff local copies and queue updates without re-browsing the whole catalog.
How it compares
Use instead of manually scrolling awesome-copilot README lists and guessing filenames in your tree.
Common Questions / FAQ
Who is suggest-awesome-github-copilot-instructions for?
Solo and indie builders (and small teams) shipping in GitHub repos who want Copilot instructions that match project context without duplicate or stale files.
When should I use suggest-awesome-github-copilot-instructions?
During build when setting up agent-tooling, before ship when tightening review conventions, or during operate iterate when upstream awesome-copilot packs change—any time you want catalog-backed instruction hygiene.
Is suggest-awesome-github-copilot-instructions safe to install?
Review the Security Audits panel on this Prism page before installing; the skill expects network fetch to GitHub and reading files under your repository.
SKILL.md
READMESKILL.md - Suggest Awesome Github Copilot Instructions
# Suggest Awesome GitHub Copilot Instructions Analyze current repository context and suggest relevant copilot-instruction files from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md) that are not already available in this repository. ## Process 1. **Fetch Available Instructions**: Extract instruction list and descriptions from [awesome-copilot README.instructions.md](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md). Must use `#fetch` tool. 2. **Scan Local Instructions**: Discover existing instruction files in `.github/instructions/` folder 3. **Extract Descriptions**: Read front matter from local instruction files to get descriptions and `applyTo` patterns 4. **Fetch Remote Versions**: For each local instruction, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g., `https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/<filename>`) 5. **Compare Versions**: Compare local instruction content with remote versions to identify: - Instructions that are up-to-date (exact match) - Instructions that are outdated (content differs) - Key differences in outdated instructions (description, applyTo patterns, content) 6. **Analyze Context**: Review chat history, repository files, and current project needs 7. **Compare Existing**: Check against instructions already available in this repository 8. **Match Relevance**: Compare available instructions against identified patterns and requirements 9. **Present Options**: Display relevant instructions with descriptions, rationale, and availability status including outdated instructions 10. **Validate**: Ensure suggested instructions would add value not already covered by existing instructions 11. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions **AWAIT** user request to proceed with installation or updates of specific instructions. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO. 12. **Download/Update Assets**: For requested instructions, automatically: - Download new instructions to `.github/instructions/` folder - Update outdated instructions 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, .ts, etc.) - Framework indicators (ASP.NET, React, Azure, Next.js, etc.) - Project types (web apps, APIs, libraries, tools) - Development workflow requirements (testing, CI/CD, deployment) 🗨️ **Chat History Context**: - Recent discussions and pain points - Technology-specific questions - Coding standards discussions - Development workflow requirements ## Output Format Display analysis results in structured table comparing awesome-copilot instructions with existing repository instructions: | Awesome-Copilot Instruction | Description | Already Installed | Similar Local Instruction | Suggestion Rationale | |------------------------------|-------------|-------------------|---------------------------|---------------------| | [blazor.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/blazor.instructions.md) | Blazor development guidelines | ✅ Yes | blazor.instructions.md | Already covered by existing Blazor instructions | | [reactjs.instructions.md](https:/