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.