Suggest Awesome Github Copilot Skills
Discover awesome-copilot skills missing from your repo, avoid duplicates, and flag local copies that lag upstream.
Overview
Suggest Awesome GitHub Copilot Skills is an agent skill most often used in Build (also Ship, Operate) that recommends awesome-copilot skills and detects duplicates or outdated local SKILL.md files.
Install
npx skills add https://github.com/github/awesome-copilot --skill suggest-awesome-github-copilot-skillsWhat is this skill?
- Fetches the skills index from awesome-copilot README.skills.md via the fetch tool
- Scans local `.github/skills/` and reads each SKILL.md frontmatter
- Compares local skills to raw GitHub SKILL.md versions for drift detection
- Suggests relevant skills based on repo context and chat history
- Explicitly skips skills already present to reduce duplicate installs
Adoption & trust: 8.6k installs on skills.sh; 34.6k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You do not know which community Copilot skills fit your repo or whether your installed skills are behind upstream awesome-copilot.
Who is it for?
Repos already using or adopting `.github/skills` who want catalog-driven expansion tied to github/awesome-copilot.
Skip if: Projects that forbid network fetches in the agent loop or teams not using the awesome-copilot skill layout.
When should I use this skill?
You want relevant awesome-copilot skills suggested from repo context while avoiding duplicates and spotting outdated local skills.
What do I get? / Deliverables
You get a shortlist of skills to add plus clarity on which local skills need updates, without reinstalling what you already have.
- Ranked skill suggestions
- Duplicate and outdated-skill report versus awesome-copilot
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Installing and curating agent skills is core Build agent-tooling; the same audit helps when you expand tooling during Ship review or Operate iteration. Agent-tooling is where solo builders assemble `.github/skills` libraries and keep them aligned with community catalogs.
Where it fits
After cloning a SaaS starter, fetch README.skills.md and propose testing and review skills you lack.
Recommend documentation skills when chat shows heavy README and ADR work.
Before release, diff local security-review skill against awesome-copilot main.
Quarterly pass to flag outdated skills after awesome-copilot updates.
How it compares
Targeted awesome-copilot sync and gap analysis—not a generic marketplace browser like Prism’s full journey catalog.
Common Questions / FAQ
Who is suggest-awesome-github-copilot-skills for?
Solo builders and small teams on GitHub Copilot (or compatible agents) who maintain a local skills folder and want curated suggestions from awesome-copilot.
When should I use suggest-awesome-github-copilot-skills?
When bootstrapping Build agent-tooling, before a release when reviewing automation coverage in Ship, or during Operate when refreshing stale SKILL.md copies against upstream.
Is suggest-awesome-github-copilot-skills safe to install?
The skill instructs fetching public GitHub URLs; review the Security Audits panel on this Prism page and your org’s policy on agent network access before enabling it.
SKILL.md
READMESKILL.md - Suggest Awesome Github Copilot Skills
# Suggest Awesome GitHub Copilot Skills Analyze current repository context and suggest relevant Agent Skills from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.skills.md) that are not already available in this repository. Agent Skills are self-contained folders located in the [skills](https://github.com/github/awesome-copilot/tree/main/skills) folder of the awesome-copilot repository, each containing a `SKILL.md` file with instructions and optional bundled assets. ## Process 1. **Fetch Available Skills**: Extract skills list and descriptions from [awesome-copilot README.skills.md](https://github.com/github/awesome-copilot/blob/main/docs/README.skills.md). Must use `#fetch` tool. 2. **Scan Local Skills**: Discover existing skill folders in `.github/skills/` folder 3. **Extract Descriptions**: Read front matter from local `SKILL.md` files to get `name` and `description` 4. **Fetch Remote Versions**: For each local skill, fetch the corresponding `SKILL.md` from awesome-copilot repository using raw GitHub URLs (e.g., `https://raw.githubusercontent.com/github/awesome-copilot/main/skills/<skill-name>/SKILL.md`) 5. **Compare Versions**: Compare local skill content with remote versions to identify: - Skills that are up-to-date (exact match) - Skills that are outdated (content differs) - Key differences in outdated skills (description, instructions, bundled assets) 6. **Analyze Context**: Review chat history, repository files, and current project needs 7. **Compare Existing**: Check against skills already available in this repository 8. **Match Relevance**: Compare available skills against identified patterns and requirements 9. **Present Options**: Display relevant skills with descriptions, rationale, and availability status including outdated skills 10. **Validate**: Ensure suggested skills would add value not already covered by existing skills 11. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot skills and similar local skills **AWAIT** user request to proceed with installation or updates of specific skills. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO. 12. **Download/Update Assets**: For requested skills, automatically: - Download new skills to `.github/skills/` folder, preserving the folder structure - Update outdated skills by replacing with latest version from awesome-copilot - Download both `SKILL.md` and any bundled assets (scripts, templates, data files) - 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, infrastructure) - Development workflow requirements (testing, CI/CD, deployment) - Infrastructure and cloud providers (Azure, AWS, GCP) 🗨️ **Chat History Context**: - Recent discussions and pain points - Feature requests or implementation needs - Code review patterns - Development workflow requirements - Specialized task needs (diagramming, evaluation, deployment) ## Output Format Display analysis results in structured table comparing awesome-copilot skills with existing repository skills: | Awesome-Copilot Skill | Description | Bundled Assets | Already Installed | Similar Local Skill | Suggestion Rationale | |-----------------------|-------------|----------------|-------------------|-------------