Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nexu-io/github-dashboard
GitHub repository analytics dashboard — stars, forks, contributors, issues, pull requests, recent activity, and top contributors.
Passed 18 of 22 test cases with the skill, and 9 of 22 without it.
and 10 more in the full report
9 fixed9 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What CSS width specification should be set for the left navigation sidebar on desktop viewports? Should it be 200px or 300px?
| Checked | Without skill | With skill |
|---|---|---|
| Sidebar width is configured to exactly 256px. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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
Use this when the user asks for a dashboard or report about a single GitHub repository, for example:
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.
Resolve repository scope
owner/repo from the brief.owner/repo.Collect public GitHub data
GET /repos/{owner}/{repo} (stargazers_count, forks_count, watchers_count, open_issues_count).GET /repos/{owner}/{repo}/contributors?per_page=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.test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.