contributor-setuplisted

# Skill: contributor-setup Audits everything a first-time visitor or contributor touches — README, issue templates, CONTRIBUTING.md, and the surrounding community-health files — then creates what's missing and upgrades what falls short. Analysis always comes first: never overwrite an existing file without showing the user what's wrong with it. Run this when asked to "make this repo contributor-friendly", prepare a project for open-sourcing, set up issue templates, or as the community slice of a repo maturity audit. ## Phase 1 — Analyze Start from GitHub's own community-profile scoring, then inspect each file locally: ```bash gh api repos/{owner}/{repo}/community/profile --jq '{health_percentage, files}' ls .github/ISSUE_TEMPLATE/ 2>/dev/null ls .github/PULL_REQUEST_TEMPLATE.md .github/CODEOWNERS CONTRIBUTING.md CODE_OF_CONDUCT.md SECURITY.md LICENSE README.md 2>/dev/null ``` Then judge quality, not just existence. Before writing anything, understand the project well enough to describe it accurately: read the manifest (`package.json` / `pom.xml` / …), the entry points, and any existing docs — the README must reflect what the project actually does, not a generic template. **README** — evaluate against the target group (the developer who lands on the repo knowing nothing): - [ ] Answers *what is this and why should I care* in the first screen (one-paragraph pitch, not an architecture essay) - [ ] States the added value: which problem it solves, for whom, and why to pick i