github-stars — Claude Code skill: GitHub star growth charts
github-stars renders terminal charts showing daily and hourly star growth for any GitHub repo in your chosen timezone. Track launches, Product Hunt spikes, or DevRel momentum in real time.
MIT 197 installs ★ 750 updated 2026-10-21
npx skills add OpenClaudia/openclaudia-skills --skill github-stars -a claude-codeWhat github-stars does
This skill fetches star timestamps from the GitHub API and draws two ASCII charts: stars per day (default 14 days) and stars per hour for recent days (default 2 days). It runs via the gh CLI, which must be installed and authenticated.
You need gh auth status to work and Python 3.9 or later. Daylight saving transitions are handled correctly through the standard zoneinfo library. GitHub returns timestamps only for the first 40,000 stars; the total count stays accurate, but hourly and daily breakdowns become incomplete beyond that threshold.
Run: bash github-stars.sh <owner/repo | search-term> [--tz <timezone>] [--days N] [--hours-days N]. Pass an exact repo name (facebook/react), a search term to find the top-starred match, or set your timezone (default America/Los_Angeles), day window, and hourly window. Re-run anytime to fetch live data — poll every 15 minutes or so to track a launch without hitting rate limits.
What it helps with
- monitor star velocity for a GitHub repo over hours and days
- spot launch spikes or Product Hunt peaks in real-time activity
- visualize star growth in a specific timezone with correct DST handling
Example prompts for the agent
- Show me the last 14 days of star growth for
vercel/next.jshour by hour - Pull star charts for
facebook/reactin bothAmerica/New_YorkandAsia/Shanghaitimezones - Did
reactget more stars this hour or yesterday at this time?
How to install github-stars
1Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill github-stars -a claude-code2Manually: put the files in place
~/.claude/skills/github-stars/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/github-stars/
1Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill github-stars -a codex2Manually: put the files in place
.agents/skills/github-stars/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill github-stars -a cursor2Manually: put the files in place
.cursor/skills/github-stars/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OpenClaudia/openclaudia-skills skills/github-stars2Manually: put the files in place
.github/skills/github-stars/SKILL.md1Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill github-stars -a gemini-cli2Platform CLI
gemini skills install https://github.com/OpenClaudia/openclaudia-skills --path skills/github-starsManually: put the files in place
.devin/skills/github-stars/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill github-stars -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about github-stars
How do I install github-stars in Claude Code?
Run npx skills add OpenClaudia/openclaudia-skills --skill github-stars -a claude-code, then open ~/.claude/skills/github-stars/SKILL.md.
What do I need to run github-stars?
GitHub CLI (gh) must be installed and authenticated — check gh auth status. Python 3.9 or newer is required. Without authentication, gh hits a low rate limit and fails on large repos.
Why does the hourly breakdown cut off at 40,000 stars?
The GitHub API returns timestamps only for the first 40,000 stargazers. The total star count is still accurate, but hourly and daily buckets are incomplete beyond that point. If the repo's live star count is higher, the gap reflects unstarring activity.
Source text
SKILL.md · MIT
--- name: github-stars description: Show a GitHub repo's star growth as CLI charts — by day and by hour, in any timezone. Use when the user asks to "check GitHub stars", "stars by hour/day for <repo>", "star growth", "how many stars did <repo> get today", or shares a repo name and wants its starring activity over time. --- # github-stars Fetch a repo's per-star timestamps from the GitHub API and render two ASCII charts in the terminal: **stars by day** and **stars by hour** (for the most recent day(s)). Useful for tracking a launch, a Show HN / Product Hunt spike, or DevRel growth. ## Requirements - The [`gh` CLI](https://cli.github.com/) installed and authenticated (`gh auth status`). Unauthenticated calls hit a low rate limit and large repos fail mid-pagination. - Python 3.9+ (uses the stdlib `zoneinfo` for correct DST handling). ## How it works The script calls `gh api` with the `application/vnd.github.star+json` Accept header, which adds a `starred_at` timestamp to each stargazer. It paginates through all stargazers, converts each timestamp to the target timezone, and buckets them by day and by hour. ## Usage The script lives next to this file. From the skill directory: ```bash bash github-stars.sh <owner/repo | search-term> [--tz <IANA tz>] [--days N] [--hours-days N] ``` - **`<owner/repo>`** — exact repo (e.g. `facebook/react`). Skips the search. - **`<search-term>`** — a bare word (no `/`) is resolved to the top repo by stars. - **`--tz`** — IANA timezone for all buckets. Default `America/Los_Angeles`. Use e.g. `UTC`, `America/New_York`, `Asia/Shanghai`, `Europe/Berlin`. - **`--days N`** — how many recent days to show in the daily chart (default 14). - **`--hours-days N`** — how many recent days to break out hourly (default 2). ## Examples ```bash # default: last 14 days daily + last 2 days hourly bash github-stars.sh vercel/next.js # resolve a search term, show UTC bash github-stars.sh next.js --tz UTC # zoom in: only today hourly, 7-day daily window bash github-stars.sh facebook/react --days 7 --hours-days 1 ``` ## Sample output ``` owner/repo — 284 stars (with timestamps) newest: 2026-06-15 02:03 PM PDT | now: 2026-06-15 02:11 PM PDT STARS BY DAY (PDT) 2026-06-13 16 █████████ 2026-06-14 69 ████████████████████████████████████████ ← peak 2026-06-15 22 █████████████ STARS BY HOUR — 2026-06-15 (PDT) total 22 06:00 5 ██████████████████████████████ 07:00 2 ████████████ 14:00 2 ████████████ ``` ## Caveats — surface these to the user when relevant - **40,000-star cap:** GitHub only returns `starred_at` for the first 40k stargazers. Past that, the hourly/daily breakdown is incomplete (the script warns). The plain total stays accurate. - **Net, not gross:** the stargazer list reflects stars currently in place. Un-stars don't appear, so a flat total between two checks can hide +1/−1 churn. If the live `stargazers_count` disagrees with the timestamp count, an un-star happened. - **DST is handled** automatically via `zoneinfo` — don't hardcode UTC offsets. ## Re-checking / live polling Just run the script again — it re-fetches live each time. To watch a launch, re-run on an interval and report the delta; don't poll faster than every ~15 minutes (rate limits + politeness).
© OpenClaudia · MIT · OpenClaudia/openclaudia-skills