Github Traffic

A straightforward tool for tracking GitHub repo traffic over time, which matters because GitHub only keeps the last 14 days and then tosses it. Fetches views, clones, referrers, and stars via the gh CLI, saves snapshots locally to build history, and generates PNG trend charts with matplotlib. Requires push access to the repo, so read-only collaborators are out of luck. The real value is in running it on a schedule to accumulate months of data you'd otherwise lose. Good for maintainers who want actual traffic insights beyond GitHub's tiny window, though you need to remember to snapshot regularly or set up a cron job.

skills.sh installs: 3.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add zc277584121/marketing-skills --skill github-traffic --agent claude-code

Installs into .claude/skills of the current project.

Files

Skill: GitHub Traffic

Fetch and analyze GitHub repository traffic data — page views, git clones, referral sources, popular pages, and star growth. Optionally generate trend charts as PNG images.

Prerequisites:

gh CLI must be installed and authenticated

Push (write) access to the target repository is required — GitHub's Traffic API does not work with read-only access

matplotlib is optional (for PNG chart generation; falls back to ASCII if unavailable)

When to Use

The user asks about repository traffic, page views, clone counts, or where visitors come from
The user wants to see traffic trends over time (weekly, monthly, quarterly)
The user wants to generate traffic report charts for sharing or documentation
The user wants to periodically snapshot traffic data to build long-term history

Important: GitHub Traffic API Limitations

GitHub only provides the last 14 days of traffic data. To track trends over longer periods (30 days, 90 days, etc.), the script stores each fetch in a local history file (~/.github-traffic/<repo>_traffic.json). Regular snapshots are required to build up history.

SKILL.md on GitHub