fork-first-run-alert

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

6|2|Updated May 21, 2026

Search Tags:#state tracking #gitHub #workflow runs #fork monitoring #community alerts #autonomous ops #notification batching

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill closes the visibility gap between weekly fork-cohort tracking and same-day activations by alerting you when a fork runs its very first workflow for the first time.

Core Features & Use Cases

First-run community detection: Identifies forks whose latest workflow run appears for the first time while they are in the ACTIVE/POWER cohort.
Persistent seen-list state: Stores a bounded, long-lived record to ensure forks are not re-announced after the initial alert.
Cost-aware GitHub API strategy: Prefers a cached cohort state (fast path) and falls back to live per-fork run lookups only when the cache is stale.

Quick Start

Configure and run the fork-first-run-alert skill daily using the default parent repo, or optionally pass an owner/repo override to target a specific upstream.

Frequently Asked Questions about fork-first-run-alert

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

FAQPage Schema

How do I get alerts when a GitHub fork runs its first workflow?▼

To get alerts when a GitHub fork runs its first workflow, you can use a monitoring skill that tracks fork fleets daily and emits same-day notifications upon detecting a fork's initial workflow run.

How does fork monitoring prevent duplicate workflow run alerts?▼

Fork monitoring prevents duplicate workflow run alerts by implementing stateful tracking via a persistent seen-list JSON file, ensuring a fork is never re-announced after its initial first-run alert.

How do I monitor first-run workflow activations for a specific parent repo?▼

You can monitor first-run workflow activations for a specific parent repo by passing an owner/repo override to the daily autonomous monitoring skill, targeting the desired upstream repository.

Does GitHub fork monitoring work when the cohort cache is stale?▼

GitHub fork monitoring works when the cohort cache is stale by falling back to live per-fork action run lookups using GitHub CLI API calls, applying retry and gating logic to manage costs.

Can I test GitHub fork alerts without sending live notifications?▼

You can test GitHub fork alerts without sending live notifications by utilizing the skill's dry-run mode, which validates the monitoring and detection logic without emitting actual community alerts.