oss-find-issue
Find unclaimed open source issues that match the user's skills and experience level. Searches for issues created by maintainers/org admins, checks contribution eligibility, and ranks by learning value. Use when looking for an issue to contribute to, starting OSS contributions, or finding GSoC-friendly issues.
Profile →npx skills add majiayu000/claude-skill-registry --skill oss-find-issue --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.
# Find Issue Find a real, unclaimed issue that matches your skills. from repos that actually want your contribution. This skill does the research; you decide what's worth your time. ## Purpose Not every issue is worth picking up. Random issues filed by drive-by users often get closed without merging. Issues from maintainers and org members are the ones that get reviewed and merged. This skill finds those, checks if the repo accepts outside contributions, and matches issues to what you actually know. so you don't waste weeks on something that gets rejected or ignored. ## Prerequisites - A GitHub account with `gh` CLI authenticated - A target repo or area of interest (language, framework, domain) ## Process ### 1. Understand the contributor Before searching for anything, understand who's contributing. Ask the user: - "What languages and frameworks are you comfortable with?" - "What's your experience level? (first contribution / a few PRs merged / experienced contributor)" - "Any specific repos or domains you're interested in? (web, CLI tools, data, infra, etc.)" Do NOT skip this. Issue matching without knowing the contributor is useless. ### 2. Check contribution eligibility Before l
- Purpose
- Prerequisites
- Process
- 1. Understand the contributor
- 2. Check contribution eligibility
- 3. Identify maintainers and core contributors
- 4. Search for matching issues
- 5. Filter and rank
- 6. Present recommendations
- 7. Thinking gate: user decides
- 8. Claim the issue
- Related Skills
- Common Rationalizations
- Red Flags
Fetch contribution guidelines
gh api repos/{owner}/{repo}/contents/CONTRIBUTING.md --jq '.content' | base64 -d 2>/dev/null
gh api repos/{owner}/{repo}/contents/.github/CONTRIBUTING.md --jq '.content' | base64 -d 2>/dev/null
gh api repos/{owner}/{repo}/contents/CODE_OF_CONDUCT.md --jq '.content' | base64 -d 2>/dev/null
Check if external PRs actually get merged
gh pr list -R {owner}/{repo} --state merged --limit 20 --json author,mergedAt,authorAssociation | \
jq '[.[] | select(.authorAssociation != "MEMBER" and .authorAssociation != "OWNER")]'
Get repo collaborators and recent committers
gh api repos/{owner}/{repo}/contributors --jq '.[0:10] | .[].login'
Check issue author associationWhat does the oss-find-issue skill do?
Find unclaimed open source issues that match the user's skills and experience level. Searches for issues created by maintainers/org admins, checks contribution eligibility, and ranks by learning value. Use when looking for an issue to contribute to, starting OSS contributions, or finding GSoC-friendly issues.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill oss-find-issue --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.