Popular for its size, but the engineering basics lag behind the interest.

A collection of AI agent skills for Clawdbot, Claude Code, Codex

Documentation

67

License6pt0

No license detected.

Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt80

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

33

Tests18pt0

No tests detected anywhere in the repository.

Add automated tests. They prove the code works and give contributors confidence to make changes.

Linting and formatting5pt0

No linter or formatter config found.

Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

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.

Reproducibility6pt70

Lockfile present (skills/elegant-reports/package-lock.json). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/trust-badges.yml).

Project health

100

Dependency manifest6pt100

Dependency manifest found (clawdbot/clawddocs/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)
  • 29
    Forks
  • 0
    Releases

Community

  • Community health
  • authors own >50% of commits
  • 234
    Watchers

Responsiveness

  • 3d 12h
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files11 root entries
  • .github
    Good: CI is configured (.github/workflows/trust-badges.yml).
  • clawdbot
    Good: Dependency manifest found (clawdbot/clawddocs/package.json).
  • codex
  • prompts
  • scripts
  • skills
    Good: Lockfile present (skills/elegant-reports/package-lock.json). Installs are reproducible.
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • COMPATIBILITY.md
  • CONTRIBUTING.md
    Good: 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.
  • 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.