contrib-scoutlisted

Research any open-source repository end to end and answer the core question — SHOULD YOU contribute to it? — with a GO / NO-GO / GO-IF verdict backed by evidence: snapshot, momentum, contribution landscape (PR acceptance rates, outside-contributor merge rates, time-to-merge and time-to-first-response latency, first-timer outcomes), available-work inventory, issue health, governance, community sentiment, and event fitness for Hacktoberfest / GSoC. Use when the user asks 'should I contribute to X', wants a before-I-contribute due-diligence check on a project, asks whether a project accepts outside PRs, wants contribution-health numbers like PR merge rates or stale-PR counts, asks which repo to pick for Hacktoberfest or Google Summer of Code or an open-source portfolio, asks whether a repo is worth their time, wants to find unclaimed good-first-issues, or asks for a deep dive on an open-source codebase's health and dynamics before investing time in it.
rabbive/contrib-scout · ★ 1 · Code & Development · score 72

Install: claude install-skill rabbive/contrib-scout

# Should I Contribute? — repository contribution research Research ANY open-source repository and produce a detailed analysis report: what it is, how healthy it is, how it actually treats outside contributors, what a PR/issue from a stranger would experience — and, at the end, a clear GO / NO-GO / GO-IF verdict on whether YOU should contribute. The core insight: PR *acceptance* is a much better signal of open-source health than PR *volume* — a project can look busy while quietly ignoring everyone outside the core team. ## Output contract Deliver ONE markdown report with these sections (see Report template at the end): 1. Executive summary — 3-6 bullet verdict (GO / GO-IF / NO-GO) with the headline numbers 2. Snapshot — identity, stats, license, stack 3. Momentum — is the project alive and shipping? 4. Contribution landscape — the core: open-PR census, age buckets, outside-author share, merge rates, **latency**, **substance**, first-timer outcomes 5. Available work — unclaimed newcomer issues; is there anything for the requester to actually DO? 6. Issue health — open issues, stale bugs, "documented bug with unmerged fix" search 7. Governance & maintainability — docs, templates, who actually merges, bus factor 8. Community sentiment — HN/Reddit/Discord signals, maintainer quotes 9. Event fitness — Hacktoberfest / GSoC suitability, **only when the requester mentions one** 10. Risks & opportunities for the requester 11. Methodology & caveats — every number gets its source and