fork-skill-gap

Audits active GitHub forks for upstream skills missing from each fork's skills.json manifest.

Updated May 25, 2026
One-click install
npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill fork-skill-gap-cbowcrptex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fork-skill-gap
Source: https://github.com/Cbowcrptex/CBOWCRYPTEX/tree/main/skills/fork-skill-gap
Command: npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill fork-skill-gap-cbowcrptex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Forks of an agent repository silently drift behind upstream as new skills ship, and operators have no visibility into which skills their fork never adopted. This Skill produces a weekly digest that surfaces per-fork skill gaps and fleet-wide adoption patterns. ## Core Features & Use Cases - Per-fork gap analysis: Compares each active fork's skills.json against the upstream manifest and reports missing slugs with category rollups. - Fleet-level rollup: Ranks forks by gap size, identifies universally unadopted upstream skills, and picks a one-line verdict (WIDE_GAP, BIG_FORK_GAP, NEW_UPSTREAM_UNCLAIMED, STEADY, COLD START). - Cohort reuse with fallback: Reuses fork-cohort state when fresh, or builds its own POWER + ACTIVE fork list via the GitHub API when it is not. - Use Case: An upstream maintainer runs the weekly digest and sees that three forks are each missing 20+ skills and that a newly shipped skill has zero fleet adoption, prompting a re-examination of that skill. ## Quick Start Run the fork-skill-gap skill to audit active forks against the upstream skills.json and write the weekly gap report.

Frequently Asked Questions about fork-skill-gap

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

FAQPage Schema
How do I find which upstream skills my GitHub fork is missing?▼

Run this skill to compare your fork's skills.json against the parent repository's manifest using slug-level diffing. It produces a per-fork table of missing skills with category rollups and writes a dated article report.

How does the skill decide which forks to audit?▼

It targets POWER and ACTIVE forks, meaning forks with at least one workflow run in the last 7 days. It reuses fork-cohort state when that state is under 8 days old, otherwise it builds the list live via the GitHub forks API.

What happens if a fork has no skills.json file?▼

The fork is marked unreadable rather than treated as having zero skills, so renamed or missing manifests never inflate the gap count. Unreadable forks are listed separately in the report with the failure reason.

Does the skill send notifications every week?▼

No. Notifications are skipped on dry-run mode, quiet weeks where all forks are within 5 skills of upstream, and error states like no active forks. State and the article are still written even when notify is suppressed.

Can I run the audit against a different parent repository?▼

Yes. Pass an owner/repo token in the var parameter to override the resolved parent, optionally combined with dry-run. Unknown tokens cause the run to exit with a bad-var status and no notification.

What are the scale limits of the fork audit?▼

Processing is capped at 80 forks per run, sorted by stargazers when trimming. Per-fork state stores at most 50 missing slugs, and stale fork entries are evicted after 35 days.