Bucket GitHub repository forks into activation cohorts from workflow run history and aeon.yml skill counts.
npx skills add https://github.com/anajuliabit/aeon --skill fork-cohort
Please help me install this Agent Skill. Skill: fork-cohort Source: https://github.com/anajuliabit/aeon/tree/main/skills/fork-cohort Command: npx skills add https://github.com/anajuliabit/aeon --skill fork-cohort
This Skill solves the visibility gap of GitHub forks that look healthy by code history but are not actually running in your production automation.
Run fork-cohort to generate a weekly article that buckets all forks of the parent repo by current activation stage and includes the key cohort movements.
High-intent search queries and answers about installing and using this skill.
Monitor active GitHub forks by bucketing them into activation cohorts using recent GitHub Actions workflow run history. This approach classifies forks by actual automation health over the last 7 days, exposing forks that look healthy by code but are not running in production.
Fork cohort analysis groups repository forks into COLD, STALE, ACTIVE, and POWER categories by querying latest workflow run timestamps via the GitHub API. It detects week-over-week movement signals like leveled-ups and revived stale forks to emit a capped markdown report and updated JSON state log.
Generate a weekly health digest by running periodic autonomy monitoring that computes cohort transitions from stored state. The process reads each fork's aeon.yml to count enabled skills, detects week-over-week movement signals, and emits a size-capped markdown report with an updated JSON state log.
Detect power users by upgrading forks to a POWER cohort only when recent GitHub Actions workflow activity exists and at least 5 skills are enabled in the fork's aeon.yml. This requires reading the aeon.yml file from each fork to count enabled skills alongside workflow run history.
Prioritize quiet fork owners by detecting which forks went stale or newly cold based on stored cohort state and latest workflow run timestamps. This social-proof reporting identifies which production automation has stopped running, helping you check in on specific fork owners when activity ceases.
GitHub fork monitoring requires no external dependencies to query workflow run timestamps and fork lists. The process directly queries the GitHub API to read latest workflow run timestamps and reads aeon.yml from each fork to compute cohort transitions from stored JSON state.
swarm-ai-researchClassify GitHub forks into POWER, ACTIVE, STALE, or COLD status buckets.
ekatasingh1107Generate a weekly pipeline dashboard from CRM data and agency.config.json targets.
Atrium-HermesValidate aeon.yml and GitHub Actions workflow structural correctness.
aaronjmarsClassify GitHub repository forks into POWER, ACTIVE, STALE, and COLD buckets by workflow-run activity.
