Fork Health

Monitor GitHub fork activity and classify forks into health tiers.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/aeoncity-demo/myaeon --skill fork-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Fork Health
Source: https://github.com/aeoncity-demo/myaeon/tree/main/skills/fork-health
Command: npx skills add https://github.com/aeoncity-demo/myaeon --skill fork-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides insights into the health and activity of GitHub forks, categorizing them into tiers based on push recency, enabled skill count, and PR activity.

Core Features & Use Cases

  • Health Tiering: Classifies forks into tiers like ACTIVE, WARM, STALE, and QUIET based on their activity levels.
  • Fleet Health Ratio: Calculates the ratio of ACTIVE forks within the fleet.
  • Top-10 ACTIVE Forks: Provides a leaderboard of the most active forks.
  • Weekly Updates: Generates reports weekly, with optional notifications for significant changes.

Quick Start

Use the fork-health skill to get a report on the health of GitHub forks.

Frequently Asked Questions about Fork Health

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

FAQPage Schema
How do I monitor GitHub fork activity and health metrics?

Monitoring GitHub fork health requires tracking push recency, enabled skill counts, and PR activity to classify forks into tiers. This Skill automates that process by retrieving fork and PR data via the GitHub API to assess overall fleet health.

What is GitHub fork health tiering and how does it work?

GitHub fork health tiering classifies forks into ACTIVE, WARM, STALE, and QUIET categories based on activity metrics. It evaluates push recency, enabled skill counts, and PR activity to provide a clear fleet health ratio and identify the most active forks.

Can I track GitHub PR activity across multiple forks automatically?

Yes, you can track GitHub PR activity across multiple forks automatically. The Skill requires GitHub API access to retrieve PR data and push recency, generating weekly reports and notifications for significant changes in fork activity levels.

How do I generate weekly health reports for GitHub forks?

You can generate weekly GitHub fork health reports by retrieving activity metrics via the GitHub API. The Skill analyzes push recency and PR activity, calculating fleet health ratios and providing optional notifications for significant changes.

Does fork monitoring require GitHub API access?

Yes, GitHub fork monitoring requires GitHub API access to retrieve fork and PR data. The API provides the necessary activity metrics, such as push recency and PR activity, to classify forks into health tiers and calculate fleet health ratios.

What are the limitations of tracking fork health metrics automatically?

Tracking fork health metrics relies entirely on GitHub API data availability for push recency and PR activity. If the API rate limits are exceeded or fork data is restricted, the health tiering and fleet health ratio calculations will not update accurately.