Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
akillness avatar

Github Repo Candidate Quality Gate

  • 139 installs
  • 40 repo stars
  • Updated August 4, 2026
  • akillness/oh-my-skills

Score and filter GitHub repo candidates against maintainability, activity, and fit before adopting a dependency or fork base.

About

Applies a repeatable quality gate to GitHub repository candidates—checking signals like maintenance cadence, issue hygiene, test presence, and project fit—so teams reject risky deps early and document why a repo was accepted or ruled out.

  • Structured repo scoring rubric
  • Maintainability and activity signals
  • License and risk checks
  • Shortlist vs reject decisions
  • Consistent candidate comparison

Github Repo Candidate Quality Gate by the numbers

  • 139 all-time installs (skills.sh)
  • Ranked #388 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/akillness/oh-my-skills --skill github-repo-candidate-quality-gate

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs139
repo stars40
Last updatedAugust 4, 2026
Repositoryakillness/oh-my-skills

What it does

Score and filter GitHub repo candidates against maintainability, activity, and fit before adopting a dependency or fork base.

Files

SKILL.mdMarkdownGitHub ↗

GitHub Repo Candidate Quality Gate

Use this skill when broad GitHub search output is too noisy for merge-ready recommendations.

When to use

  • You already ran gh search repos (or equivalent) and need recommendation-grade keeps.
  • You must preserve broad discovery evidence while filtering keeps deterministically.
  • You need lane-level status + degraded-cause reporting for unattended cron review.

Minimum keep metadata

For every kept candidate, capture all fields:

  • full_name
  • url
  • license
  • pushed_at (or updated_at fallback)
  • archived
  • stars
  • one-line fit rationale
  • provenance label

Quality gate order

1. License gate: drop missing/unknown license unless explicit exception rationale. 2. Archive gate: drop archived repos by default. 3. Freshness gate: drop if pushed_at older than 24 months unless exception + risk. 4. Fit gate: drop keyword-only mismatches (low-fit). 5. Signal gate: keep broad discovery evidence, but recommendation-grade keeps require traction (default: stars >= 3) or explicit adoption rationale.

Reporting contract

  • Keep and publish full discovery counts even when keeps are sparse.
  • Emit lane_status: pass|degraded.
  • Emit degraded_causes counts using: license, stale, low-fit, archived, low-signal, no-results.
  • When a lane ends with raw_count == 0 after documented recovery, include no-results explicitly to keep degraded reports deterministic.
  • Include lane health metrics: kept_count, raw_count, median_stars_raw, zero_star_raw.
  • State provenance labels used (direct page retrieval, indexed snippet, etc.).

Rollback-safe operation

  • Never delete raw evidence files.
  • If stricter gates reduce keep counts too far, preserve output but mark lane degraded.
  • Allow exception keeps only when rationale + risk note are explicit.

Example

  • Input: 30 raw hits, many zero-star repos.
  • Output: discovery evidence retained, recommendation keeps filtered by metadata/freshness/signal gates, degraded causes documented for reviewer.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.