Running the pre-flight inspection…
Running the pre-flight inspection…
Agent-Ready Score
77/100Flight-worthy, minor squawks
[](https://sortielabs.com/score/sveltejs/svelte)
Agent rules file15/15
AGENTS.md found at the repo root — the open standard every major agent reads.
Rules have substance8/8
Your rules file is meaty enough to actually steer an agent.
Cross-tool coverage0/7
Only one (or zero) agent tools are catered for.
FIX → Add a one-line CLAUDE.md that imports AGENTS.md (`@AGENTS.md`) so every tool reads the same rules.
CI pipeline10/10
GitHub Actions workflows found — agents' mistakes get caught.
Tests exist8/8
Test files found — agents can prove their changes work.
One-command verify7/7
A verify/check command exists — the single most agent-friendly pattern there is.
Score another repo
Env template0/7
No .env.example found.
FIX → Ship a .env.example so agents (and humans) know what config exists without seeing values.
.gitignore5/5
Present.
Lockfile committed4/4
Dependencies are pinned — reproducible installs.
License4/4
Present.
README8/8
A real README exists.
Contributing guide4/4
Present.
Docs directory0/3
No docs/ directory.
FIX → A docs/ folder gives agents somewhere to look before inventing answers.
Typed foundations4/10
JavaScript without TypeScript config — agents get no type safety net.
FIX → Typed languages (or strict TS config) catch agent mistakes before runtime.