milestone-tracker

Tracks weekly progress toward product milestones and notifies on crossings, approaches, and stalls.

Updated May 25, 2026
One-click install
npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill milestone-tracker-cbowcrptex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: milestone-tracker
Source: https://github.com/Cbowcrptex/CBOWCRYPTEX/tree/main/skills/milestone-tracker
Command: npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill milestone-tracker-cbowcrptex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose sight of whether key product and growth metrics are actually moving week over week. This Skill automates weekly milestone checks by fetching current values, comparing them against recorded baselines, and alerting only when something notable happens. ## Core Features & Use Cases - Automated state fetching: Pulls GitHub star counts via the gh CLI and counts enabled skills from aeon.yml, with fallback to last recorded values on API failure. - Status classification: Labels each milestone as crossed, done, approaching, stalled, or on-track based on delta, percentage of target, and consecutive weeks without movement. - Conditional notifications: Writes a formatted digest and sends it through a notify script only when milestones cross, approach, or stall. - Use Case: A maintainer wants to know when a repository hits 1,000 stars or when growth has flatlined for two weeks; the Skill runs weekly, updates memory/milestones.md, and sends an alert only when action is warranted. ## Quick Start Run the milestone tracker to check this week's progress against my milestones and notify me of anything notable.

Frequently Asked Questions about milestone-tracker

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

FAQPage Schema
How do I track GitHub repository star milestones automatically?▼

Add a row to memory/milestones.md with a target in the format stars:owner/repo:count. The Skill fetches the current star count using gh api repos/owner/repo and classifies progress against your target each run.

How do I get notified when a metric stalls or crosses a target?▼

The Skill classifies milestones as crossed, approaching, stalled, or on-track, then writes a formatted digest to .pending-notify-temp and sends it via the ./notify script. If nothing is notable, it logs MILESTONE_TRACKER_OK and skips notification.

What milestone target formats are supported?▼

Three formats are supported: stars:owner/repo:N for GitHub star counts, skills:N for counting enabled skills in aeon.yml, and manual:label for operator-maintained milestones whose status is updated by hand.

What happens if the GitHub API call fails during a run?▼

If gh api fails due to a private repo or rate limit, the Skill falls back to the Last value recorded in memory/milestones.md instead of failing the entire run. Other milestones continue to be processed normally.

Does the milestone tracker require API keys or environment variables?▼

No environment variables are required. The gh CLI authenticates automatically using the workflow's GITHUB_TOKEN, and the aeon.yml grep check is local-only, so no external network access beyond the GitHub API is needed.