Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Automatically update a public dashboard with commit count, last commit, and timestamps from a private GitHub repo for transparent project progress.
Automatically update a public dashboard with commit count, last commit, and timestamps from a private GitHub repo for transparent project progress.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Scaffold a live public "build dashboard" that automatically shows proof of work โ commit count, last commit message, timestamp โ pulled from a private GitHub repo and displayed on a public static site.
Use this skill when you want to: Show your community what you're shipping, updated automatically on every push Build in public without exposing your private repo Add a community ideas board to let people vote on what you build next Create a polished /build page for your product or project
Private repo (your code) โโโ GitHub Actions: on push โ runs update-status.js โโโ Writes status.json โ commits to public site repo โโโ Public site fetches status.json every 60s โ displays live stats Result: every git push to your private repo automatically updates your public dashboard within minutes.
build-transparency-dashboard/ โโโ SKILL.md โ this file โโโ scripts/ โ โโโ update-status.js โ generates status.json from git log โ โโโ ideas-api.js โ Express routes for community ideas board โโโ assets/ โ โโโ build.html โ dashboard page template โ โโโ nav.js โ shared nav renderer (configurable) โ โโโ nav.css โ nav styles โ โโโ github-actions.yml โ GitHub Actions workflow template โโโ references/ โโโ setup-guide.md โ step-by-step setup instructions
In assets/build.html, search for these TODOs: TODOReplace WithYOUR_PROJECT_NAMEYour project's display name (e.g. MyApp)YOUR_BORN_DATEISO date your project started (e.g. 2026-01-01T00:00:00-05:00)YOUR_BRAND_COLORHex color (default: #7c6eff)YOUR_COIN_CAToken contract address, or remove the coin section entirelyYOUR_IDEAS_API_URLBase URL of your ideas API (e.g. https://myapp.fly.dev/public/ideas)YOUR_TWITTER_HANDLEYour @handle for the nav badgeYOUR_QUEUE_ITEMSWhat you're building next (edit the queue section) In assets/github-actions.yml, set these: VariableDescriptionSITE_REPOYour public site repo (e.g. username/my-site)SITE_REPO_PATHDirectory name for checkout (e.g. my-site)BOT_NAMECommitter name (e.g. StatusBot)BOT_EMAILCommitter email In assets/nav.js, edit the config object at the top: const NAV_CONFIG = { brand: 'MYAPP', // nav logo text links: [ { href: '/', label: 'Home' }, { href: '/build', label: 'The Build' }, ], badge: { label: '@yourhandle โ', href: 'https://x.com/yourhandle' }, };
Add to your private repo โ Settings โ Secrets and variables โ Actions: GH_PAT โ Personal Access Token with repo scope (to push to the public site repo)
The build.html file is a standalone static page. Deploy anywhere: Fly.io: fly launch + fly deploy in your site repo Netlify: drag & drop or connect repo GitHub Pages: push to a gh-pages branch Vercel: connect repo, zero config
The community ideas board requires a running API. Copy scripts/ideas-api.js into your backend app and mount the routes. It uses a flat JSON file for storage โ no database needed. Or skip it entirely: remove the coin/ideas section from build.html and it works as a pure static display.
Copy assets/github-actions.yml to .github/workflows/update-build-status.yml in your private repo. Push a commit โ the workflow fires automatically.
The workflow generates this file and commits it to your public site repo: { "generatedAt": "2026-02-28T21:00:00Z", "version": "1.0.0", "project": { "name": "MyApp", "description": "Your project description.", "born": "2026-01-01T00:00:00-05:00", "status": "building", "statusText": "Online ยท Building" }, "lastCommit": { "message": "feat: add dark mode", "time": "2026-02-28T20:55:00Z" }, "commitsThisWeek": 12, "shipped": [], "queue": [], "ideas": [] }
The template uses: Syne (display headings) + DM Sans (body) + DM Mono (mono/labels) Dark theme โ #050508 background, #7c6eff brand accent Noise overlay, animated orbs, fixed ticker bar Fully responsive (desktop โ tablet โ mobile) Swap --nova / --nova2 CSS vars for your brand color.
The pattern was built for novaiok-site.fly.dev/build. That's the reference implementation.
references/setup-guide.md โ detailed step-by-step with commands assets/build.html โ the template (search TODOs) assets/github-actions.yml โ the workflow
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.