fleet-skill-adoption

Measure upstream skill adoption across POWER+ACTIVE forks using enabled:true in aeon.yml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves uncertainty about which of a large upstream catalog of skills are actually enabled and running across real, active forks by producing a fleet-wide adoption leaderboard based on enabled:true in aeon.yml.

Core Features & Use Cases

  • Fleet adoption leaderboard (enabled:true): Counts adoption per upstream skill using only POWER+ACTIVE forks and only where the skill is enabled in each fork’s aeon.yml.
  • Top/Bottom insights with shipping-aware ranking: Highlights most adopted skills, least adopted established skills, and separates freshly shipped skills (not yet rank-shamed).
  • Trend-aware movement: Compares the current week to the prior saved run to identify adoption gainers/decliners and top-10 churn, while supporting quiet runs when nothing changes.

Quick Start

Run the fleet-skill-adoption skill weekly to publish the current adoption leaderboard for upstream skills across active forks.

Frequently Asked Questions about fleet-skill-adoption

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

FAQPage Schema
How do I track skill adoption trends across active forks using aeon.yml?▼

Identify zero-adoption skills by aggregating enabled:true counts from active forks and filtering for skills with no enablement, separating freshly shipped skills from established skills to avoid prematurely rank-shaming new releases.

How do I generate a weekly leaderboard for upstream skill enablement?▼

Detect adoption gainers and decliners by comparing the current week's aggregated enablement counts to the prior saved run, identifying top-10 churn and trend-aware movement while supporting quiet runs when nothing changes.

Does the fleet adoption reporting work with cached and API fallback fork lists?▼

Distinguish top adopted skills from bottom adopted established skills by applying shipping-aware ranking, which separates freshly shipped skills within a defined recency window so they are not yet rank-shamed alongside established skills.

What is the best way to report on fleet-wide skill usage without manual counting?▼

Apply shipped-fresh filtering within a defined recency window to separate newly released skills from established ones, ensuring recently shipped skills are not prematurely rank-shamed while still detecting zero-adoption among older entries.