Evaluate a codebase for agent-friendliness based on autonomous agent best practices...
Evaluate how well a codebase supports autonomous agent execution based on the "How to Get Out of Your Agent's Way" principles.
Autonomous agents fail for predictable reasonsβmost are system design failures, not model failures. This evaluation checks whether infrastructure enables true autonomy: agents that run unattended, isolated, reproducible, and bounded by system constraints rather than human intervention.
Explore the codebase for indicators across all 12 principles. Key files to examine:
Environment & Isolation:
Dockerfile, docker-compose.yml, .devcontainer/Makefile, setup.sh, bootstrap.sh.github/workflows/, .gitlab-ci.yml, Jenkinsfile)devbox.json, flake.nixDependencies & State:
package-lock.json, yarn.lock, Pipfile.lock, Cargo.lock, go.sum).env.example, config templatesExecution & Interfaces:
bin/ scriptsQuality & Monitoring:
Read evaluation-criteria.md for detailed scoring rubric.
Score each of the 12 principles 0-3:
Output format:
# Agent-Ready Evaluation Report
**Overall Score: X/36** (Y%)
**Rating: [Excellent|Good|Needs Work|Not Agent-Ready]**
## Summary
[2-3 sentence assessment of overall agent-readiness]
## Principle Scores
| Principle | Score | Evidence |
|-----------|-------|----------|
| 1. Sandbox Everything | X/3 | [brief evidence] |
| 2. No External DB Dependencies | X/3 | [brief evidence] |
| 3. Clean Environment | X/3 | [brief evidence] |
| 4. Session-Independent Execution | X/3 | [brief evidence] |
| 5. Outcome-Based Instructions | X/3 | [brief evidence] |
| 6. Direct Low-Level Interfaces | X/3 | [brief evidence] |
| 7. Minimal Framework Overhead | X/3 | [brief evidence] |
| 8. Explicit State Persistence | X/3 | [brief evidence] |
| 9. Early Benchmarks | X/3 | [brief evidence] |
| 10. Cost Planning | X/3 | [brief evidence] |
| 11. Verifiable Output | X/3 | [brief evidence] |
| 12. Infrastructure-Bounded Permissions | X/3 | [brief evidence] |
## Top 3 Improvements
1. **[Highest impact improvement]**
- Current state: ...
- Recommendation: ...
- Impact: ...
2. **[Second improvement]**
...
3. **[Third improvement]**
...
## Strengths
- [What the codebase does well for agents]
## Detailed Findings
[Optional: deeper analysis of specific areas]
If time is limited, prioritize these high-signal indicators: