fork-skill-gap

Diff upstream skills.json against GitHub fork manifests to detect missing skill slugs.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill fork-skill-gap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fork-skill-gap
Source: https://github.com/anajuliabit/aeon/tree/main/skills/fork-skill-gap
Command: npx skills add https://github.com/anajuliabit/aeon --skill fork-skill-gap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill identifies which upstream skills a GitHub fork has not yet enabled, preventing silent “skill drift” where forks fall behind without operators noticing.

Core Features & Use Cases

  • Weekly cross-fork adoption digest: Compares upstream skills.json against each POWER+ACTIVE fork’s skills.json to compute missing skill slugs and counts.
  • Actionable fleet rollups: Produces a verdict that highlights wide gaps across the fleet, the worst single fork lagging behind, and cases where newly shipped upstream skills have no adoption.
  • Operational resilience: Uses the cached cohort state when available, falls back to GitHub API otherwise, and marks forks with missing/blocked skills.json as unreadable (avoids false “zero skill” conclusions).

Quick Start

Run the fork-skill-gap skill with your desired mode, for example: fork-skill-gap to generate the weekly adoption gap report and notify based on the verdict.

Frequently Asked Questions about fork-skill-gap

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

FAQPage Schema
How do I detect upstream skill drift across GitHub forks?▼

Detect upstream skill drift by diffing the upstream skills.json manifest against each active GitHub fork's skills.json to compute missing slugs and highlight adoption gaps. This prevents silent configuration divergence where forks fall behind upstream updates unnoticed.

What is the best way to monitor missing skills across a GitHub fork fleet?▼

Monitor missing skills across a fork fleet by applying scheduled cross-fork adoption diffing to generate weekly operator reports. This produces actionable rollups highlighting wide adoption gaps, the worst lagging fork, and newly shipped upstream skills with zero adoption.

How does diffing manifests handle GitHub forks with blocked or missing skills.json?▼

Diffing manifests handles blocked or missing skills.json by marking those GitHub forks as unreadable. This avoids false zero-skill conclusions during adoption gap monitoring and ensures fleet rollups reflect actual configuration drift accurately.

Can I run fork skill gap monitoring in dry-run mode without sending notifications?▼

You can run fork skill gap monitoring in dry-run mode to skip notifications while still writing an article and persistent state. This allows you to validate missing skill slugs and category rollups before alerting operators.

Does GitHub fork monitoring require API reads for both upstream and fork manifests?▼

GitHub fork monitoring requires API reads for the upstream skills.json and each fork's skills.json. It optionally uses cached cohort-state acceleration to speed up manifest diffing and applies quiet-week gating to suppress unnecessary reporting noise.