95

/ 100

GradeA

Excellent work. The main thing left to polish is the README.

Top 6% of 5,156 graded repos

Lifecycle Management for Agent Skills

Outstanding. A score of 95/100 puts this repo in a very small tier of truly well-engineered projects.

Top fixes

Highest-impact changes first, ranked by point weight

6 to address
  1. 1
    README12pt

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

  2. 2
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Dependency manifest6pt

    Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.

  4. 4
    Dependency manifest6pt

    Add a `keywords` array to help people find your package on npm.

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

README12pt70

README is present.

Contributing guide5pt97

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

100

Tests18pt100

Test files detected (packages/cli/src/commands/__meta__/telemetry-coverage.test.ts).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc).

Reproducibility6pt100

Lockfile present (package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

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)
  • 17
    Forks
  • 74
    Releaseslatest 3mo ago

Community

  • 100% - Good
    Community health
  • -
    authors own >50% of commits
  • 74
    Watchers

Responsiveness

  • 2d 5h
    Median issue response
  • <1h
    Median PR merge time
  • 22
    Open issues
Repository files59 root entries
  • .claude
  • .devcontainer
  • .git-crypt
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 3 ecosystems (npm, github-actions, docker). Dependencies stay current.
    Good: Issue or PR templates present.
  • .husky
  • .skillsmith
  • apps
  • benchmarks
  • data
  • docs
  • packages
    Good: Test files detected (packages/cli/src/commands/__meta__/telemetry-coverage.test.ts).
  • reports
  • scripts
  • supabase
  • tests
  • .dockerignore
  • .env.example
  • .env.schema
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitleaks.toml
  • .gitmodules
  • .linear-drift-allowlist
  • .markdownlint.json
  • .markdownlintignore
  • .mcp.json
  • .npmrc
  • .nvmrc
  • .prettierignore
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • .security-scan-ignore
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • docker-compose.yml
  • docker-entrypoint-native-per-package.sh
  • docker-entrypoint.sh
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • eslint.config.js
  • LICENSE
    Good: Licensed under Other.
  • lint-staged.config.js
  • NOTICE
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
    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.
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.base.json
  • tsconfig.json
  • turbo.json
  • vercel.json
  • vitest-e2e.config.ts
  • vitest.config.colocated.ts
  • vitest.config.root-tests.ts
  • vitest.config.ts
  • vitest.config.vscode.ts
  • vitest.e2e.config.ts
  • vitest.preset.ts
  • vitest.setup.ts
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/smith-horn/skillsmith)](https://www.repo-grade.com/report/smith-horn/skillsmith)

More graded TypeScript repos