Strong community interest, but tests, CI, or docs need work.
A library of practical AI-agent loops and an installable skill for finding, adapting, and designing repeatable agent workflows.
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
54
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.
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/ci.yml).
Lockfile present (worker/package-lock.json). Installs are reproducible.
Test files detected (worker/test).
Project health
100
Dependency manifest found (worker/package.json).
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)
- 98Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 1,196Watchers
Responsiveness
- 4hMedian issue response
- <1hMedian PR merge time
- 0Open issues
Repository files10 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- audits
- scripts
- site
- skills
- workerGood: Test files detected (worker/test).Good: Lockfile present (worker/package-lock.json). Installs are reproducible.Good: Dependency manifest found (worker/package.json).
- .gitignoreGood: .gitignore present.
- AGENTS.md
- LICENSEGood: Licensed under MIT.
- 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.