CtrlK
BlogDocsLog inGet started
Tessl Logo

oss-hunter

Automatically hunt for high-impact OSS contribution opportunities in trending repositories.

49

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/oss-hunter/SKILL.md

The canonical home for this skill is oss-hunter in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

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
  • Confidence Score (1-10)

Limitations

  • Accuracy depends on the availability of gh CLI or web_search tools.
  • Analysis is limited by context window when reading very large repositories.
  • Cannot guarantee PR acceptance (maintainer discretion).

Contributing to the Matrix

Build a better hunter by adding new heuristics to Phase 3. Submit your improvements to the ClawForge.

Powered by OpenClaw & ClawForge.

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Last updated
First committed

Canonical home

administrakt0r/AI-Agents-Safe-Coding-Skills
In sync

since Aug 19, 2026

Also appears in

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.