github-repo-signals

Name: github-repo-signals
Availability: InStock
Author: Gooseworks

Aggregate and score GitHub engagement signals to identify cross-repo leads.

9|5|Updated Apr 3, 2026

Search Tags:#github #signals #multi-repo #lead-generation #csv-export #profile-enrichment

Ready to run

npx skills add https://github.com/gooseworks-ai/gooseworks-skills --skill github-repo-signals

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-repo-signals
Source: https://github.com/gooseworks-ai/gooseworks-skills/tree/main/skills/packs/lead-gen-devtools/github-repo-signals
Command: npx skills add https://github.com/gooseworks-ai/gooseworks-skills --skill github-repo-signals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

Identify high-potential leads on GitHub by aggregating and scoring signals across multiple repositories. This tool surfaces deduplicated, cross-repo prospects for outreach based on engagement across stars, forks, issues, PRs, comments, and contributions.

Core Features & Use Cases

Cross-repo lead extraction: aggregates signals from multiple GitHub repositories to surface top prospects.
Score-based ranking: computes a weighted score per user based on interaction types (star, fork, issue opener, PR author, commenter, watcher, contributor).
Output-ready data: exports two CSV files with user profiles and per-repo interactions for outreach across multiple teams or campaigns.
Use Case: marketing teams identifying engineers active across competing repos to engage with targeted messaging.

Quick Start

Analyze your target repos and generate a ranked leads CSV with profiles and per-repo signals.

Frequently Asked Questions about github-repo-signals

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate leads from GitHub repository activity?▼

To generate leads from GitHub repository activity, analyze and score interactions like stars, forks, PRs, and issues across multiple repositories. Deduplicate users to surface ranked prospects for targeted outbound campaigns.

What GitHub signals are most useful for identifying developer leads?▼

Useful GitHub signals for identifying developer leads include stars, forks, issue creation, PR authorship, comments, watchers, and contributions. Aggregating these interactions across competing repos surfaces high-potential prospects for marketing outreach.

Can I export GitHub contributor profiles to a CSV file for outreach?▼

Yes, you can export GitHub contributor profiles to CSV files for outreach. The process outputs two CSV files containing unified user profiles and per-repo interactions, providing output-ready data for downstream targeting and campaigns.

How do I rank developers across multiple GitHub repositories?▼

Rank developers across multiple GitHub repositories by computing a weighted score per user based on interaction types. Cross-repo lead extraction aggregates these signals to deduplicate profiles and surface top prospects for engagement.

Does this lead generation approach require Python dependencies to run?▼

Yes, running this GitHub lead generation approach requires the Python dependency pyyaml. You need this environment setup to execute the scripts that analyze repository activity and output the ranked leads CSV files.