0
/ 100
Solid engineering. The main gap is visibility.
AI agent orchestration platform — single binary, hot-reloadable policies
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
- 4README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
70
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
76
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
Test files detected (dashboard/e2e/smoke.spec.ts).
Lockfile present (Cargo.lock). Installs are reproducible.
CI is configured (.github/workflows/ci-macos-trusted.yml).
Issue or PR templates present.
Project health
100
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 4Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 8Watchers
Responsiveness
- <1hMedian issue response
- 11hMedian PR merge time
- 22Open issues
Repository files37 root entries
- .cargo
- .claude
- .githooks
- .githubGood: CI is configured (.github/workflows/ci-macos-trusted.yml).Good: Issue or PR templates present.
- dashboardGood: Test files detected (dashboard/e2e/smoke.spec.ts).
- docs
- migrations
- out
- policies
- routines
- scripts
- skills
- src
- tests
- .claudeignore
- .gitattributes
- .gitignoreGood: .gitignore present.
- .nvmrcGood: Environment pinned via .nvmrc.
- agentdesk.example.yaml
- ARCHITECTURE.md
- build.rs
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CLAUDE.md
- defaults.json
- DRIFT_REPAIR_ANALYSIS.md
- EPIC_3016_DESIGN.md
- FEATURES.md
- justfile
- LICENSEGood: Licensed under MIT.
- Makefile
- NOTICE
- OVERHAUL_LOG.md
- package.json
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Good: README has code examples.Good: README links to a live demo or deployed app.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
- rust-toolchain.toml
- TEST_PLAN.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/itismyfield/agentdesk)