github-traffic

zc277584121/marketing-skills · updated Apr 8, 2026

$npx skills add https://github.com/zc277584121/marketing-skills --skill github-traffic
0 commentsdiscussion
summary

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.

skill.md

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.

Recommended: set up a cron job or CI schedule to run the snapshot command periodically:

# Daily snapshot via cron (no output, just stores data)
0 9 * * * python /path/to/scripts/github_traffic.py owner/repo --snapshot

Default Workflow

python /path/to/skills/github-traffic/scripts/github_traffic.py <owner/repo>

This will:

  1. Fetch current traffic data via gh api
  2. Save a snapshot to ~/.github-traffic/ for historical tracking
  3. Display a formatted summary (views, clones, referrers, popular pages)

Generating Charts

# Generate PNG trend chart (last 30 days, default)
python .../github_traffic.py owner/repo --chart

# Last 7 days
python .../github_traffic.py owner/repo --chart --days 7

# Last 90 days (needs accumulated history)
python .../github_traffic.py owner/repo --chart --days 90

# ASCII chart (no matplotlib needed)
python .../github_traffic.py owner/repo --ascii

The PNG chart includes up to 3 panels:

  1. Page Views — total views and unique visitors (area chart)
  2. Git Clones — total clones and unique cloners (bar + line chart)
  3. Star Growth — star count over time (line chart, shown when multiple snapshots exist)

Script Options

Flag Default Description
repo (positional) required Repository in owner/name format
--chart off Generate PNG trend chart
--ascii off Force ASCII bar chart output
--days 30 Number of days to include in chart
--history-dir ~/.github-traffic/ Directory for historical data storage
--output <repo>_traffic.png Output path for chart image
--snapshot off Fetch and store data only (no display)

Examples

# Quick traffic summary
python .../github_traffic.py zilliztech/memsearch

# Weekly trend chart
python .../github_traffic.py zilliztech/memsearch --chart --days 7

# Monthly trend chart, custom output path
python .../github_traffic.py zilliztech/memsearch --chart --days 30 --output ./reports/traffic.png

# Just store a snapshot (for cron jobs)
python .../github_traffic.py zilliztech/memsearch --snapshot

# ASCII chart when matplotlib is not available
python .../github_traffic.py zilliztech/memsearch --ascii --days 14

History & Long-Term Tracking

Each run merges the current 14-day window into a persistent JSON file at ~/.github-traffic/<owner>_<repo>_traffic.json. The file contains:

  • Daily views: date → {views, unique}
  • Daily clones: date → {clones, unique}
  • Star snapshots: date → star count
  • Fetch metadata: timestamp, 14-day totals, stars, forks

To build meaningful 30/90-day charts, run the script at least every 14 days (daily is ideal). Gaps longer than 14 days will show as missing data in charts.


Permissions

The GitHub Traffic API requires push access to the repository. This means:

  • Repository owners and admins: full access
  • Collaborators with write/maintain role: full access
  • Read-only users and forkers: no access (API returns 403)

If you get a permission error, check your gh auth status and ensure your token has the repo scope.


Troubleshooting

Problem Solution
"Must have push access" error You need write access to the repo. Check gh auth status.
Chart shows only 14 days GitHub only provides 14-day windows. Run --snapshot regularly to accumulate history.
matplotlib not found Install with pip install matplotlib. Or use --ascii for text-based charts.
No data for some dates GitHub may not report days with zero traffic. These gaps are normal.

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.666 reviews
  • Xiao Garcia· Dec 28, 2024

    Useful defaults in github-traffic — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Zara Chawla· Dec 20, 2024

    github-traffic is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Liam Chen· Dec 16, 2024

    Registry listing for github-traffic matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Li Park· Dec 12, 2024

    github-traffic reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Zara Bhatia· Dec 12, 2024

    github-traffic fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Zaid Wang· Nov 11, 2024

    Solid pick for teams standardizing on skills: github-traffic is focused, and the summary matches what you get after install.

  • Zara Kapoor· Nov 7, 2024

    github-traffic fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Harper Park· Nov 7, 2024

    I recommend github-traffic for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Tariq Haddad· Nov 3, 2024

    We added github-traffic from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Olivia Tandon· Oct 26, 2024

    We added github-traffic from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 66

1 / 7