Skill Gap

Compare fork and upstream skills.json manifests to report adoption gaps.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/aeoncity-demo/myaeon --skill skill-gap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill Gap
Source: https://github.com/aeoncity-demo/myaeon/tree/main/skills/skill-gap
Command: npx skills add https://github.com/aeoncity-demo/myaeon --skill skill-gap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Identifies and reports the skill adoption gaps between a fork and the upstream repository, helping operators understand which new skills are being adopted and which are not.

Core Features & Use Cases

  • Skill Adoption Analysis: Compares the skills present in the upstream repository with those adopted by the fork.
  • Fork Comparison: Identifies which forks are missing the most skills and provides detailed information on the gaps.
  • Alerts: Sends notifications when significant gaps are detected, allowing operators to take action.

Quick Start

Run the Skill Gap skill to get a report on the skill adoption gaps for your fork.

Frequently Asked Questions about Skill Gap

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

FAQPage Schema
How do I track skill adoption gaps across GitHub forks?

To track skill adoption gaps across GitHub forks, compare the skills defined in the upstream repository's manifest with those present in the fork to identify missing skill implementations.

What is GitHub fork analysis for skill adoption?

GitHub fork analysis for skill adoption is the process of comparing an upstream repository's skill manifest against its forks to report which specific skills are missing or unadopted.

Do I need a skills.json manifest to compare upstream repository skills?

Yes, you need a skills.json manifest in the upstream repository to compare upstream repository skills, as this file defines the baseline skills required for accurate fork comparison.

Does fork analysis require GitHub API access and jq?

Yes, fork analysis requires GitHub API access to retrieve repository data and jq to parse the JSON data extracted from the upstream and fork repositories.

Can I get alerts when significant skill gaps are detected in forks?

Yes, you can get alerts when significant skill gaps are detected in forks, allowing operators to take action and ensure new skills are properly adopted across repositories.

How do I identify which forks are missing the most skills?

To identify which forks are missing the most skills, run a skill adoption analysis that compares fork repositories against the upstream baseline and details the specific gaps found.