- name
- github-dashboard
- description
- 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.
- triggers
- - "github dashboard" - "repo dashboard" - "repository dashboard" - "github analytics" - "open source dashboard" - "github growth" - "仓库看板" - "GitHub 看板"
- od
- mode: prototype platform: desktop scenario: operation preview: type: html entry: index.html design_system: requires: true sections: [color, typography, layout, components] outputs: primary: index.html secondary: - template.html - data.json - artifact.json - provenance.json capabilities_required: - shell - file_write example_prompt: "Build a GitHub dashboard for nexu-io/open-design — stars, forks, contributors, issues, PRs, recent activity, and top contributors."
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
-
Resolve repository scope
- Parse
owner/repofrom 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.
- Parse
-
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}(stargazers_count,forks_count,watchers_count,open_issues_count).