# GitHub Candidate Scorer (`fuze/github-candidate-scorer`) Actor

Score GitHub developers against a job description by reading their real repos and code — with evidence, strengths, gaps and contact. · More no-code data tools → datatools-hub.vercel.app

- **URL**: https://apify.com/fuze/github-candidate-scorer.md
- **Developed by:** [Fredrik Hansson](https://apify.com/fuze) (community)
- **Categories:** AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $154.00 / 1,000 candidate scoreds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## GitHub Candidate Scorer

**Score developers against a job by reading their ACTUAL code — not just keywords on a profile.**

Give it a job description and either a list of GitHub usernames or a search query. For each developer, it reads their real profile, repositories, languages, topics and README content, then scores how well they fit the role — with **evidence** (which projects and skills justify the score), strengths, gaps, an estimated seniority, and recovered contact details.

This is what a great technical screener does — read the real work — done at scale. Uses the **open GitHub API only** (no scraping, no legal grey area).

![GitHub Candidate Scorer — input and sample output](https://datatools-hub.vercel.app/actor-shots/github-candidate-scorer.png)

### Quick start

1. **Fill in the input** — set the fields in the input tab (prefilled with a working example).
2. **Click Start** — the Actor runs and writes one record per item to the dataset.
3. **Get your data** — export to **JSON, CSV or Excel**, or pull it via the API.

```json
// input
{ "jobDescription": "Senior Rust engineer, systems/CLI, open-source track record", "usernames": ["someuser", "another"] }
```

```json
// per-candidate output
{
  "username": "someuser", "name": "Jane Dev", "matchScore": 88, "seniority": "senior",
  "topLanguages": ["Rust", "Go", "TypeScript"],
  "matchReason": "Strong systems background: authored a popular Rust CLI and contributes to async runtimes...",
  "strengths": ["2.5k-star Rust CLI", "Active OSS maintainer", "Systems-level projects"],
  "gaps": ["No obvious distributed-systems work"],
  "evidence": ["repo: fast-grep (Rust, ★2.5k)", "repo: tokio-utils contributions"],
  "location": "Berlin, DE", "email": "jane@example.com", "profileUrl": "https://github.com/someuser"
}
```

### Use cases

- **Technical sourcing / recruiting** — rank a shortlist (or a search) of developers against a specific role, with evidence.
- **Hiring triage** — turn a pile of GitHub profiles into a ranked, explained candidate list.
- **Agent tool** — via the Apify MCP server, an agent can score a developer against a role on demand.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `jobDescription` | `string` | — (required) | The role to score against. |
| `usernames` | `string[]` | — | Specific GitHub usernames to score. |
| `searchQuery` | `string` | — | GitHub user-search query to find candidates (used if no usernames). |
| `maxResults` | `integer` | `25` | Max candidates to score (one charge each). |
| `model` | `string` | `gpt-4o-mini` | OpenAI model. |

### Output

One record per candidate: `matchScore`, `seniority`, `matchReason`, `strengths[]`, `gaps[]`, `evidence[]`, `topLanguages[]`, `name`, `location`, `email`, `blog`, `followers`, `publicRepos`, `profileUrl`. Top candidates in the run `SUMMARY`.

### Pricing

Pay-per-event: one **`candidate-scored`** event per developer scored.

### Environment variables

| Variable | Required | Purpose |
|---|---|---|
| `OPENAI_API_KEY` | **Yes** | Powers the scoring. |
| `GITHUB_TOKEN` | Recommended | Free GitHub personal access token — raises the GitHub API limit from 60 to 5,000 requests/hour. Without it, only a few candidates per run. |

### Notes

- Reads profile + repositories + top READMEs (real "what did they build" signal). Forks and archived repos are discounted.
- Scoring is evidence-based; provide a detailed job description for best results.

### License

ISC.

### Related actors

- [Nordic Tender Matcher (AI)](https://apify.com/fuze/nordic-tender-matcher) — AI agent that scores Norwegian, Finnish and Swedish public tenders against your company
- [EU & Nordic Grant Finder (AI-matched)](https://apify.com/fuze/eu-grant-finder) — Find open EU + Nordic public-funding calls matched to your company with AI — eligibility
- [AI SEO + AEO/GEO Site Auditor — Crawl & Auto-Fix](https://apify.com/fuze/ai-seo-site-auditor) — Crawl a whole site and get an AI-prioritized technical + content + AEO/GEO audit with

# Actor input Schema

## `jobDescription` (type: `string`):

The role to score candidates against — responsibilities, required skills, stack, seniority.

## `usernames` (type: `array`):

Specific GitHub usernames to score (one per line).

## `searchQuery` (type: `string`):

Find candidates via GitHub user search, e.g. 'language:typescript location:berlin followers:>100'. Used if no usernames are given.

## `maxResults` (type: `integer`):

Max developers to score. One pay-per-event charge per candidate scored.

## `model` (type: `string`):

Override the model (default gpt-4o-mini).

## Actor input object example

```json
{
  "jobDescription": "Senior Backend Engineer. Must have deep TypeScript/Node.js experience, built and scaled production APIs, and ideally open-source contributions. Bonus: distributed systems, Postgres.",
  "maxResults": 25
}
```

# Actor output Schema

## `candidates` (type: `string`):

Scored candidates in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "jobDescription": "Senior Backend Engineer. Must have deep TypeScript/Node.js experience, built and scaled production APIs, and ideally open-source contributions. Bonus: distributed systems, Postgres."
};

// Run the Actor and wait for it to finish
const run = await client.actor("fuze/github-candidate-scorer").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "jobDescription": "Senior Backend Engineer. Must have deep TypeScript/Node.js experience, built and scaled production APIs, and ideally open-source contributions. Bonus: distributed systems, Postgres." }

# Run the Actor and wait for it to finish
run = client.actor("fuze/github-candidate-scorer").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "jobDescription": "Senior Backend Engineer. Must have deep TypeScript/Node.js experience, built and scaled production APIs, and ideally open-source contributions. Bonus: distributed systems, Postgres."
}' |
apify call fuze/github-candidate-scorer --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fuze/github-candidate-scorer"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/GM2Xn2wsomt83PDxC/builds/gKlZmtO1uIOSRCFAd/openapi.json