Report · marked 25 Aug 2026

pbakaus/impeccable

Ready for an agent to work in without hand-holding.

JavaScript · 62,530 stars · 3,270 files · branch main

86 /100 A

Instructions 27/27Whether the repo tells an agent how to behave before it starts guessing. Full marks.Setup 14/14Whether an agent can install the project and get it running without a human. Full marks.Verification loop 22/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on static type checking.Context economy 11/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability 9/10How quickly anything new can orient itself. Losing marks on repository description.

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

Fix these first

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.

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.

Repository weight

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

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: CLAUDE.md

✓Instruction quality 12/12

Specific enough that an agent can act on it.

14,057 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 14/14 A+

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

✓Deterministic install 6/6

bun.lock pins the dependency tree.

Found bun.lock

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

package.json scripts (build:skills, build:skills:release, build, build:release, build:browser, build:extension…)

scripts/ directory

–Environment config n/a

Not applicable — this reads as a library, with no environment to configure.

✓Pinned runtime version 2/2

The language runtime version is pinned.

package.json engines.node >=22.18.0

–Reproducible environment n/a

Not applicable — a library doesn't need a container to be worked on.

Verification loop 22/25 A

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

✓Tests exist 8/8

484 test files against 2212 source files.

e.g. tests/build.test.js, tests/ci-test-plan.test.mjs, tests/cli-args.test.mjs

✓Test command is discoverable 7/7

An agent can find and run `npm run test`.

✓Continuous integration 4/4

3 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

biome.json encodes the house style.

✗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 11/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 58 patterns.

✗File sizes fit in context 0/6

77 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.

.agents/skills/impeccable/scripts/live-browser.js — 489KB

.claude/skills/impeccable/scripts/live-browser.js — 489KB

.cursor/skills/impeccable/scripts/live-browser.js — 489KB

✗Repository weight 2/5

About 348MB checked out. Large enough that cloning and searching are both slow.

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

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 pbakaus/impeccable

undefined

Open the raw markdown or curl -o AGENTS.md agentreadme.com/draft/pbakaus/impeccable.md

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/pbakaus/impeccable.svg)](https://agentreadme.com/pbakaus/impeccable)

Other JavaScript repositories, marked

react/react 71 B+ affaan-m/ECC 90 A trekhleb/javascript-algorithms 69 B Snailclimb/JavaGuide 53 C+ airbnb/javascript 54 C+ vercel/next.js 77 B+

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