Popular for its size, but the engineering basics lag behind the interest.
๐ Build powerful agents and configurations with the complete collection of Claude Code from an Anthropic hackathon winner, refined over 10+ months.
Documentation
63
README documents how to install the project.
README is present.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
48
No CI configuration detected in this repository.
โ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
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.
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (tests).
Linter or formatter configured (eslint.config.js).
Project health
100
Dependency manifest found (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)
- 22Forks
- 0Releases
Community
- 57% - FairCommunity health
- โauthors own >50% of commits
- 124Watchers
Responsiveness
- โMedian issue response
- โMedian PR merge time
- 0Open issues
Repository files28 root entries
- .claude
- .claude-plugin
- agents
- assets
- commands
- contexts
- docsGood: Security policy present.
- examples
- hooks
- mcp-configs
- plugins
- rules
- schemas
- scripts
- skills
- testsGood: Test files detected (tests).
- .gitignoreGood: .gitignore present.
- .markdownlint.json
- commitlint.config.js
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (โ12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (โ8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (โ8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- eslint.config.jsGood: Linter or formatter configured (eslint.config.js).
- LICENSEGood: Licensed under MIT.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (โ15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Issue: No live demo link in the README (โ20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.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.Issue: No run or usage instructions found (โ45 pts).Fix: Add a section showing how to start or use the project.
- README.zh-CN.md
- the-longform-guide.md
- the-shortform-guide.md