fork-first-run-alert

You can get alerts for GitHub fork first workflow runs by configuring this Skill to monitor parent repositories. It detects new fork activations, computes newly active forks, and emits notifications with run URLs and timestamps while maintaining a persistent seen-state to prevent duplicate alerts.

Fork activation monitoring tracks when forked repositories execute their first workflow run. It provides automated visibility into community engagement, enabling immediate recognition and timely response to new active forks within a parent repository's cohort.

Track first-run activity across repository forks by running this Skill to compute a NEW_ACTIVE cohort from monitored forks. It gathers per-fork run metadata including titles, URLs, and timestamps, then formats named alerts for clear visibility and traceability.

No, this first-run alerting tool operates without external dependencies. It reads and updates internal memory state and cohort caches directly to compute newly active forks and format notifications while honoring built-in safety constraints and processing limits.

Yes, you can backfill first-run alerts for previously active forks. The Skill maintains a persistent seen-state to support backfill on first run, ensuring historical fork activations are recognized without re-announcing previously processed forks.