fork-skill-gap

Comparing upstream skills across GitHub forks involves evaluating each fork's skills.json against the parent repository's skills.json to identify unadopted skills. This calculation surfaces adoption drift, allowing operators to quantify per-fork gaps and prioritize upgrade efforts.

A fork skill gap represents missing upstream skills in a forked repository's skills.json compared to the parent manifest. It affects automation by creating adoption drift, which hinders fleet-wide governance and requires structured reporting to prioritize upgrades.

Generating a weekly digest for unadopted upstream skills requires running a scheduled workflow that compares fork manifests against the parent repository. This produces a readable report summarizing fleet-wide gaps, per-fork gaps, and top unadopted slugs.

Fork skill gap reporting handles unreadable manifests through robust error handling. It processes POWER and ACTIVE forks, calculates per-fork gaps, and accounts for manifest errors to produce a reliable fleet-wide rollup verdict for automation.

You can use this approach for fleet-wide governance and audits because it produces a structured state file and readable reports. These outputs track per-fork evaluation metrics and fleet-wide rollups suitable for operator decision-making.

Quantifying missing upstream skills across active forks requires comparing each fork's skills.json against the parent repository's manifest. This generates per-fork gap calculations and a fleet-wide rollup to expose adoption drift.