oss-hunter
Automatically hunt for high-impact OSS contribution opportunities in trending repositories.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- oss-hunter
- risk
- safe
- source
- https://github.com/jackjin1997/ClawForge
- date_added
- 2026-02-27
- description
- Automatically hunt for high-impact OSS contribution opportunities in trending repositories.
02 资源文件 1
- 脚本bin/hunter.py1.9 KB
03 SKILL.md 正文
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-wantedgood-first-issuebugv1/roadmap
gh issue list --repo owner/repo --label "help wanted" --limit 10
Phase 3: Feasibility Analysis
Analyze the issue:
- Reproducibility: Is there a code snippet to reproduce the bug?
- Impact: How many users does this affect?
- Mergeability: Check recent PR history. Does the maintainer merge community PRs quickly?
- 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
ghCLI orweb_searchtools. - 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.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.