Sep 20, 2026

Awesome Copilot Equips Your Copilot With Community Agents, Instructions, and Skills

A 39k-star, community-built collection of custom agents, instructions, skills, hooks, workflows, and plugins for GitHub Copilot — installable from the Copilot CLI or gh in one line.

#tutorial#ai-agents#developer-tools#workflow

GitHub Copilot's customization primitives — custom agents, path-triggered instructions, skills — are powerful, but out of the box you are authoring all of them yourself. github/awesome-copilot, at 39k stars, is a community-created collection that hands you the ready-made versions, installable with one command.

Why This Skill Matters

The repository's main table indexes four resource types plus a Cookbook: Agents (specialized Copilot agents that integrate with MCP servers), Instructions (coding standards applied automatically by file pattern), Skills (self-contained folders with instructions and bundled assets), and Plugins (curated bundles of agents and skills for specific workflows). Hooks and workflows get their own docs pages alongside them. The companion website, awesome-copilot.github.com, adds full-text search and filtering across the collection — the README describes it as hundreds of resources — plus a Learning Hub of guides.

Two structural facts make this collection more than a link dump. Skills here follow the Agent Skills specification (agentskills.io): each one is a folder with a SKILL.md plus bundled scripts, templates, and reference data, loaded on demand. And the two packaging layers ship real install paths: plugins install through the Copilot CLI marketplace, and skills install through the GitHub CLI — one command each, not a copy-paste archaeology session.

One caution the repo states itself: the customizations are sourced from third-party developers, so inspect any agent and its documentation before installing.

Installation

Plugins go through the Copilot CLI. For most users the marketplace is already registered:

copilot plugin install <plugin-name>@awesome-copilot

If you see an unknown-marketplace error, register it once first:

copilot plugin marketplace add github/awesome-copilot
copilot plugin install <plugin-name>@awesome-copilot

Individual skills install through the GitHub CLI (v2.90.0 or later):

gh skills install github/awesome-copilot acquire-codebase-knowledge

Real Workflow: Onboard Onto an Unfamiliar Codebase

  1. Install the skill:
gh skills install github/awesome-copilot acquire-codebase-knowledge
  1. Prompt with one of the skill's documented triggers:
Map this codebase and document the architecture.
  1. Read what lands on disk. The skill bundles document templates — ARCHITECTURE.md, STACK.md, STRUCTURE.md, TESTING.md, and more — plus a scan.py script that supports the discovery pass.

The skill's own description scopes it honestly: it fires for repository-level discovery requests like "onboard me to this repo" or "create codebase docs", and it does not trigger for routine feature implementation, bug fixes, or narrow code edits unless you ask for repository-level discovery.

Real Workflow: Install a Workflow Plugin

  1. Browse the plugins table on the website or docs/README.plugins.md and pick the bundle matching your work.
  2. Install it:
copilot plugin install <plugin-name>@awesome-copilot
  1. If the marketplace name is rejected, register it once with copilot plugin marketplace add github/awesome-copilot, then retry the install.

Tips

  • Point an AI agent at the collection with the machine-readable llms.txt the website exposes — it lists agents, instructions, and skills in structured form.
  • New to Copilot customization? The Learning Hub covers the core concepts — agents, skills, instructions — before you dive into individual resources.
  • Skills that follow the Agent Skills spec stay readable by other compatible agents, so installing one for Copilot does not lock the assets away.
  • The Cookbook collects copy-paste-ready recipes for working with Copilot APIs.

When Not to Use This

The resources target Copilot tooling — if your team standardizes on a different agent, most of the collection needs porting, not installing. Third-party sourcing means every entry deserves the inspection pass the README asks for. And if your team already maintains its own instructions and review standards, importing community bundles on top can quietly conflict with them.


See the leaderboard for more skills.