fork-skill-gap

Compare fork skills.json files against the parent manifest to quantify upstream gaps.

Updated Jun 2, 2026

Search Tags:#automation #github #reporting #upstream #fork #skill-gap

Ready to run

npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill fork-skill-gap-atrium-hermes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fork-skill-gap
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/fork-skill-gap
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill fork-skill-gap-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and surfaces missing upstream skills across forks, enabling operators to measure adoption drift and prioritize upgrade efforts.

Core Features & Use Cases

Compare each fork's skills.json against the parent manifest to surface unadopted upstream skills.
Generate a weekly digest that summarizes fleet-wide gaps, per-fork gaps, and top unadopted slugs for upstream visibility.
Produce a structured state file and readable reports to support governance, audits, and operator decision-making.

Quick Start

Run the fork-skill-gap workflow weekly to generate the digest and publish the article.

Frequently Asked Questions about fork-skill-gap

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

FAQPage Schema

How do I compare upstream skills across GitHub forks?▼

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.

What is a fork skill gap and how does it affect repository automation?▼

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.

How do I generate a weekly digest for unadopted upstream skills?▼

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.

Does fork skill gap reporting handle unreadable manifests and errors?▼

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.

Can I use this approach for fleet-wide governance and audits?▼

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.

What's the best way to quantify missing upstream skills across active forks?▼

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.