Running the pre-flight inspection…
Running the pre-flight inspection…
Agent-Ready Score
72/100Flight-worthy, minor squawks
[](https://sortielabs.com/score/laravel/laravel)
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 coverage7/7
2 rule files — Claude Code, Cursor, and Copilot users all get guidance.
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 verify0/7
No verify, check, lint or typecheck entry point found.
FIX → Add `scripts/verify.sh` (typecheck + lint + build + test) and require it in your agent rules.
Score another repo
Env template7/7
.env.example documents required secrets without leaking them.
.gitignore5/5
Present.
Lockfile committed0/4
No lockfile found.
FIX → Commit your lockfile so agents build against the same dependency tree you do.
License0/4
No license file.
FIX → Add a LICENSE — agents and humans both need to know what they're allowed to do.
README8/8
A real README exists.
Contributing guide0/4
No CONTRIBUTING guide.
FIX → A short CONTRIBUTING.md doubles as agent guidance for PR conventions.
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.