Skip to content

GitHub Repo Dashboard

Builds a single-screen analytics dashboard for one GitHub repository's stars, forks, contributors, issues and PRs.

Stars
105,448
Licence
Apache-2.0
Files
7 files

What it does

When installed, the agent can turn a request about one GitHub repository into a styled HTML dashboard showing key counts (stars, forks, contributors, open issues, pull requests), top contributors, and recent activity. It is told to pull public data from GitHub's API or CLI, tidy it into a fixed data shape, and produce either a standalone index.html page or a set of files (template, data, artifact and provenance records) for a refreshable version. It also tells the agent to note where any numbers are estimated or synthetic.

Great for

  • Maintainers who want a quick health or growth overview of their open-source project
  • Developer advocates or community managers preparing a repository status page
  • Anyone who needs a clean, read-only visual report of a single public GitHub repo

Skip it if

  • Comparing several repositories at once, since the skill is explicitly scoped to one repo per dashboard (the skill itself says so)
  • Precise historical star or fork growth, because GitHub's REST API does not expose complete history and the skill allows estimated or synthetic chart data
  • Private repositories or anything needing authenticated private metadata, since the skill says not to store tokens or private metadata and is built around public data

Try asking

  • “Build a GitHub dashboard for nexu-io/open-design showing stars, forks, contributors, issues, PRs and recent activity”
  • “Make a repository health page for owner/repo with top contributors”
  • “Create a refreshable open-source growth report for my project that I can update later”
Step-by-step guide: how to use GitHub Repo DashboardInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 7 original files, the Apache-2.0 licence and an attribution note.

    github-dashboard.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip github-dashboard.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip github-dashboard.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give the full owner/repo name so the agent does not need to ask a follow-up question
  • Ask for a live artifact if you want to refresh the data later; otherwise a static index.html is produced
  • Check provenance notes before sharing, especially any growth figures marked as estimated

What's inside

  • example.html
  • references/artifact-example.json
  • references/example-data.json
  • references/provenance-example.json
  • references/README.md
  • references/template.html
  • SKILL.md

Redistributed unmodified from nexu-io/open-design under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.