GitHub via Scavio

Pull GitHub profiles, repositories, READMEs, releases, issues and comments, run GitHub search across five verticals, and get composite intelligence: a full repo dossier, a user's public-activity velocity, reaction-ranked top issues, and public commit emails. All endpoints return structured JSON.

When to trigger

Use this skill when the user asks to:

• Look up a GitHub user's profile, or a repository's stars, forks, issues, license, topics and metadata
• List a user's repositories, or a repository's releases with assets and download counts
• Read a repository's README, its issues (PRs filtered out by default), or a single issue / PR and its comments
• Search repositories, users, issues, code or commits
• Rank a repository's most-reacted open issues, or build a full repo dossier (metadata, README excerpt, releases, top issues, language breakdown, top contributors, weekly activity)
• Measure a user's public-activity velocity, or resolve a username to public commit email(s)

Setup

Get a free API key at scavio.dev (50 free credits to get started, no card required):

export SCAVIO_API_KEY=sk_live_your_key

Every request is a POST with a JSON body and:

Authorization: Bearer $SCAVIO_API_KEY

Endpoints

Base URL: https://api.scavio.dev. Most endpoints cost 1 credit; the composite/intelligence endpoints cost more (see the table).

Parameters

handle = username, @handle, or a github.com/<user> URL. url = a github.com/<owner>/<repo> URL or a bare <owner>/<repo>. per_page = 1-100, page = 1-based.

Examples

import requests

BASE = "https://api.scavio.dev"
# Your key from https://scavio.dev. Load it from your environment or secret
# store in real code - keep it out of source control.
API_KEY = "sk_your_key_here"
HEADERS = {"Authorization": f"Bearer {API_KEY}"}

# 1. A repo's core metadata (1 credit)
repo = requests.post(f"{BASE}/api/v1/github/repo", headers=HEADERS,
    json={"url": "facebook/react"}).json()

# 2. Its most-reacted open issues (5 credits)
top = requests.post(f"{BASE}/api/v1/github/repo/top-issues", headers=HEADERS,
    json={"url": "facebook/react", "sort": "reactions", "per_page": 10}).json()

# 3. Search the top ML repositories by stars (1 credit)
search = requests.post(f"{BASE}/api/v1/github/search", headers=HEADERS,
    json={"query": "machine learning", "type": "repositories",
          "sort": "stars", "order": "desc", "per_page": 20}).json()

# 4. A full repo dossier (5 credits) and a user's 90-day velocity (10 credits)
dossier = requests.post(f"{BASE}/api/v1/github/repo/dossier", headers=HEADERS,
    json={"url": "facebook/react"}).json()
velocity = requests.post(f"{BASE}/api/v1/github/user/profile-velocity", headers=HEADERS,
    json={"handle": "torvalds", "depth": "default"}).json()

curl:

curl -s https://api.scavio.dev/api/v1/github/profile \
  -H "Authorization: Bearer $SCAVIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"handle":"torvalds"}'

Response shape

Every response uses the envelope { data, response_time, credits_used, credits_remaining }. Paginated endpoints put their rows in data.items; search also returns the vertical's total. credits_used on each response tells you exactly what the call cost.

Guardrails

• Costs are not uniform: profile-velocity is 10 credits, top-issues and dossier are 5, user/email is 2, everything else is 1. Check the table before a loop.
• A 400 (bad input), 404 (unknown user/repo/issue) and 429 (upstream rate limit) all cost nothing - only a fully-served 200 is billed.
• repo/issues filters pull requests out by default; pass type: "all" or type: "pr" to include them.
• profile-velocity and the public feed it reads are capped at 300 events / 90 days - it is a recent-activity signal, not a full history.
• user/email is public-commit OSINT and flags @users.noreply.github.com addresses. It is personal data - use it responsibly and do not build profiles of individuals.
• Never fabricate stars, issue text, contributor names or emails. Only return what the API returned.

Failure handling

• 400 means an invalid or missing parameter. Fix and retry.
• 401 means the API key is invalid or missing. Check SCAVIO_API_KEY.
• 404 means the user, repo or issue does not exist.
• 429 means rate or usage limit exceeded. Wait before retrying. See rate limits.
• 502 means the source is temporarily unavailable - wait a few seconds and retry.
• If SCAVIO_API_KEY is not set, prompt the user to export it before continuing.