BlinkingSun

GitHub Web Skill — Git skill for Claude Code

Git community

Add your GitHub stats to your own website and keep them updated on a schedule by your coding agent — contribution heatmap, streaks, repo split bar and pinned cards with live star/fork counts.

How to install GitHub Web Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open BlinkingSun/github-web-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What GitHub Web Skill does

Add your GitHub stats to your own website and keep them updated on a schedule by your coding agent — contribution heatmap, streaks, repo split bar and pinned cards with live star/fork counts. Rendered to static HTML at build time: no client JS, no token in the browser.

Alternatives in Git

  • Star Us On GitHub — It helps us keep building 7k ★
  • Auteur — The Claude Code skill that directs a website like a film 1k ★
  • GitCommit — You are a commit message generator 250 ★

README

github-web

**Put your GitHub stats on your own website, and let your coding agent keep them current on a schedule.** Contribution heatmap, streaks and activity stats, a public/private repository split bar, and your pinned repo cards with live star and fork counts.

![The section, rendered](docs/screenshot.png)

Packaged as an **agent skill** — a `SKILL.md` your agent reads and follows. `/github-web` walks you through GitHub API access, installs the section into your page, and sets up the automatic refresh on whatever machine you have. Works with Claude Code, Cursor, the Grok CLI, or anything else that can read a skill file and run a shell. It is also a plain set of scripts — see [Without an agent](#without-an-agent).


What makes it different

**The data is rendered into static HTML at build time.** A Node script fetches from the GitHub GraphQL API and rewrites marked-up regions of your page in place. That means:

  • No client-side JavaScript. Works on a site with script-src 'none', and with JS disabled entirely.
  • No token in the browser. The credential never leaves the machine that runs the sync.
  • No API call per visitor. No rate limits, no latency, no third-party request from your reader's browser.
  • It is just HTML. Your page keeps working if this project disappears.

The trade-off is that it needs *something* to run on a schedule. That can be a server you own, or GitHub Actions for free — the package ships templates for both.


What it renders

Element Notes
53×7 contribution heatmap real daily counts, GitHub's own green ramp
Month labels derived from the data on every sync, each sized to its own week columns — never authored
12-month contribution total includes private contributions if your profile allows it
Current / longest streak counted to the last completed UTC day, so it never reads 0 mid-day
Busiest day, days with commits derived
Repository split bar public vs p