fork-skill-gap

Diff parent and fork skills.json manifests to detect missing upstream skills.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill fork-skill-gap-aaronjmars
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fork-skill-gap
Source: https://github.com/aaronjmars/aeon/tree/main/skills/fork-skill-gap
Command: npx skills add https://github.com/aaronjmars/aeon --skill fork-skill-gap-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies skill drift across a fork network by showing which upstream skills are present in the parent but missing from individual forks, preventing silent operational gaps.

Core Features & Use Cases

  • Weekly upstream-to-fork gap auditing: Compares skills.json in a parent repo against each power/active fork’s skills.json to compute missing-slug counts by fork.
  • Fleet-level rollups and prioritization: Produces a verdict based on whether the gap is wide across forks, concentrated in a single laggard fork, or driven by newly shipped upstream skills with low adoption.
  • Operational safety and accuracy: Treats missing/unreadable manifests as unreadable (not zero skills), uses slug-based comparison, and gates notifications on quiet weeks to reduce noise.

Quick Start

Run it with a direction for the fork operator, for example: fork-skill-gap dry-run owner/repo to generate state and the weekly report without sending a notification.

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 which upstream skills are missing from active GitHub forks?

You can detect missing upstream skills by diffing the parent and fork `skills.json` manifests to identify missing slugs. This skill automates that comparison to prevent silent operational gaps across your fork network.

What is the best way to monitor fork adoption and track skill drift across a repository fleet?

The best way to monitor fork adoption is comparing parent and fork manifests to compute missing-slug counts, producing a fleet-level rollup. This identifies whether drift is fleet-wide, concentrated in a laggard, or driven by newly shipped skills.

Does fork-skill-gap require authenticated GitHub API access to run?

Yes, fork-skill-gap requires authenticated GitHub API access via the `gh` tool to read parent and fork manifests. It also supports an optional parent override and a dry-run mode for generating reports without sending notifications.

How do I safely handle unreadable manifests when auditing fork skill gaps?

To safely handle unreadable manifests when auditing fork skill gaps, the system treats them as unreadable rather than counting as zero skills. This ensures accurate slug-based comparison and prevents false positives in your operator digests.

Can I generate a weekly release tracking report without sending operator notifications?

Yes, you can generate a release tracking report without sending notifications by using the dry-run mode. This produces both an articles report and a persistent state file for quiet-week gating to reduce notification noise.