skill-leaderboard

To track Aeon fork configuration drift, you can aggregate aeon.yml skill settings across forks pushed in the last 30 days. This identifies where forks diverge from upstream defaults by computing enablement, var, model, and schedule override signals.

A skill leaderboard ranks configured forks by aggregating configuration signals and highlighting divergence from upstream defaults. It helps operators prioritize alignment or sunset decisions by identifying promote, match, sunset, and fleet-only signals across the repository fleet.

You can generate a weekly ranking article by running the leaderboard to output a published markdown file at articles/skill-leaderboard-<today>.md. This article logs week-over-week changes and notifies stakeholders of rising, falling, new, or dropped skills.

Yes, you can monitor week-over-week changes automatically by storing historical deltas of aeon.yml skill configurations. The leaderboard logs these configuration changes to reveal trends and new or dropped items for operator decision making.

The best way to decide which Aeon skills to promote or sunset is to compute actionable insights from configuration overrides. Comparing each fork against upstream defaults identifies promote, match, sunset, and fleet-only signals to guide upstream collaboration.