← Back to Skills Marketplace
99rebels

Github Growth Tracker

by 99rebels · GitHub ↗ · v1.4.0 · MIT-0
cross-platform ⚠ pending
157
Downloads
0
Stars
0
Active Installs
10
Versions
Install in OpenClaw
/install github-growth-tracker
Description
Track GitHub repo growth (stars, forks, issues, commits) with periodic digests and trend analysis. Compare your repos against a watchlist. Use when checking...
README (SKILL.md)

GitHub Growth Tracker 📊

Track stars, forks, issues, and commit activity across GitHub repos. Generates text digests with trend arrows (↑↓→) and compares your repos against a watchlist you curate.

Why

You ship code but have no idea if anyone's using it. This skill gives you a weekly pulse on your projects — what's growing, what's stagnant, and how you stack up against repos you admire.

When to Use

  • "Check my repo stats"
  • "How's my project doing on GitHub?"
  • "Give me a growth digest"
  • "Compare my repo against X"

Credentials

Required: GitHub Personal Access Token (fine-grained, public repo read-only).

Create at: github.com → Settings → Developer settings → Personal access tokens
Type:     Fine-grained
Access:   Public repos (read-only)

Pass via setup --token \x3CTOKEN> (saved to \x3CDATA_DIR>/github.json) or set GITHUB_TOKEN env var.

⚠ Token is stored plaintext on disk. For higher security, use the GITHUB_TOKEN environment variable instead.

Setup

python3 scripts/github_tracker.py setup --token \x3CTOKEN>   # list your repos
python3 scripts/github_tracker.py add owner/repo1 owner/repo2  # track repos
python3 scripts/github_tracker.py add other/repo --watch  # watchlist
python3 scripts/github_tracker.py fetch                     # record data

Commands

setup [--token TOKEN]              List your repos, optionally save token
fetch                              Fetch metrics for all tracked + watched repos
digest                             Generate growth digest with trends
add repo1 [repo2 ...] [--watch]    Add repos to tracking or watchlist
remove owner/repo                  Stop tracking (history preserved)
list                               Show tracked repos and watchlist

Output Example

📊 GitHub Growth Digest — Friday April 03, 2026
====================================================

📌 Your Repos

   99rebels/blog-translator
      Stars: 3 ↑ (+2)
      Forks: 1 →
      Issues: 2 ↓ (-1)
      Commits (4w): 5 ↑ (+5)
      Lang: TypeScript  Last push: 2026-04-03
      vs watchlist: ✅ above avg commit velocity

📌 Watchlist

   octocat/Hello-World
      Stars: 3,550 NEW  Forks: 5,963 NEW  Commits (4w): 0

Format output for the current channel. Read references/formatting.md for platform-specific examples.

Scheduled Monitoring

python3 \x3Cskill_path>/scripts/github_tracker.py fetch && python3 \x3Cskill_path>/scripts/github_tracker.py digest

Data Directory

Credentials and data resolve to:

1. $SKILL_DATA_DIR (set by agent platform)
2. ~/.config/github-growth-tracker/  (default fallback)
Credentials: \x3CDATA_DIR>/github.json     (token)
Config:      \x3CDATA_DIR>/config.json      (repo lists)
History:     \x3CDATA_DIR>/repos/           (per-repo, 90 days)

Any platform can set $SKILL_DATA_DIR. If unset, ~/.config/github-growth-tracker/ is used. Works with OpenClaw, Claude Code, Codex, and any agent that can run Python scripts.

Notes

  • fetch skips repos already recorded today (safe to run multiple times)
  • add accepts multiple repos: add repo1 repo2 repo3
  • History auto-trims to 90 days on each save
  • GitHub API rate limit: 5,000 req/hour authenticated
Usage Guidance
This skill appears to be what it says: a GitHub metrics tracker. Before installing, note: 1) You must provide a GitHub Personal Access Token (fine-grained, public-repo read-only recommended). The skill can read GITHUB_TOKEN from the environment or save it to <DATA_DIR>/github.json; saving to disk writes the token in JSON (the script sets file mode 600). If you prefer greater safety, set GITHUB_TOKEN as an environment variable instead of running setup --token. 2) The registry metadata does not declare the required token — treat the SKILL.md/script as the source of truth. 3) The script only contacts api.github.com; if you want extra assurance, review the included scripts/github_tracker.py yourself or run the skill in a sandboxed agent first. 4) Use a least-privilege token (fine-grained, read-only for public repos) and consider setting SKILL_DATA_DIR to a directory you control. If any of these points are unacceptable, do not install or run the skill until the maintainer fixes the metadata and you have verified the code.
Capability Tags
requires-oauth-token
Capability Assessment
Purpose & Capability
Name/description align with the behavior: the script calls the GitHub REST API to fetch repo metrics and stores per-repo history. However, registry metadata lists no required credential while SKILL.md and the script require a GitHub Personal Access Token (GITHUB_TOKEN) — this mismatch is a packaging/metadata omission.
Instruction Scope
SKILL.md instructs only GitHub-related actions (setup, fetch, digest, add/remove/list). It documents credentials, data directory, and scheduling. It explicitly warns that tokens saved to disk are stored plaintext and offers env var use as an alternative. The runtime instructions and provided script do not attempt to read unrelated system files or exfiltrate data to endpoints other than api.github.com.
Install Mechanism
No install specification; the skill is instruction-only plus a Python script using only the standard library (urllib). No remote downloads or package installs are performed by the skill itself.
Credentials
The only secret required is a GitHub PAT, which is appropriate for the stated purpose. The script supports GITHUB_TOKEN env var or saving a token file. The registry metadata failing to declare this required credential is inconsistent and should be corrected. The skill stores the token in a JSON file (plaintext) under the data directory but sets file mode 600; SKILL.md recommends using the env var for higher security.
Persistence & Privilege
The skill persists data and credentials to a per-skill data directory (SKILL_DATA_DIR or ~/.config/github-growth-tracker/). It does not request permanent platform-wide privileges, does not set always:true, and does not modify other skills' configuration.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install github-growth-tracker
  3. After installation, invoke the skill by name or use /github-growth-tracker
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.4.0
Portable architecture: SKILL_DATA_DIR env var with XDG fallback, chmod 0600 on credentials, generic User-Agent, cross-agent compatibility
v1.3.1
v1.3.1: Added homepage link to source repository.
v1.3.0
v1.3.0: Rewritten SKILL.md for ClawHub readability. Added Why/When to Use sections. Commands and config as code blocks. Platform formatting moved to references/formatting.md. Tighter description with natural trigger phrases. Security note preserved. Brief Notes section for implementation details. 50% smaller SKILL.md with zero loss of LLM effectiveness.
v1.2.3
v1.2.3: Added source repository — https://github.com/99rebels/github-growth-tracker
v1.2.2
v1.2.2: Added security note acknowledging plaintext token storage and recommending GITHUB_TOKEN env var for higher security.
v1.2.1
v1.2.1: Clarified credential flow — credentials file is the primary method, env var is advanced option.
v1.2.0
v1.2.0: Security rework. Token stored in ~/.openclaw/credentials/github.json (outside workspace, follows OpenClaw convention). Config no longer contains secrets. Recommend fine-grained read-only token. GITHUB_TOKEN env var preferred over --token flag. Credential requirement declared in skill metadata.
v1.1.1
v1.1.1: Address ClawHub security review. Recommend fine-grained read-only token instead of classic repo scope. Prefer GITHUB_TOKEN env var over plaintext config storage. Document credentials requirements in SKILL.md.
v1.1.0
v1.1.0: Reworked from scratch. Removed auto-similar-repo comparison (was noisy). Replaced with user-curated watchlist. Digest auto-compares tracked repos vs watchlist average. Multi-repo add. Channel-aware formatting (Slack/Discord/WhatsApp). History trimmed to 90 days. Simplified to 6 commands: setup, fetch, digest, add, remove, list.
v1.0.0
Initial release of GitHub Growth Tracker - Track growth metrics (stars, forks, issues, commits, subscribers) for any GitHub repository over time. - Generate periodic digest reports with trend analysis using text and trend arrows (↑↓→). - Benchmark your repository against similar projects with automated comparisons. - Easily manage tracked repositories: add, remove, or list repos via commands. - Setup supports personal access tokens; data is saved outside the skill folder for persistence. - Supports scheduled monitoring and reporting via cron or heartbeat.
Metadata
Slug github-growth-tracker
Version 1.4.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 10
Frequently Asked Questions

What is Github Growth Tracker?

Track GitHub repo growth (stars, forks, issues, commits) with periodic digests and trend analysis. Compare your repos against a watchlist. Use when checking... It is an AI Agent Skill for Claude Code / OpenClaw, with 157 downloads so far.

How do I install Github Growth Tracker?

Run "/install github-growth-tracker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Github Growth Tracker free?

Yes, Github Growth Tracker is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Github Growth Tracker support?

Github Growth Tracker is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Github Growth Tracker?

It is built and maintained by 99rebels (@99rebels); the current version is v1.4.0.

💬 Comments