skill-leaderboard

Generate weekly AEON skill adoption rankings across configured GitHub forks.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill skill-leaderboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-leaderboard
Source: https://github.com/anajuliabit/aeon/tree/main/skills/skill-leaderboard
Command: npx skills add https://github.com/anajuliabit/aeon --skill skill-leaderboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns noisy skill usage across forks into actionable weekly insight, so maintainers learn which skills are genuinely adopted versus just inherited defaults.

Core Features & Use Cases

  • Configured-fleet leaderboard: Ranks skills by adoption only among forks whose aeon.yml meaningfully diverges from upstream defaults, avoiding “heartbeat tautology.”
  • Evidence-based recommendations: Produces Promote, Match, Sunset (review), and Fleet-only categories based on enabled/override patterns across the configured fleet.
  • Operational reporting: Fetches active forks, inspects per-fork aeon.yml overrides, tracks week-over-week deltas, and writes a dated article plus a notification when meaningful.

Quick Start

Run the leaderboard scan for your target repo by setting var to the GitHub owner/repo string (or leave it empty to read the first entry from memory/watched-repos.md).

Frequently Asked Questions about skill-leaderboard

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

FAQPage Schema
How do I track skill adoption across GitHub forks to see which configurations are actively used?

Track skill adoption across GitHub forks by enumerating active forks and inspecting each fork's aeon.yml overrides against upstream defaults. This generates a weekly ranked leaderboard of genuinely adopted skills, filtering out inherited heartbeat configurations.

What is fleet monitoring for autonomous agents and how does week-over-week state comparison work?

Fleet monitoring for autonomous agents tracks recurring behavior changes across configured repositories using week-over-week state comparison. It reads memory state files to compare enabled states, model overrides, var usage, and scheduling changes to identify emergent preferences.

How do I generate a ranked weekly report of enabled skills and model overrides for a target repository?

Generate a ranked weekly report by setting the target GitHub owner/repo string or reading from watched-repos memory, then applying configured-tier classification to active forks. The scan outputs a dated article and notification gated by a minimum configured-fork denominator.

Does the skill leaderboard require a minimum number of configured forks before generating adoption reports?

Yes, the skill leaderboard requires a minimum configured-fork denominator before generating article or notification outputs. This threshold ensures reporting only occurs when enough forks meaningfully diverge from upstream defaults to provide statistically useful adoption data.

Can I monitor aeon.yml configuration diffs to identify which skills should be promoted or sunsetted?

Monitor aeon.yml configuration diffs across active forks to produce evidence-based Promote, Match, Sunset, and Fleet-only recommendation categories. This classification relies on enabled and override patterns observed exclusively within the configured fleet.

Why do my GitHub fork adoption metrics show high usage for skills that are just upstream defaults?

Fork adoption metrics show high default usage because unconfigured forks inherit upstream aeon.yml settings, creating heartbeat tautology. The leaderboard solves this by ranking adoption only among forks whose configurations meaningfully diverge from upstream defaults.