AEON Gallery

Disabled defaults

Auto-generated by scripts/atlas.mjs on 2026-06-01. Which upstream-enabled skills are systematically turned off by forks?

Tracking 3 upstream root(s). Per-root tables below.

aaronjmars/aeon-agent

Sample size: 1 fork(s) — rates are not statistically meaningful at this scale; treat as descriptive only.

Ships 17 skill(s) enabled by default. Disable rates across 1 forks:

Skill Disabled by Rate
fleet-skill-adoption 1 / 1 100%
operator-scorecard 1 / 1 100%
project-lens 1 / 1 100%
skill-enabler 1 / 1 100%
star-milestone 1 / 1 100%
star-momentum-alert 1 / 1 100%
thread-formatter 1 / 1 100%
weekly-shiplog 1 / 1 100%
feature 0 / 1 0%
heartbeat 0 / 1 0%
memory-flush 0 / 1 0%
push-recap 0 / 1 0%
repo-actions 0 / 1 0%
repo-article 0 / 1 0%
repo-pulse 0 / 1 0%
self-improve 0 / 1 0%
token-report 0 / 1 0%

aaronjmars/miroshark-aeon

Sample size: 1 fork(s) — rates are not statistically meaningful at this scale; treat as descriptive only.

Ships 15 skill(s) enabled by default. Disable rates across 1 forks:

Skill Disabled by Rate
operator-scorecard 1 / 1 100%
star-milestone 1 / 1 100%
star-momentum-alert 1 / 1 100%
thread-formatter 1 / 1 100%
feature 0 / 1 0%
heartbeat 0 / 1 0%
memory-flush 0 / 1 0%
project-lens 0 / 1 0%
push-recap 0 / 1 0%
repo-actions 0 / 1 0%
repo-article 0 / 1 0%
repo-pulse 0 / 1 0%
self-improve 0 / 1 0%
token-report 0 / 1 0%
weekly-shiplog 0 / 1 0%

aaronjmars/aeon

Ships 3 skill(s) enabled by default. Disable rates across 140 forks:

Skill Disabled by Rate
fleet-skill-adoption 115 / 140 82%
skill-enabler 110 / 140 79%
heartbeat 0 / 140 0%

≥ 50% disable rate → defaults to reconsider (roots with ≥ 5 forks)

Skills disabled by a majority of operators are strong candidates for upstream to either (a) ship disabled-by-default, (b) document better what the trade-off is, or (c) fix whatever’s making them unwelcome.

Universally accepted defaults (< 5% disable rate, roots with ≥ 5 forks)

These defaults are working — almost no one turns them off.

How this is computed

For each skill upstream has enabled: true in aeon.yml, count how many forks have enabled: false (or no entry for it) in their own aeon.yml. Forks that don’t carry a parseable aeon.yml are excluded from the denominator.

Caveat: the YAML probe is a regex (see scripts/atlas.mjs:parseEnabledSkills) that handles the single-line dict form (skill: { enabled: true, … }) but skips multi-line block dicts. Real disable rates may therefore be slightly under-counted for skills only ever set via the block form.