fork-cohort

To track GitHub fork activity, you can classify forks into activation buckets like POWER, ACTIVE, STALE, or COLD by reading GitHub Actions run history and last-run timestamps. This reveals which repository forks are currently operational versus dormant.

The aeon.yml file influences power status through its enabled flags. When assessing fork activation status, the skill optionally checks each fork's aeon.yml configuration to determine whether enabled skills should elevate the fork's classification to a power status.

Generating a weekly cohort report involves classifying forks by activation status, computing deltas from previous states, and writing a weekly cohort article. This tracks transitions and trends across your repository forks for maintenance decisions.

Yes, you can monitor a growing fleet of Aeon forks automatically by applying weekly status reporting that reads GitHub Actions run history. This surfaces operational health signals to help identify active instances and dormant forks for outreach.

Fork status buckets classify activation levels: POWER indicates forks with active aeon.yml enabled flags, ACTIVE shows recent GitHub Actions runs, STALE means diminished run history, and COLD identifies dormant forks with no recent activity.

No external dependencies are required to classify forks and update persistent memory state. The skill reads GitHub Actions run history and last-run timestamps directly, then computes deltas and writes cohort articles without additional packages.