Skills

GitHub Repository Dashboard

Builds a repo analytics page with stars, forks, contributors, issues and pull requests.

Install

npx skills add nexu-io/open-design --skill github-dashboard -g -a claude-code -y
Repository
nexu-io/open-design105k
Category
Engineering
Updated
3d ago
License
Apache-2.0
Context cost
Mediumabout 1,563 tokens
Runs scripts
No, instructions only

What it does

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.

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

github-dashboard/
├── SKILL.md
├── example.html                         ← rendered reference dashboard
└── references/
    ├── template.html                    ← live-artifact-compatible HTML template
    ├── example-data.json                ← normalized public GitHub data shape
    ├── artifact-example.json            ← minimal live-artifact create input
    └── provenance-example.json          ← safe source/provenance example

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.
Read the whole SKILL.md on GitHub

More in Engineering