Report · marked 10 Oct 2026

github/awesome-copilot

Solid foundations, held back in a few specific places.

JavaScript · 39,883 stars · 3,464 files · branch main

71 /100 B+

Instructions 27/27Whether the repo tells an agent how to behave before it starts guessing. Full marks.Setup 12/20Whether an agent can install the project and get it running without a human. Losing marks on environment config and pinned runtime version.Verification loop 10/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on tests exist and test command is discoverable.Context economy 13/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

Test command is discoverable

Add a `test` script or a `test` target that runs the whole suite with no arguments. The convention is the interface — an agent tries `npm test` and `make test` before it tries reading your CI config.

File sizes fit in context

A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.

Environment config

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

The full marking

Every deduction below names the file or setting it came from.

Instructions 27/27 A+

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12

AGENTS.md is present, which is the format the most tools read.

Also found: Copilot instructions

✓Instruction quality 12/12

Specific enough that an agent can act on it.

17,747 characters, a workable length

names the actual commands to run

uses headings, so an agent can skim it

includes copyable code blocks

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 12/20 B-

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6

package-lock.json pins the dependency tree.

Found package-lock.json

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

package.json scripts (start, build, contributors:add, contributors:report, contributors:generate, contributors:check…)

✗Environment config 0/4

Nothing documents the environment this needs. An agent will get a runtime error it can't diagnose.

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

✗Pinned runtime version 0/2

No pinned runtime version.

Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.

✗Reproducible environment 0/2

No container or devcontainer definition.

A Dockerfile or devcontainer removes an entire class of 'it won't install' failures.

Verification loop 10/25 C

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✗Tests exist 6/8

49 test files against 459 source files.

e.g. .github/scripts/app-for-beginners-sync.test.mjs, .github/workflows/canvas-smoke-test.yml, eng/canvas-smoke-test.mjs

✗Test command is discoverable 0/7

There's no obvious way to run the tests. Even if tests exist, an agent won't reliably find the entry point.

✓Continuous integration 4/4

55 GitHub Actions workflows define what "passing" means.

✗Lint and format rules 0/3

No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.

A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

✗Static type checking 0/3

No static type checking.

A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

Context economy 13/20 B

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6

No generated directories committed.

✓.gitignore hygiene 3/3

.gitignore covers 20 patterns.

✗File sizes fit in context 0/6

12 source files are over 100KB.

A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.

skills/azure-architecture-autopilot/scripts/icons.py — 2094KB

extensions/pr-artifact-explorer/assets/app.js — 186KB

extensions/edit-tutorial/extension.mjs — 151KB

✗Repository weight 4/5

About 128.3MB checked out, which is comfortable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for github/awesome-copilot

# AGENTS.md

Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.

## Setup

```
npm ci
```

## Commands

```
npm run start                   # run the app
npm run build                   # produce a build
npm run contributors:add
npm run contributors:report
npm run contributors:generate
npm run contributors:check
npm run plugin:validate
npm run plugin:create
```

## Layout

- `extensions/` 181 source files
- `website/`    97 source files
- `skills/`     75 source files
- `eng/`        48 source files
- `cookbook/`   38 source files
- `hooks/`      12 source files

## Conventions

- Tests live alongside the code they cover, following `.github/scripts/app-for-beginners-sync.test.mjs`.
- CI defines what passing means. See `.github/workflows/advanced-copilot-cli-sync.lock.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `skills/azure-architecture-autopilot/scripts/icons.py` is 2094KB. It will not fit comfortably in context, so read it in parts.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown or curl -o AGENTS.md agentreadme.com/draft/github/awesome-copilot.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good JavaScript AGENTS.md looks like covers what to add by hand, and what AGENTS.md is explains the format itself.

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/github/awesome-copilot.svg)](https://agentreadme.com/github/awesome-copilot)

Other JavaScript repositories, marked

affaan-m/ECC 89 A react/react 71 B+ trekhleb/javascript-algorithms 69 B DietrichGebert/ponytail 74 B+ Snailclimb/JavaGuide 53 C+ airbnb/javascript 54 C+

All JavaScript repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in