0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.
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 (88).
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 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
82
README is present.
CONTRIBUTING guide found.
README documents how to install the project.
A license file is present.
Engineering
49
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.
Test files detected (packages/skillstore/tests).
CI is configured (.github/workflows/test-recalculate-scores.yml).
Lockfile present (skills/199-biotechnologies/deep-research/requirements.txt). Installs are reproducible.
Linter or formatter configured (skills/bellybook/genesis/templates/web-react/eslint.config.js).
Project health
86
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)
- 31Forks
- 11Releaseslatest 7mo ago
Community
- -Community health
- -authors own >50% of commits
- 379Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 1Open issues
Repository files9 root entries
- .githubGood: CI is configured (.github/workflows/test-recalculate-scores.yml).
- packagesGood: Test files detected (packages/skillstore/tests).
- pending
- schemas
- scripts
- skillsGood: A license file is present.Good: 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.Good: Code of conduct present.Good: Linter or formatter configured (skills/bellybook/genesis/templates/web-react/eslint.config.js).Good: Lockfile present (skills/199-biotechnologies/deep-research/requirements.txt). Installs are reproducible.Good: Environment pinned via skills/adminturneddevops/gke-expert/Dockerfile.Good: Security policy present.
- .gitignoreGood: .gitignore present.
- 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.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/aiskillstore/marketplace)