fork-skill-gap

To identify missing skills across GitHub forks, you can run an automated gap analysis that compares upstream skills.json files with each active fork to quantify drift. This generates audit-ready reports and weekly digests ranking forks by missing skill slugs.

Fork skill drift occurs when active GitHub forks lack skills present in the upstream repository. Gap analysis tracks this by fetching skills.json using gh and jq, computing missing slugs per fork, and emitting state files with summary metrics to monitor drift over time.

Yes, you need both gh and jq installed to analyze upstream fork gaps. The skill uses gh to fetch skills.json from GitHub-hosted forks and jq to parse the data and compute missing slugs per fork for the final audit-ready reports.

You generate weekly digests for missing skills by running the skill to compare upstream skills with fork implementations. It automatically writes a state file, an article, and summary metrics tracking which forks are missing specific skill slugs for that week.

Yes, you can audit fork skill gaps across an entire GitHub fleet at once. The skill performs fleet-wide gap analysis by comparing upstream skills with each active fork, ranking them by missing skills to prioritize outreach and generate audit-ready reports.

The best way to report missing slugs per fork is to use automated gap analysis that generates articles and summary metrics. It ranks forks by missing skills, producing audit-ready artifacts and state files suitable for stakeholder communication and outreach prioritization.