repo_scanner

Scan GitHub repositories and scaffold OSS Agent Lab specialists when scores exceed thresholds.

2|Updated Mar 17, 2026

Search Tags:#automation #workflow #github #scaffolding #discovery #repo-analysis #specialist-generation

Ready to run

npx skills add https://github.com/jeremylongshore/oss-agent-lab --skill repo-scanner-jeremylongshore

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo_scanner
Source: https://github.com/jeremylongshore/oss-agent-lab/tree/main/agents/specialists/repo_scanner
Command: npx skills add https://github.com/jeremylongshore/oss-agent-lab --skill repo-scanner-jeremylongshore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically identifies promising GitHub repositories and wraps them as new specialists, reducing manual effort to scale capabilities.

Core Features & Use Cases

Auto-discovers candidate repos and infers possible capabilities.
Evaluates repos with a scoring pipeline and decides next steps (auto_scaffold, evaluate, watch, skip).
Scaffolds a production-ready specialist skeleton when the score meets the threshold.

Quick Start

Run the Repo Scanner on a GitHub repo slug to automatically evaluate and scaffold a new specialist when eligible.

Frequently Asked Questions about repo_scanner

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

FAQPage Schema

How do I automate GitHub repository discovery for wrapping as new specialists?▼

The scanner evaluates candidate GitHub repositories by deriving deterministic signals directly from the repo slug, applying a scoring pipeline to assess suitability, and deciding next steps like auto-scaffold, evaluate, watch, or skip.

What's the best way to scaffold a production-ready specialist skeleton from a GitHub repo?▼

Scaffolding a production-ready specialist skeleton requires running the evaluate_score stage on a repo slug; when the score crosses the threshold, the pipeline automatically generates the specialist skeleton and multiple structured output formats.

Does repo scanning require dependencies or external components to function?▼

Repo scanning requires no external dependencies or components, relying entirely on deriving deterministic signals from the provided GitHub repo slug to execute the scan, evaluate, and scaffold pipeline.

How does the repo evaluation pipeline decide whether to scaffold or skip a repository?▼

The repo evaluation pipeline decides whether to scaffold or skip by applying a scoring stage to the derived signals, triggering auto-scaffolding only when the score crosses a predefined threshold.

What output formats are generated when a candidate repository is scaffolded as a specialist?▼

Scaffolding a candidate repository produces a structured result and multiple output formats designed specifically for downstream integration within the OSS Agent Lab specialist workflow.