skills.rest
aaronjmars
aaronjmarsCOMMUNITY
Explore all skills by this author →
𝕏@aaronjmarsGitHub

fork-cohort

Classify GitHub repository forks into POWER, ACTIVE, STALE, and COLD buckets by workflow-run activity.

626|225|Updated Mar 4, 2026
Search Tags:#github#forks#workflow runs#cohort reporting#community metrics#autonomous monitoring#incident visibility
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill fork-cohort-aaronjmars
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fork-cohort
Source: https://github.com/aaronjmars/aeon/tree/main/skills/fork-cohort
Command: npx skills add https://github.com/aaronjmars/aeon --skill fork-cohort-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill resolves the visibility gap of “how many forks exist” versus “how many forks are actually running production workflows right now,” so you can spot abandoned or stalled community setups.

Core Features & Use Cases

  • Weekly cohort tracking by run activity: Buckets each fork into POWER / ACTIVE / STALE / COLD (and UNREADABLE) based on the last workflow run timestamp, not code divergence.
  • Config-aware POWER detection: For forks with recent runs, it reads each fork’s aeon.yml and confirms the fork has at least 5 enabled skills to qualify as POWER.
  • Week-over-week movement reporting: Persists prior state and computes transitions like LEVELED_UP, REVIVED, and WENT_STALE, then generates a capped weekly article.
  • Fleet-friendly, read-only reporting: Lists forks, checks Actions run history, and reads aeon.yml content without writing to any fork repositories.

Quick Start

Use the fork-cohort skill to generate and publish this week’s fork activation cohort article and a notification summarizing which forks leveled up, revived, or went stale.

Frequently Asked Questions about fork-cohort

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

FAQPage Schema
How do I check which GitHub forks are actively running workflows?▼

To check which GitHub forks are actively running workflows, you can classify each fork by recent GitHub Actions workflow-run activity, bucketing them into POWER, ACTIVE, STALE, or COLD categories based on their latest run timestamps.

What is the difference between stale and cold community-managed forks?▼

The difference between stale and cold community-managed forks is based on recent GitHub Actions workflow-run activity. Stale forks show some prior run history, while cold forks lack recent workflow execution, indicating abandoned or stalled setups.

How do I track week-over-week GitHub Actions run activity across multiple forks?▼

You track week-over-week GitHub Actions run activity across multiple forks by persisting prior state as JSON and computing state transitions like LEVELED_UP, REVIVED, and WENT_STALE, then generating a capped weekly cohort article.

Can I monitor GitHub fork workflow enablement without writing to repositories?▼

Yes, you can monitor GitHub fork workflow enablement without writing to repositories. This fleet-friendly, read-only reporting approach lists forks, checks Actions run history, and reads aeon.yml content without modifying any fork.

How does a GitHub fork qualify as a POWER cohort member based on workflow runs?▼

A GitHub fork qualifies as a POWER cohort member when it has recent workflow runs and its aeon.yml file confirms at least 5 enabled skills, ensuring scheduling reliability and workflow enablement meet the threshold.

Does autonomous fork monitoring handle paginated GitHub repository enumeration?▼

Yes, autonomous fork monitoring handles paginated GitHub repository enumeration. It performs paginated fork enumeration and Actions run lookups with retry-based error handling to reliably classify workflow activity across large fork networks.

Related Skills

Explore More Content & Communication Skills→
swarm-ai-researchswarm-ai-research

fork-cohort

Classify GitHub forks into POWER, ACTIVE, STALE, or COLD status buckets.

Official
Advanced
Atrium-HermesAtrium-Hermes

contributor-spotlight

Generate weekly recognition posts from fork-cohort data for fork operators.

Community
Advanced
anajuliabitanajuliabit
6

fork-first-run-alert

Detect GitHub forks completing their first workflow run and emit named notifications.

Community
Advanced
sungaoxiang-backendsungaoxiang-backend

evidence-review-methodology

Evaluate evidence credibility with four governing methods under legal standards.

Community
Basic