terrylica/cc-skills
Grade a repo

0

/ 100

GradeD

Getting some notice. Tests and CI would be the fastest wins.

Higher than 46% of 5,156 graded repos

Claude Code Skills Marketplace: plugins, skills for ADR-driven development, DevOps automation, ClickHouse management, semantic versioning, and productivity workflows

Documentation88
Engineering33
Health92
Shell54MIT1mo ago

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 A (90).

See your top fixes
Now
D
62
Potential
A
90

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    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.

  3. 3
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated 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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

88

Contributing guide5pt72

CONTRIBUTING guide found.

README12pt80

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

33

CI/CD14pt0

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.

Issue and PR templates6pt0

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.

Tests18pt35

Test files detected (.mise/tasks/tests).

Reproducibility6pt80

Lockfile present (bun.lock). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (plugins/itp-hooks/hooks/ruff.toml).

Project health

92

Dependency manifest6pt75

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 8
    Forks
  • 956
    Releaseslatest 8mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 54
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 56
    Open issues
Repository files22 root entries
  • .claude-plugin
  • .mise
    Good: Test files detected (.mise/tasks/tests).
  • docs
  • outputs
  • plugins
    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: Linter or formatter configured (plugins/itp-hooks/hooks/ruff.toml).
    Good: Environment pinned via plugins/calcom-commander/scripts/webhook-relay/Dockerfile.
  • scripts
  • .gitignore
    Good: .gitignore present.
  • .lychee.toml
  • .pre-commit-hooks.yaml
  • .releaserc.yml
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • CHANGELOG.md
  • CLAUDE.md
  • cli_spec.json
  • LICENSE
    Good: Licensed under MIT.
  • lychee.toml
  • package-lock.json
  • package.json
    Good: Dependency manifest found (package.json).
  • plugin.json
  • PRD.md
  • README.md
    Good: 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • tsconfig.json
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/terrylica/cc-skills)](https://www.repo-grade.com/report/terrylica/cc-skills)

More graded Shell repos