Extract and score leads from GitHub repositories by analyzing stars, forks, issues, PRs, comments, and contributions. Produces unified multi-repo CSV with deduplicated user profiles. No paid API credits required.
SkillScore77Maintained
Automatic
◆Sales & GTM pack
Last verified 8/16/2026
What it changes
Passed 15 of 20 test cases with the skill, and 7 of 20 without it.
Without skill36%
With skill77%
Checks it passed that the model alone missed
Assigns 4 points to contributors.
Assigns 5 points to issue openers.
Assigns 3 points to issue commenters.
and 9 more in the full report
9 fixed8 passed either way5 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+73%
Agent turns
0%
Response time
-56%
Model gemini-3.6-flashMeasured 8/16/2026v117 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
We have two leads: User A scored 18 points across 1 repository. User B scored 12 points across 2 repositories. Which user surfaces first in the primary export ranking?
What was checked, without and with the skill
Checked
Without skill
With skill
Ranks multi-repo interaction higher than total score across a single repository.
Missed
Passed
case-07 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md213 lines8 filesincludes scripts
GitHub Repository Signals
Extract high-intent leads from one or more GitHub repositories by analyzing every type of user interaction. This skill uses only free GitHub API data — no enrichment credits are spent.
When to Use
User wants to find leads from open-source GitHub repositories
User wants to identify people who interact with competitor or category repos
User wants cross-repo interaction analysis to find high-intent prospects
User asks for GitHub-based lead generation without paid enrichment
User says their ICP, target audience, or buyers are developers, engineers, or technical people who are active on GitHub
User describes prospects who use open-source tools, contribute to open source, or build with specific technologies — and those technologies have public GitHub repos
User wants to find leads in a technical space (e.g., "real-time communication", "AI agents", "infrastructure") where the community congregates around GitHub repositories
Note: If the user describes their ICP as GitHub-active but hasn't identified specific repositories yet, this skill still applies. In that case, ask the user which repositories their ICP is likely to interact with, or help them identify relevant repos based on the technology/space they describe.
Prerequisites
gh CLI authenticated (gh auth status to verify)
Python 3.9+ with PyYAML installed
Working directory: the project root containing this skill
Inputs to Collect from User
Before running, ask the user for:
Repositories (required): One or more GitHub repository URLs or owner/repo strings
User limit (required): How many top users to include in the output. Explain that more users = longer runtime due to GitHub profile fetching (~5,000 profiles/hour). Suggest 500 as a good starting point for testing.