fork-first-run-alert

Detect forks completing their first workflow run and generate named alerts.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill fork-first-run-alert-atrium-hermes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fork-first-run-alert
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/fork-first-run-alert
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill fork-first-run-alert-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Daily — named alert the day a fork completes its first ever workflow run. Fork-cohort runs weekly; this skill catches the activation moment to reduce the gap between activation and recognition.

Core Features & Use Cases

  • Detects forks for which the ACTIVE/POWER state has just emerged and triggers a named alert on first activation.
  • Supports a dry-run mode, a parent-repo override, and a backfill behavior on first run.
  • Maintains a persistent seen list with a 500-entry limit, and writes logs for each run.

Quick Start

Inspect today’s forks and simulate first-run alerts without sending notifications.

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 a notification when a GitHub fork runs a workflow for the first time?

You can generate a named alert the day a fork completes its first workflow run by using a Skill that tracks activation states. It identifies active forks and triggers notifications when their first workflow run completes.

Can I test fork workflow alerts without sending live notifications?

Yes, you can simulate first-run alerts without sending notifications by enabling dry-run mode. This allows you to inspect today's fork activity and verify alert behavior safely before executing live.

How many forks can this alert system track at once?

The alert system tracks fork activity using a persistent seen list with a 500-entry limit. It manages cohort caches and applies batch notification rules to prevent alert fatigue.

Does this GitHub fork alert tool work on a specific parent repository?

Yes, the tool operates on a parent repository and includes an optional parent-repo override. It also supports a backfill behavior on the first run to establish initial state tracking.

What happens if the local fork cohort cache is missing?

The system has a live fallback to the GitHub API to retrieve fork data if the local cache is unavailable. This ensures continuous monitoring of workflow runs and accurate first-run alerts.

How do I reduce notification noise from automated fork alerts?

You can reduce noise using built-in batch notification rules and bot-allowlist handling. The system processes cohort caches and applies a 500-entry seen list to avoid duplicate alerts.