fork-skill-digest

Compute weekly divergence digests for aeon fork fleets from aeon.yml settings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It identifies where configured forks of aeon systematically diverge from upstream skill defaults, so operators can correct noisy or incorrect defaults without manually comparing repositories.

Core Features & Use Cases

  • Weekly divergence digest across forks: Compares forked aeon.yml settings (enabled, var, model, schedule) against locally computed upstream defaults.
  • Default-flip recommendations: Surfaces skills with majority enable-upward or disable-downward divergence for upstream maintenance.
  • Consensus hotspots: Detects fleet-wide common alternative model, frequently overridden var, and shared schedule changes.
  • Fork-only discovery: Lists skills that exist in forks but not in upstream for potential upstreaming review.
  • Week-over-week change tracking: Uses memory/topics/fork-skill-digest-state.json to highlight new flips, strengthened/faded patterns, and new heavy customizers.

Quick Start

Run fork-skill-digest with optional var set to a target repo like owner/aeon to generate the weekly divergence digest article and notification if thresholds are met.

Frequently Asked Questions about fork-skill-digest

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

FAQPage Schema
How do I detect configuration drift in GitHub fork fleets?

Compute a weekly divergence digest to detect configuration drift in GitHub fork fleets by comparing forked aeon.yml settings against upstream defaults. It scans active forks and aggregates differences in enabled state, var overrides, model selection, and schedules into flip, consensus, and emerging buckets.

What is YAML divergence analysis for upstream skill defaults?

YAML divergence analysis for upstream skill defaults identifies where configured forks systematically disagree with upstream aeon.yml settings. It surfaces default-flip recommendations, consensus hotspots for frequently overridden variables, and fork-only skills missing from upstream.

How do I track week-over-week changes in forked repository configurations?

Persist divergence data to a JSON state file to track week-over-week changes in forked repository configurations. This approach highlights new default flips, strengthened or faded fleet patterns, and newly active heavy customizers across the scanned GitHub forks.

Can I identify skills in forks that are missing from the upstream repository?

Yes, you can identify skills in forks that are missing from the upstream repository by enumerating fork file trees and analyzing their aeon.yml files. The divergence digest lists these fork-only skills for potential upstreaming review.

What do I need to resolve before scanning active GitHub forks for var overrides?

Resolve a target repository like owner/aeon and snapshot upstream defaults from a local aeon.yml file before scanning active GitHub forks for var overrides. The skill then fetches fork configurations when present to begin the analysis.

What are the limitations of automated fork analysis for aeon.yml files?

A key limitation of automated fork analysis for aeon.yml files is that it strictly analyzes forks where the configuration file exists and diverges from upstream. It requires resolving a specific target repository and does not process forks lacking the aeon.yml file.