testflight-monitor

What problem does it solve?

Many TestFlight betas are advertised with cryptic codes and fill up quickly, creating noisy notifications and wasted manual checks. This skill solves the problem by continuously monitoring TestFlight join links, resolving human-friendly app names, tracking prior status, and only notifying when a beta transitions from full to available.

Core Features & Use Cases

• Smart lookups: Resolve obfuscated TestFlight codes to readable app names using a community-powered lookup table and optional custom overrides.
• Single and batch checks: Check a single TestFlight URL on demand or run silent batch checks across many links, ideal for cron-based monitoring.
• Stateful alerts: Persist last-known states in JSON and alert only on meaningful transitions (full → available) to avoid spam.
• Maintenance tools: Update the community lookup from the awesome-testflight-link source to keep names current.
• Use case: Add a list of beta links to the batch configuration and run the batch job hourly via cron to receive announcements only when slots open.

Quick Start

Run the batch monitor to check all configured TestFlight links and only report when any app changes from full to available.