Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build custom dashboards from any data source with local hosting and visual QA loops.
Build custom dashboards from any data source with local hosting and visual QA loops.
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.
~/dashboard/ ├── registry.json # Dashboard index ├── {name}/ │ ├── config.json # Layout, widgets │ ├── data.json # Current data │ └── index.html # Dashboard page Create on first use: mkdir -p ~/dashboard
This skill: ✅ Generates static HTML dashboards ✅ Creates fetch scripts user can run ✅ Stores dashboards in ~/dashboard/ User-driven model: User specifies data sources User provides API credentials via environment User runs fetch scripts (cron or manual) Skill generates HTML and fetch scripts This skill does NOT: ❌ Access credentials without user providing them ❌ Run automated fetches (user's cron runs scripts) ❌ Scrape services without user consent
TopicFileData source patternssources.mdVisual design rulesdesign.mdWidget templateswidgets.md
When creating a dashboard: User: "Dashboard for my Stripe revenue" Agent: "I'll create a fetch script. Set STRIPE_API_KEY in your environment, then run the script." → Generates: ~/dashboard/stripe/fetch.sh → User adds to cron: */15 * * * * ~/dashboard/stripe/fetch.sh
[User's Cron] → [fetch.sh] → [data.json] → [index.html] ↓ Uses $API_KEY from env Agent generates scripts. User runs them.
#!/bin/bash # Requires: STRIPE_API_KEY in environment curl -s -u "$STRIPE_API_KEY:" \ https://api.stripe.com/v1/balance \ | jq '.' > ~/dashboard/stripe/data.json
Open in browser, take screenshot Check: no overlap, readable fonts (≥14px), good contrast If issues → fix → repeat Only deliver after visual validation
ElementValueBackground#0f172a (dark) / #f8fafc (light)Text#e2e8f0 (dark) / #1e293b (light)Spacing16px, 24px, 32pxCorners8pxKPI48-72px number, 14px label
Credentials via env vars, never in files Dashboards on 127.0.0.1 by default No PII in displayed data User adds auth if exposing to network
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.