oss-hunter

name	oss-hunter
description	Automatically hunt for high-impact OSS contribution opportunities in trending repositories.
type	skill
created	2026-02-27T00:00:00.000Z
domain	productivity
category	developer-experience
risk	unknown
source	community
tags	["skill","productivity","developer-experience","oss","hunter"]

OSS Hunter 🎯

A precision skill for agents to find, analyze, and strategize for high-impact Open Source contributions. This skill helps you become a top-tier contributor by identifying the most "mergeable" and influential issues in trending repositories.

When to Use

• Use when the user asks to find open source issues to work on.
• Use when searching for "help wanted" or "good first issue" tasks in specific domains like AI or Web3.
• Use to generate a "Contribution Dossier" with ready-to-execute strategies for trending projects.

Quick Start

Ask your agent:

• "Find me some help-wanted issues in trending AI repositories."
• "Hunt for bug fixes in langchain-ai/langchain that are suitable for a quick PR."
• "Generate a contribution dossier for the most recent trending projects on GitHub."

Workflow

When hunting for contributions, the agent follows this multi-stage protocol:

Phase 1: Repository Discovery

Use web_search or gh api to find trending repositories. Focus on:

• Stars > 1000
• Recent activity (pushed within 24 hours)
• Relevant topics (AI, Agentic, Web3, Tooling)

Phase 2: Issue Extraction

Search for specific labels:

• help-wanted
• good-first-issue
• bug
• v1 / roadmap

gh issue list --repo owner/repo --label "help wanted" --limit 10

Phase 3: Feasibility Analysis

Analyze the issue:

1. Reproducibility: Is there a code snippet to reproduce the bug?
2. Impact: How many users does this affect?
3. Mergeability: Check recent PR history. Does the maintainer merge community PRs quickly?
4. Complexity: Can this be solved by an agent with the current tools?

Phase 4: The Dossier

Generate a structured report for the human:

• Project Name & Stars
• Issue Link & Description
• Root Cause Analysis (based on code inspection)
• Proposed Fix Strategy
• (1-10)