github-repo-signals
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.
npx skills add gooseworks-ai/goose-skills --skill github-repo-signals --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 hel
- When to Use
- Prerequisites
- Inputs to Collect from User
- Execution Steps
- Step 1: Verify Environment
- Step 2: Run the Tool
- Step 3: Review Output
- Phase 3: Analyze & Recommend
- Step 5: Collect Company Context
- Step 6: Analyze the Data
- Step 7: Recommend Next Steps
- Step 8: Ask for Go-Ahead
- Output Interpretation Reference
- Rate Limits & Runtime Estimates
gh auth status
python3 ${CLAUDE_SKILL_DIR}/scripts/gh_repo_signals.py \What does the github-repo-signals skill do?
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.
How do I install it?
Run `npx skills add gooseworks-ai/goose-skills --skill github-repo-signals --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gooseworks-ai/goose-skills, a repository with 1,091 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.