github-repo-vitals
Read a GitHub repository's vital signs with keyless curl — commit recency, release cadence, issue/PR responsiveness, and bus factor — interpreted into an is-this-project-alive verdict. Use when asked is this repo maintained, check this project before we build on it, how active is this library's development, or compare these repos' health. Produces the vitals with their reads, the responsiveness sampling, the rate-limit-aware command set, and the alive/coasting/abandoned verdict.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill github-repo-vitals --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# GitHub Repo Vitals Skill The repository is where a project's real pulse shows — registries say what shipped; the repo says whether anyone's home. GitHub's REST API serves the vitals keylessly (60 requests/hour anonymous — enough for a handful of checks, and the skill budgets accordingly): last commit, release cadence, issue responsiveness, contributor spread. The interpretation discipline matters here too: stars measure *attention once*, commits measure *life now*, and an unanswered issue tracker measures the thing adopters actually care about. ## What This Skill Produces - **The verdict** — alive / coasting / life-support / abandoned, with reasoning - **The vitals table** — last commit, release recency/cadence, open-issue dynamics, contributor concentration - **The responsiveness sample** — how recent issues/PRs actually got treated (the tell no summary stat carries) - **The commands** — each vital's curl, within the anonymous rate budget ## Required Inputs Ask for these if not provided: - **The repo** — owner/name; from a package check, the registry metadata's repository URL (chain from [package-health](../package-health/SKILL.md)) - **The stakes** — building on it, contributin
- What This Skill Produces
- Required Inputs
- Framework: The Vitals and the Budget
- Output Format
- Quality Checks
- Anti-Patterns
What does the github-repo-vitals skill do?
Read a GitHub repository's vital signs with keyless curl — commit recency, release cadence, issue/PR responsiveness, and bus factor — interpreted into an is-this-project-alive verdict. Use when asked is this repo maintained, check this project before we build on it, how active is this library's development, or compare these repos' health. Produces the vitals with their reads, the responsiveness sampling, the rate-limit-aware command set, and the alive/coasting/abandoned verdict.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill github-repo-vitals --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.