agentreadme

Report · marked 25 Aug 2026

amruthpillai/reactive-resume

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

TypeScript · 41,723 stars · 1,445 files · branch main

Fix these first

01
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.
02
Pinned runtime version
Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.
03
Static type checking
Turn on `"strict": true`. Type errors are the fastest feedback an agent gets, and non-strict mode silently discards most of them.

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, Copilot instructions
Instruction quality 12/12
Specific enough that an agent can act on it.
15,614 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 18/20 A

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

Deterministic install 6/6
pnpm-lock.yaml pins the dependency tree.
Found pnpm-lock.yaml
Discoverable commands 6/6
Commands are declared where an agent will look for them.
package.json scripts (build, doctor, check, docs:gen, db:generate, db:migrate…)
Environment config 4/4
.env.example documents what the app needs to 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 2/2
dockerfile gives a known-good environment.
Verification loop 24/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
365 test files against 990 source files.
e.g. apps/server/src/http/app.test.ts, apps/server/src/http/auth.test.ts, apps/server/src/http/public-resume-pdf.test.ts
Test command is discoverable 7/7
An agent can find and run `npm run check`.
Continuous integration 4/4
6 GitHub Actions workflows define what "passing" means.
Lint and format rules 3/3
biome.json encodes the house style.
Static type checking 2/3
Type checking is configured, but not in strict mode.
Turn on `"strict": true`. Type errors are the fastest feedback an agent gets, and non-strict mode silently discards most of them.
Context economy 17/20 A

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 39 patterns.
File sizes fit in context 6/6
No source file is large enough to crowd out a context window.
Repository weight 2/5
About 242MB 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 amruthpillai/reactive-resume
undefined

Open the raw markdown  or  curl -o AGENTS.md agentreadme.com/draft/amruthpillai/reactive-resume.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 94 out of 100

[![agent ready](https://agentreadme.com/badge/amruthpillai/reactive-resume.svg)](https://agentreadme.com/amruthpillai/reactive-resume)

Other TypeScript repositories, marked

freeCodeCamp/freeCodeCamp 69 B openclaw/openclaw 68 B nilbuild/developer-roadmap 45 C vuejs/vue 67 B n8n-io/n8n 87 A anomalyco/opencode 80 A-

All TypeScript 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