0
/ 100
Strong early engineering with some momentum.
a minimalist agent that teaches you to create coding agents
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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 license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
Engineering
68
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
CI is configured (.github/workflows/docs.yml).
Lockfile present (uv.lock). Installs are reproducible.
Test files detected (tests).
Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).
Project health
98
Dependency manifest found (pyproject.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)
- 13Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 67Watchers
Responsiveness
- 2dMedian issue response
- <1hMedian PR merge time
- 19Open issues
Repository files13 root entries
- .githubGood: CI is configured (.github/workflows/docs.yml).
- dev-notes
- src
- testsGood: Test files detected (tests).
- websiteGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
- .gitignoreGood: .gitignore present.
- .python-versionGood: Environment pinned via .python-version.
- AGENTS.md
- landing.html
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.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.
- session-temp.jsonl
- uv.lockGood: Lockfile present (uv.lock). Installs are reproducible.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/alejandro-ao/tau)