agentreadme

Report · marked 25 Aug 2026

f/prompts.chat

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

HTML · 167,890 stars · 1,535 files · branch main

85 /100 A
Instructions 26/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on readme as an entry point.Setup 20/20Whether an agent can install the project and get it running without a human. Full marks.Verification loop 23/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.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 5/10How quickly anything new can orient itself. Losing marks on written documentation and license.

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

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
License
Without a license nobody can safely reuse this, and some tools will refuse to work with it at all.
03
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.

The full marking

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

Instructions 26/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.
8,936 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 2/3
README exists but never explains how to get the thing running.
Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.
Setup 20/20 A+

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 (dev, build, db:deploy, start, lint, db:generate…)
scripts/ directory
✓Environment config 4/4
.env.example documents what the app needs to run.
✓Pinned runtime version 2/2
The language runtime version is pinned.
package.json engines.node 24.x
✓Reproducible environment 2/2
compose.yml gives a known-good environment.
Verification loop 23/25 A

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

✗Tests exist 6/8
52 test files against 528 source files.
e.g. packages/prompts.chat/src/__tests__/builder.test.ts, packages/prompts.chat/src/__tests__/parser.test.ts, packages/prompts.chat/src/__tests__/platforms.test.ts
✓Test command is discoverable 7/7
An agent can find and run `npm run test`.
✓Continuous integration 4/4
5 GitHub Actions workflows define what "passing" means.
✓Lint and format rules 3/3
eslint.config.mjs encodes the house style.
✓Static type checking 3/3
Strict type checking is on, which catches a whole class of agent mistakes before they run.
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 29 patterns.
✗File sizes fit in context 4/6
2 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.
scripts/generate-book-pdf.ts — 149KB
src/data/api-docs.ts — 102KB
✗Repository weight 0/5
About 511MB 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 f/prompts.chat 
undefined

Open the raw markdown  or  curl -o AGENTS.md agentreadme.com/draft/f/prompts.chat.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 85 out of 100

[![agent ready](https://agentreadme.com/badge/f/prompts.chat.svg)](https://agentreadme.com/f/prompts.chat)

Other HTML repositories, marked

docker/awesome-compose 38 D QSCTech/zju-icicles 26 F PKUanonym/REKCARC-TSC-UHT 30 D dejan23/agentreadme 98 A+

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