Agent skill · data analytics · nexu-io
github-dashboard
GitHub repository analytics dashboard — stars, forks, contributors, issues, pull requests, recent activity, and top contributors. Use when the brief asks for a GitHub repo dashboard, open-source growth report, repository health page, or GitHub analytics view.
Why this skill is useful
Provides specific commands and workflows for collecting and displaying GitHub repository analytics that the AI wouldn't reliably generate on its own.
What it needs
Requires github-cli installed locally. Requires github account access. About 4k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
GitHub Dashboard Skill Create a single-screen GitHub repository analytics dashboard in the FlowAI / Soft Paper Workspace visual style: warm off-white canvas, white rounded panels, a fixed left sidebar, compact KPI cards, pastel pills, dense tables, and low-contrast hairlines. Resource map When to use this skill Use this when the user asks for a dashboard or report about a single GitHub repository, for example: repository growth dashboard open-source project health report GitHub stars / forks / contributors analytics issue and pull-request activity page maintainer / contributor dashboard If the user asks for refreshability, source auditability, or scheduled updates, produce the live-artifact source set (template.html, data.json, artifact.json, provenance.json) and follow the live-artifact contract. If they only need a visual artifact, produce a self-contained index.html. Workflow 1. Resolve repository scope Parse owner/repo from the brief. This v1 skill is scoped to one repository. If multiple repositories are requested, ask the user to pick the primary repository or create one dashboard per repository. If the repo is missing, ask one concise question for the GitHub URL or owner/repo. 2. Collect public GitHub data Prefer GitHub CLI/API for public repository data when available. Current stars/forks/watchers/open issue count: GET /repos/{owner}/{repo} (stargazerscount, forkscount, watcherscount, openissuescount). Contributors: paginate GET /repos/{owner}/{repo}/contributors?perpage=100&page=N, sort by contributions descending, and take the top N used by the dashboard. If only page 1 is available, label totals as first-page estimates. Issues: use GitHub Search API (repo:{owner}/{repo} is:issue) for total counts, or paginate GET /repos/{owner}/{repo}/issues?state=all and filter out items with a pullrequest field. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/github-dashboard--f92643