{"id":50662789,"url":"https://github.com/adewale/good-repo","last_synced_at":"2026-06-08T03:32:52.832Z","repository":{"id":362510434,"uuid":"1258835359","full_name":"adewale/good-repo","owner":"adewale","description":"A GitHub repository effectiveness skill for auditing and configuring repos for adoption, trust, discoverability, and contribution readiness.","archived":false,"fork":false,"pushed_at":"2026-06-04T13:47:29.000Z","size":104,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-06-04T15:16:19.146Z","etag":null,"topics":["agent-skill","claude-code","codex","cursor","documentation","github","open-source","pi","repo-health","repository"],"latest_commit_sha":null,"homepage":null,"language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/adewale.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2026-06-04T00:59:38.000Z","updated_at":"2026-06-04T13:47:41.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/adewale/good-repo","commit_stats":null,"previous_names":["adewale/good-repo"],"tags_count":null,"template":false,"template_full_name":null,"purl":"pkg:github/adewale/good-repo","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adewale%2Fgood-repo","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adewale%2Fgood-repo/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adewale%2Fgood-repo/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adewale%2Fgood-repo/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/adewale","download_url":"https://codeload.github.com/adewale/good-repo/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/adewale%2Fgood-repo/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":34047266,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-08T02:00:07.615Z","response_time":111,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["agent-skill","claude-code","codex","cursor","documentation","github","open-source","pi","repo-health","repository"],"created_at":"2026-06-08T03:32:51.554Z","updated_at":"2026-06-08T03:32:52.807Z","avatar_url":"https://github.com/adewale.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# good-repo\n\nA skill for making GitHub repositories easier to evaluate, adopt, contribute to, and trust.\n\n[![skills.sh](https://skills.sh/b/adewale/good-repo)](https://skills.sh/adewale/good-repo/good-repo)\n\n`good-repo` audits a repository as a product surface: README, proof, examples, install path, repo structure, GitHub metadata, automation, maintenance signals, and community defaults. It is designed to pair with [`good-readme`](https://github.com/adewale/good-readme): let `good-readme` handle the README deeply; use `good-repo` for everything around it.\n\n## Why this exists\n\nGreat code still loses users when the repo gives weak signals: no live demo, missing license, stale screenshots, vague GitHub description, no quick start, no contribution path, or no proof that the project actually works.\n\nThe first reference models are:\n\n- [`nutlope/hallmark`](https://github.com/nutlope/hallmark) — a productized skill repo with a tight README, visible examples, live demo, install instructions, packaged skill entry point, modular references, quality gates, roadmap, license, and enough proof for a visitor to decide quickly.\n- [`adewale/good-pr`](https://github.com/adewale/good-pr) — a small operational skill repo with real-pain origin, trigger-rich `SKILL.md`, PR templates, self-review checklist, readiness script, changelog, and evals.\n\n## Install\n\n```sh\nnpx skills add adewale/good-repo\n```\n\nOr copy `skills/good-repo/` into your agent skills directory.\n\nFor Pi package installs, the `package.json` includes `pi.skills`; for Claude/plugin installs, `.claude-plugin/marketplace.json` points to `./skills/good-repo`.\n\n## Usage\n\nAsk your coding agent from inside a repository:\n\n```text\nAudit this repo for GitHub effectiveness\n```\n\n```text\nConfigure this repo for maximum effectiveness\n```\n\n```text\nMake this repo launch-ready; use good-readme for the README\n```\n\n```text\ngood-repo audit https://github.com/nutlope/hallmark\n```\n\n```text\ngood-repo explain https://github.com/adewale/good-pr\n```\n\n```text\ngood-repo owner-audit adewale\n```\n\n## What it checks\n\n- **README/front door** — clarity, value proposition, install, usage, examples, honesty; delegated to `good-readme` when available.\n- **Proof** — screenshots, live demos, examples, evals, tests, sample outputs, reproducible recipes.\n- **Adoption path** — prerequisites, quick start, package metadata, release/download path, local dev setup.\n- **Repository architecture** — docs split, examples, skill/package entry points, references, scripts, evals, generated assets, fixtures.\n- **GitHub metadata** — description, homepage, topics, social preview, license, issue/discussion/wiki settings.\n- **GitHub-official baseline** — README, Community Profile health/files, license, contribution guidelines, issue/PR templates, security policy, CI/workflows, and large-file hygiene.\n- **Policy-check context** — Repolinter-style findings translated through repo class and maturity instead of copied blindly.\n- **Trust signals** — roadmap, changelog, maintenance status, contribution guidance, security policy, code owners.\n- **Automation** — CI, release workflow, dependency updates, docs/examples validation.\n- **Popularity/adoption context** — stars, forks, activity, contributor network, and quality signals without confusing popularity for quality.\n\n## Example audit output\n\n```markdown\n## Repo Effectiveness Audit\n\n**Project:** good-repo\n**Class:** agent skill / repo-effectiveness auditor\n**Score:** 85 / 100\n**Rating:** Strong\n\n### Snapshot\n- README/front door: clear purpose, install path, usage prompts, and relationship to good-readme.\n- Proof: full behavior eval results, fixture tests, sample audits, and lessons learned are present.\n- Adoption path: install command, `package.json`, `.claude-plugin`, and `pi.skills` metadata are configured.\n- GitHub metadata: description, topics, detected MIT license, issues enabled, wiki disabled; no canonical homepage yet.\n- Trust/maintenance: changelog, contributing guide, PR template, CI, and validation scripts exist; issue templates/support/security are still missing.\n\n### Top strengths\n1. Correct skill packaging — evidence: `skills/good-repo/SKILL.md`, `references/`, `.claude-plugin/marketplace.json`.\n2. Behavior proof is credible — evidence: `evals/evals.json`, `evals/run_eval.py`, `docs/eval-results-2026-06-04.md`.\n3. Repo-only artifacts are separated from runtime files — evidence: `docs/`, `evals/`, `.github/` live outside `skills/good-repo/`.\n\n### Priority improvements\n1. High impact — GitHub Community Profile is not complete — smallest fix: add `.github/ISSUE_TEMPLATE/bug_report.yml` and `.github/ISSUE_TEMPLATE/eval_case.yml`.\n2. Medium impact — support/security expectations are implicit — smallest fix: add `SUPPORT.md` and `SECURITY.md` with honest scope.\n3. Polish — README does not yet compare `good-repo` with Community Profile, Repolinter, and OpenSSF Scorecard — smallest fix: add a short positioning section.\n\n### Scores by category\n| Category | Score | Max |\n| --- | ---: | ---: |\n| Front door + README | 18 | 20 |\n| Proof + examples | 13 | 15 |\n| Adoption + DX | 13 | 15 |\n| Docs + architecture | 14 | 15 |\n| GitHub metadata | 8 | 10 |\n| Trust + governance | 10 | 15 |\n| Automation + release | 9 | 10 |\n| **Total** | 85 | 100 |\n\n### Suggested implementation plan\n1. Add issue templates for bug reports and new eval cases.\n2. Add `SUPPORT.md` and `SECURITY.md` after confirming maintainer contact/scope.\n3. Add a README section that positions `good-repo` against GitHub Community Profile, Repolinter, OpenSSF Scorecard, and package-health tools.\n4. Re-run `npm run validate`, fixture evals, and the repo readiness script.\n```\n\n## What's included\n\n| File | Purpose |\n|------|---------|\n| `skills/good-repo/SKILL.md` | Skill workflow, verbs, safety rails, output format |\n| `skills/good-repo/scripts/check-repo-readiness.sh` | Mechanical repo readiness check |\n| `skills/good-repo/scripts/audit-github-owner.py` | Owner/profile-wide GitHub audit script |\n| `evals/evals.json` | Expected skill behaviors and regression cases |\n| `evals/trigger-queries.json` | Trigger and near-miss cases for skill activation |\n| `evals/run_eval.py` | Skill-creator-inspired eval schema validator, output grader, and benchmark generator |\n| `evals/run_fixture_tests.py` | Fixture-level tests for mechanical repo readiness checks |\n| `evals/fixtures/` | Tiny repos for homepage, license, and skill-layout regression checks |\n| `evals/README.md` | Eval strategy for improving the skill |\n| `skills.sh.json` | skills.sh repository-page grouping metadata |\n| `docs/eval-results-2026-06-03.md` | First with-skill vs baseline smoke eval results |\n| `docs/eval-results-2026-06-04.md` | Full behavior eval suite results with with-skill vs baseline comparison |\n| `skills/good-repo/references/hallmark-exemplar.md` | What makes Hallmark an exemplary productized skill repo |\n| `skills/good-repo/references/good-pr-exemplar.md` | What makes good-pr an exemplary small operational skill repo |\n| `skills/good-repo/references/repo-anatomy.md` | Repo structure patterns by project type |\n| `skills/good-repo/references/github-official-baseline.md` | GitHub's official docs baseline for healthy/discoverable repos |\n| `skills/good-repo/references/community-profile-repolinter.md` | GitHub Community Profile and Repolinter interpretation guidance |\n| `skills/good-repo/references/popularity-signals.md` | Research-backed guidance on repo quality, popularity, stars, and adoption |\n| `skills/good-repo/references/skill-repo-best-practices.md` | Agent Skill folder structure, packaging, eval, and marketplace guidance |\n| `skills/good-repo/references/quality-checklist.md` | 100-point GitHub effectiveness rubric |\n| `skills/good-repo/references/github-settings.md` | GitHub metadata, settings, and automation checklist |\n| `skills/good-repo/references/anti-patterns.md` | Common repository smells and fixes |\n| `docs/recipes.md` | Copy-paste prompts for audits, launch prep, and cleanup |\n| `docs/sample-audits.md` | Scores and recommendations for a mixed GitHub sample |\n| `docs/adewale-repos-assessment.md` | Owner-wide audit for `github.com/adewale` |\n| `docs/adewale-recent-improvement-opportunities.md` | Recently modified `adewale` repos ranked by improvement opportunity |\n| `docs/community-profile-repolinter-focus.md` | Focused comparison of GitHub Community Profile and Repolinter |\n| `docs/multi-account-signal-assessment.md` | Cross-account audit of public repo portfolios and missed quality signals |\n| `docs/lessons-learned.md` | Lessons from owner-wide and cross-account audits |\n| `docs/repo-quality-popularity.md` | Research brief on whether repo quality affects popularity/adoption |\n| `CONTRIBUTING.md` | Lightweight contribution guidance |\n| `.claude-plugin/marketplace.json` | Claude plugin / skills CLI metadata |\n| `.github/PULL_REQUEST_TEMPLATE.md` | Minimal PR checklist |\n| `.github/workflows/ci.yml` | JSON, shell, link, and readiness validation |\n\n## What gets installed vs repo-only\n\n```text\nskills/good-repo/                     Installable runtime skill\n├── SKILL.md\n├── references/\n└── scripts/\n\nevals/                                Repo-only behavior checks\ndocs/                                 Repo-only reports, recipes, and lessons\n.github/                              Repo-only CI and contribution surfaces\n.claude-plugin/                       Marketplace/plugin metadata\npackage.json                          npm/Pi package metadata\n```\n\nThe runtime skill stays self-contained under `skills/good-repo/`. Reports, evals, CI, and contribution process stay outside the installable folder.\n\n## Relationship to good-readme\n\n`good-readme` is the README specialist. `good-repo` should not reimplement it when it is available. The intended stack is:\n\n1. Run `good-readme` to create or improve the README.\n2. Run `good-repo` to configure the rest of the repository.\n3. Re-run both before launch or release.\n\n## License\n\nMIT — see [LICENSE](LICENSE).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fadewale%2Fgood-repo","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fadewale%2Fgood-repo","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fadewale%2Fgood-repo/lists"}