good-repolisted

# good-repo `good-repo` is a repository effectiveness skill. It treats a GitHub repo as a product surface that must help visitors answer: 1. **What is this?** 2. **Why should I care?** 3. **Can I trust it?** 4. **Can I try it quickly?** 5. **Can I contribute or maintain it?** ## Quality and success feature model A repo's quality is not measured by stars first. Stars are an outcome. Audit the features that make the right visitor understand, trust, try, use, and contribute: 1. **Clear front door** — GitHub description + README quickly explain what, who, why, and how to try. 2. **Proof that it works** — screenshots, demo, terminal output, runnable examples, evals, tests, notebooks, or sample responses fit the project class. 3. **Fast adoption path** — prerequisites, install, quick start, expected output, local dev path, package metadata. 4. **Accurate documentation** — README and docs match current code, links work, examples are real. 5. **Trust signals** — license, changelog/releases, roadmap/status, security/support where relevant, honest limits. 6. **Repo architecture** — files/folders match the project class and route depth cleanly. 7. **Automation and validation** — CI, tests, docs checks, evals, release validation prove the repo's promises. 8. **Contribution readiness** — contributing guidance, PR/issue templates, test commands, maintainer expectations. 9. **Discoverability** — GitHub description, homepage URL, topics, social preview, package keywords. 10. **Focus and