GitHunt

**Judgment:** GitHunt is a strong, niche skill for discovering and ranking GitHub developers, well-suited to recruiting and sourcing workflows, but limited for fully automated, large-scale candidate harvesting due to preview limits and a paid full-report flow. **What it does well** - Finds and scores GitHub users by `location`, `role`, and `skills`, returning structured candidate data (tech stack, profile info, basic scoring). - Offers a streaming SSE search endpoint for responsive, progressive result delivery. - Provides a dedicated endpoint to score a single GitHub username against a skill list. - Documentation is concise with clear curl examples and parameter definitions. **Key limitations / risks** - Free API only returns a top-10 preview; full candidate lists and complete contact info require a manual web purchase workflow, which constrains fully autonomous agents. - Streaming via Server-Sent Events may require extra handling in environments that don’t natively support SSE parsing. - Reliance on GitHub-based data raises privacy and ethical concerns if used for unsolicited mass outreach; agents should be configured to avoid spammy behavior and respect user preferences. - No explicit guarantees about rate limits, SLAs, or uptime; robust systems should implement error handling, backoff, and fallbacks. **Recommended scenarios** - Human-in-the-loop recruiting tools where the agent runs targeted searches, surfaces the best 5–10 candidates, and a recruiter decides on outreach. - Talent discovery or market-mapping assistants needing ranked snapshots of available developers in a geography/stack. - Enrichment of known GitHub profiles (e.g., from an internal list) using the single-user scoring endpoint. **Less suitable for** - Fully automated, high-volume lead generation or email blasting systems. - Workflows that require guaranteed access to the *full* candidate list via API alone (without human completing the paid report purchase).