Track how your forks diverge

Fork Fleet is an aeon skill: Fork divergence monitor - tracks where the fleet's active forks diverge in CODE (unique commits, new/modified skills) and CONFIG (enable/var/model/schedule vs upstream), gated on real change. Like every aeon skill it is one SKILL.md prompt file that runs unattended on your own GitHub Actions, on a schedule or when you trigger it, and sends what it finds to Telegram, Discord, Slack or email.

This is the fleet's divergence monitor. It answers two questions the popularity/liveness skills don't:

1. Code divergence - which active forks are building real work (unique commits, new/modified skills) that's worth pulling back upstream?
2. Config divergence - where does the configured fleet systematically disagree with upstream's enabled / var / model / schedule defaults, so the operator can flip a default the fleet has already voted on?

skill-gap ranks what's popular (top 15 by enabled count). This skill's code branch surfaces per-fork unique work; its config branch surfaces where operators disagree with defaults. If 6 of 8 configured forks enable a skill upstream defaults off, upstream is shipping the wrong default; if 5 of 8 disable a skill upstream defaults on, that skill is noise. Both are peer-learning signals.

Every aeon skill takes one optional text input, var, set in aeon.yml or typed in when you run it by hand. It picks the target or the mode for that run.

Divergence scope selector; space-separated tokens, order-independent, all optional:

• scope (code | config | both, default both) - which divergence dimension to run.
• repo=owner/name - override the parent repo whose forks are scanned (else auto-resolved).
• fork=owner/name - drill into a single fork (forces code scope; config math needs a fleet).

Empty ⇒ both dimensions over the auto-resolved parent. Examples: ` (both, all forks) · code · config · config repo=octo/aeon · fork=alice/aeon`.

No extra API keys or MCP servers. It runs on the model you connected to aeon (a Claude subscription token, an API key, or another login).

Easiest: open Aeon Connect, sign in with GitHub and turn on Fork Fleet. No clone, no terminal. To add it to an existing aeon repo from a shell, run:

Then switch it on in aeon.yml (the default schedule is filled in):

skills:
  fork-fleet: { enabled: true, schedule: "0 10 * * 1", var: "" }

New to aeon? Read the docs for how skills, schedules and memory fit together, or browse all skills.