fork-first-run-alert

Name: fork-first-run-alert
Availability: InStock
Author: @aaronjmars

Detect newly active GitHub forks on their first workflow run.

626|225|Updated Mar 4, 2026

Search Tags:#github #autonomous agents #workflow runs #fork monitoring #community alerts #notification batching #stateful scheduling

Ready to run

npx skills add https://github.com/aaronjmars/aeon --skill fork-first-run-alert-aaronjmars

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fork-first-run-alert
Source: https://github.com/aaronjmars/aeon/tree/main/skills/fork-first-run-alert
Command: npx skills add https://github.com/aaronjmars/aeon --skill fork-first-run-alert-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It solves the visibility gap where newly activated GitHub forks can run for days without anyone noticing, delaying recognition and outreach.

Core Features & Use Cases

Daily first-run alerts for new ACTIVE/POWER forks: Detects forks that just crossed from unseen to active and emits named notifications the day it happens.
Cohort-cache + live API fallback: Uses a fast cohort state cache when fresh, otherwise falls back to GitHub API checks per fork.
Robust anti-spam and safety guardrails: Handles dry-run mode, caps live scanning, batches notifications when there are many activations, and records persistent state to prevent re-announcing.

Quick Start

Trigger the skill with a dry run to validate behavior for the default parent repo: send fork-first-run-alert var as "dry-run".

Frequently Asked Questions about fork-first-run-alert

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

FAQPage Schema

Can I test fork monitoring alerts before enabling live notifications?▼

Yes, you can trigger the skill in dry-run mode to validate behavior for the default parent repo without sending live announcements. This allows you to safely test first-run alert detection and verify anti-spam guardrails before activating community visibility notifications.

How does GitHub fork monitoring handle API rate limits during fleet scanning?▼

Fork monitoring uses a fast cohort state cache when fresh, otherwise falling back to GitHub API checks per fork. It caps live scanning and applies strict gating with persistent seen-state management to prevent re-announcing and manage API rate limits across daily fleet monitoring.

How do workflow run alerts manage notification batching for many active forks?▼

Workflow run alerts batch notifications when many fork activations occur simultaneously, preventing spam. Persistent state records suppress bot accounts via an allowlist and ensure each newly active fork is announced only once on its first completed workflow run.

What is needed to set up autonomous daily fleet monitoring for GitHub forks?▼

You need persistent seen-state management for strict gating and reliable GitHub API data retrieval via gh api. The autonomous daily fleet monitoring applies cached cohort state and live API lookups to detect newly active forks across repos and emit community alerts.