oss-evaluate-repo
Evaluate whether an OSS repo is worth long-term investment before committing time. Assesses project health, governance, community, bus factor, and trajectory. Use when deciding whether to contribute to a specific repo, choosing between multiple repos, or evaluating a project's sustainability. Not for checking if a repo accepts contributions — use oss-find-issue for that.
Profile →npx skills add majiayu000/claude-skill-registry --skill oss-evaluate-repo --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.
# Evaluate Repo Is this repo worth your time? Not every open source project deserves months of contribution effort. This skill evaluates project health, governance, community dynamics, and trajectory — so you invest in repos that will value your work and still exist in a year. ## Purpose Contributing to OSS is an investment. A single meaningful PR takes 10-40 hours including learning the codebase. Before investing that time, you should know: Is this project actively maintained? Is the community healthy? Will your contributions be reviewed? Could the project be abandoned next month? This skill answers those questions with evidence, not vibes. ## When to Use - Deciding whether to invest time in a specific OSS project - Choosing between multiple repos to contribute to - Evaluating a project before committing to a GSoC proposal - **NOT** for checking if a repo accepts external contributions — `oss-find-issue` does that - **NOT** for evaluating code quality — `oss-explore-repo` does that - **NOT** for repos you're already contributing to — too late, you're invested ## Prerequisites - A repo URL or name to evaluate - `gh` CLI authenticated - Clear goals for why you want to contribute (le
- Purpose
- When to Use
- Prerequisites
- Process
- 1. Check vital signs
- 2. Assess governance and bus factor
- 3. Evaluate community health
- 4. Check release cadence and stability
- 5. Evaluate CI and development practices
- 6. Thinking gate — user articulates the decision
- 7. Make the decision
- Related Skills
- Common Rationalizations
- Red Flags
Basic repo info
gh api repos/{owner}/{repo} --jq '{
Recent commit activity
git log --oneline -20 --since="6 months ago" 2>/dev/null || \
gh api repos/{owner}/{repo}/commits --jq '.[0:10] | .[] | "\(.commit.author.date[:10]) \(.commit.message | split("\n")[0])"'
Is the repo archived or in maintenance mode?
gh api repos/{owner}/{repo} --jq '.archived'
Top contributors (bus factor check)
gh api repos/{owner}/{repo}/contributors --jq '.[0:10] | .[] | "\(.contributions)\t\(.login)"'
Recent committers (who's active NOW, not historically)What does the oss-evaluate-repo skill do?
Evaluate whether an OSS repo is worth long-term investment before committing time. Assesses project health, governance, community, bus factor, and trajectory. Use when deciding whether to contribute to a specific repo, choosing between multiple repos, or evaluating a project's sustainability. Not for checking if a repo accepts contributions — use oss-find-issue for that.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill oss-evaluate-repo --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 majiayu000/claude-skill-registry, a repository with 534 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.