GitHub Growth Tracker is a skill for monitoring and analyzing the trajectory of GitHub repositories over time. Rather than reporting only current counts, it maintains a 90-day time-series database of stars, forks, issues, and commit velocity, enabling trend analysis instead of point-in-time snapshots.

The skill tracks star velocity and uses directional indicators to show whether a metric is rising, falling, or flat. Commit velocity is measured using a 4-week rolling average across multiple repositories, giving a view of active development windows rather than raw commit counts.

A watchlist benchmarking feature lets you compare your own repositories against a set of aspirational repositories to gauge relative growth rates. This is useful when assessing whether a project is gaining traction in proportion to peers.

Automated digests are formatted as plain text, making them suitable for delivery to Slack, Discord, or other status update channels without additional transformation.

The skill integrates with GitHub’s REST API using fine-grained Personal Access Tokens and uses a standardized local data directory for persistent historical tracking. It is designed to run inside AI agent environments. Because no tools are exposed in the tool list and no package registry entry is provided, setup details and invocation specifics should be confirmed from the repository directly before integration.

Use cases

Track star velocity for one or more repositories over a 90-day window

Compare commit activity trends across multiple repos using a 4-week rolling average

Benchmark a repository's growth rate against a curated watchlist of aspirational repos

Generate formatted text digests for posting repository health summaries to Slack or Discord

Detect when a repository is losing momentum relative to historical baselines

Monitor forks and open issues alongside star counts for a fuller activity picture

When to use it

When you need historical trend data rather than current snapshot counts for GitHub repos

When managing multiple repositories and want a single digest summarizing activity across all of them

When you want to benchmark your project's growth against specific reference repositories

When running inside an AI agent environment such as Claude Code or Cursor

When not to use it

When you need data beyond a 90-day historical window

When you require integration with version control platforms other than GitHub

When no GitHub Personal Access Token is available or can be provisioned

When you need structured API tool calls exposed at runtime — no tools are listed for this skill

When the deployment environment does not support persistent local file storage for the data directory

Github Growth Tracker

Use cases

When to use it

When not to use it