github-activity
Skill1 starsChanged 5 months agoMITView on GitHub
Add a live, self-built GitHub stats section to a site — headline stat cards (repos, total stars, followers, following), a "most used languages" bar computed by repo count with real GitHub language colors, and a top-repositories list. Pulls real data from GitHub's public REST API (no token), with loading skeletons, a session cache, and a graceful fallback if rate-limited. Use when the user wants to show GitHub stats/activity and is tired of the flaky third-party badge/image services (github-readme-stats, streak-stats) that rate-limit and look washed-out.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- xenodium/emacs-skillstheir own version, first seen Mar 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- xenodium/emacs-skills★ 142same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- ask-terminalSkill
- build-themeSkill
- command-paletteSkill
- deploy-doctorSkill
- llm-endpointSkill
- numu-AOV-themesSkill
- numu-store-founderSkill
- og-imageSkill
- scroll-reveal-kitSkill
- seo-kitSkill
- theme-toggleSkill
The file
Files
GitHub Activity (self-built, reliable)
A custom GitHub section that fetches real data from the public GitHub REST API and renders
it as themed, animated cards — instead of embedding the third-party github-readme-stats /
streak-stats images that constantly rate-limit ("Something went wrong! Could not fetch…") and
don't match your theme.
What it produces
GitHubActivity.tsx(<GitHubActivity username="..." />):- Headline stats (count-up animated): public repos, total stars (summed across non-fork repos), followers, following
- Most used languages — a segmented bar + legend with official GitHub language colors, computed by repo count (not byte count, so it won't over-report HTML/CSS the way github-readme-stats does)
- Top repositories — most-starred non-fork repos with language dot, ⭐ stars, forks
- Loading skeletons, a sessionStorage cache (one fetch per visit), and an error fallback link if GitHub's unauthenticated limit (60 req/hr/IP) is hit
How to use it
- Copy
references/GitHubActivity.tsxinto the components folder. - Render
<GitHubActivity username="your-github-username" />. - Deps:
framer-motion(reveal) andlucide-react(icons). Remove them by deleting themotion.*wrappers and swapping icons for emoji/SVG if you want zero deps. - Styling uses CSS-variable tokens (
--border,--card,--primary,--muted-foreground,--foreground) so it adapts to light/dark. Map them to your theme.
Notes / honesty
- It uses unauthenticated GitHub API calls — fine for a portfolio (cached per session). For heavy traffic or to add the contributions/streak heatmap (which needs the GraphQL API), proxy a GitHub token through a tiny serverless function so the token stays server-side.
- Numbers are real — stars/followers reflect the actual account, so it's honest, not inflated.
- The language breakdown is by repo count, which is more representative of what someone builds in than github-readme-stats' byte-count (which inflates generated HTML/CSS).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

