star-momentum-alert

Projects GitHub star milestone crossings from14-day repo-pulse logs for Show HN window alerts.

6|2|Updated May 21, 2026
One-click install
npx skills add https://github.com/anajuliabit/aeon --skill star-momentum-alert
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: star-momentum-alert
Source: https://github.com/anajuliabit/aeon/tree/main/skills/star-momentum-alert
Command: npx skills add https://github.com/anajuliabit/aeon --skill star-momentum-alert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Star milestone and daily repo deltas don’t tell you when the next milestone will land in the specific Tue/Wed/Thu Show HN dispatch window, which causes launches to miss the moment.

Core Features & Use Cases

  • 14-day projection from repo-pulse logs: Converts the last 14 days of stargazer counts into a projected milestone crossing date.
  • Window-aware alerts: Alerts only when the projected crossing is 7–14 days out and lands on Tue, Wed, or Thu.
  • Milestone ladder alignment: Uses the same round-number ladder as the companion star-milestone skill so both systems agree on what counts as a milestone.
  • Idempotent, deduped notifications: Avoids repeated alerts for the same (repo, milestone) within the configured period.
  • Always writes an audit article: Produces a per-day report even when no alerts fire, using local memory/logs as the canonical input.

Quick Start

Ask your agent to run star-momentum-alert with var set to dry-run to generate the projection article and logs without sending any notifications.

Frequently Asked Questions about star-momentum-alert

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

FAQPage Schema
How do I forecast when a GitHub repo will cross its next star milestone?β–Ό

You can schedule Show HN launches by projecting star milestone crossing dates and checking if they fall within a Tue, Wed, or Thu dispatch window. Alerts only fire when the projected crossing is 7–14 days out to ensure launch-ready timing.

How do I schedule Show HN launches based on stargazer growth?β–Ό

You can schedule Show HN launches by projecting star milestone crossing dates and checking if they fall within a Tue, Wed, or Thu dispatch window. Alerts only fire when the projected crossing is 7–14 days out to ensure launch-ready timing.

Can I run a dry-run projection for GitHub repo analytics without sending alerts?β–Ό

This skill requires local file I/O, reading 14 days of stargazer counts from memory/watched-repos.md and memory/logs. It writes projection outputs to articles/star-momentum-<today>.md and updates state in memory/topics/star-momentum-state.json.

Do I need local repo-pulse logs to trigger star milestone alerts?β–Ό

This skill requires local file I/O, reading 14 days of stargazer counts from memory/watched-repos.md and memory/logs. It writes projection outputs to articles/star-momentum-<today>.md and updates state in memory/topics/star-momentum-state.json.

How does deduplication work for repeated GitHub star milestone alerts?β–Ό

Deduplication prevents repeated alerts for the same repo and milestone target within the configured period. The system tracks per-(repo, target) pairs in its state file to ensure each projected star crossing only triggers one notification.