Report · marked 27 Aug 2026
remotion-dev/remotion
Solid foundations, held back in a few specific places.
TypeScript · 57,438 stars · 13,497 files · branch main
73
/100
B+
Instructions
26/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on readme as an entry point.Setup
14/18Whether an agent can install the project and get it running without a human. Losing marks on environment config.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 lint and format rules.Context economy
6/20Whether the repo fits in a context window, or fights it. Losing marks on no committed build output and file sizes fit in context.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
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.
02
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.
03
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 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, Copilot instructions
✓Instruction quality
12/12
Specific enough that an agent can act on it.
1,694 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 14/18 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 (test, ts-build, stylecheck, formatting, format, build…)
scripts/ directory
✗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
2/2
The language runtime version is pinned.
package.json engines.node >=16
–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
1542 test files against 9065 source files.
e.g. .github/scripts/ci.test.ts, .pi/extensions/commit/index.test.ts, .pi/extensions/pullfrog-monitor/monitor.test.ts
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
6 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
3/3
Strict type checking is on, which catches a whole class of agent mistakes before they run.
Context economy 6/20 D
Whether the repo fits in a context window, or fights it.
✗No committed build output
3/6
Generated output is committed: __pycache__/.
Add these to .gitignore and `git rm -r --cached` them. Generated files pollute search results, so an agent grepping for a function finds the compiled copy and edits the wrong file.
✓.gitignore hygiene
3/3
.gitignore covers 43 patterns.
✗File sizes fit in context
0/6
69 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.
packages/lambda/src/test/integration/renders/old-version-bundle/bundle.js — 2300KB
packages/example-videos/videos/0.ts — 1869KB
packages/google-fonts/scripts/google-fonts.ts — 1596KB
✗Repository weight
0/5
About 4209MB 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 🎥 Make videos programmatically with React ## Setup ``` bun install ``` ## Commands ``` bun build # produce a build bun test # run the test suite, must pass before any commit bun format # format bun ts-build bun stylecheck bun formatting bun build-docs bun testssr ``` ## Layout - `packages/` 9046 source files - `scripts/` 1 source file ## Conventions - Tests live alongside the code they cover, following `.github/scripts/ci.test.ts`. - TypeScript runs in strict mode. Type errors are the fastest feedback available, so do not weaken it. - CI defines what passing means. See `.github/workflows/changelog.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `packages/lambda/src/test/integration/renders/old-version-bundle/bundle.js` is 2300KB. 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/remotion-dev/remotion.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/remotion-dev/remotion)Other TypeScript repositories, marked
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.