0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
A lightweight, zero-dependency CLI tool to manage and activate capabilities for AI coding assistants (such as Claude Code, Cursor, Trae, etc.).
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (89).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
60
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
Licensed under MIT.
Engineering
55
Test files detected (skills/baoyu-danger-gemini-web/scripts/gemini-webapi/client.test.ts).
CI is configured (.github/workflows/sync-skills.yml).
Lockfile present (skills/baoyu-danger-gemini-web/scripts/bun.lock). Installs are reproducible.
Linter or formatter configured (skills/brainstorming/scripts/node_modules/call-bind-apply-helpers/.eslintrc).
Issue or PR templates present.
Project health
85
.gitignore present.
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 166Forks
- 10Releaseslatest 2mo ago
Community
- -Community health
- -authors own >50% of commits
- 917Watchers
Responsiveness
- -Median issue response
- 8d 7hMedian PR merge time
- 6Open issues
Repository files26 root entries
- .agents
- .claude-plugin
- .codex-plugin
- .githubGood: CI is configured (.github/workflows/sync-skills.yml).Good: Issue or PR templates present.
- agents
- assets
- commands
- docs
- scripts
- skillsGood: Test files detected (skills/baoyu-danger-gemini-web/scripts/gemini-webapi/client.test.ts).Good: Linter or formatter configured (skills/brainstorming/scripts/node_modules/call-bind-apply-helpers/.eslintrc).Good: Lockfile present (skills/baoyu-danger-gemini-web/scripts/bun.lock). Installs are reproducible.Issue: Build artifacts or local files may be committed (skills/brainstorming/scripts/node_modules/.bin) (−40 pts).Fix: Remove them and add to .gitignore.
- spec
- template
- .gitignoreGood: .gitignore present.
- .mcp.json
- AGENTS.md
- CHANGELOG.md
- CLAUDE.md
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.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.
- GEMINI.md
- LICENSEGood: Licensed under MIT.
- package.jsonGood: Dependency manifest found (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.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.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- README.zh-CN.md
- SECURITY.mdGood: Security policy present.
- skills_index.json
- skills_sources.json
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/guanyang/open-agent-hub)