L’interface est localisée ; les présentations et documents des Skills sont traduits automatiquement par IA dans votre langue. Le code, les commandes, chemins et termes techniques restent en version originale, et le document de l’auteur fait foi.
Explorer les Skills
Design et création · SKILL.md

Dashboard

Dashboard

Build custom dashboards from any data source with local hosting and visual QA loops.

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentation de la Skill

GitHub

name: Dashboard slug: dashboard version: 1.0.1 description: Build custom dashboards from any data source with local hosting and visual QA loops. homepage: https://clawic.com/skills/dashboard changelog: User-driven data source model, explicit credential handling metadata: clawdbot: emoji: 📊 requires: bins: [] os: - linux - darwin - win32 displayName: Dashboard

Data Storage

~/Clawic/data/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

Scope

This skill:

  • ✅ Generates static HTML dashboards
  • ✅ Creates fetch scripts user can run
  • ✅ Stores dashboards in ~/Clawic/data/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

Quick Reference

TopicFile
Data source patternssources.md
Visual design rulesdesign.md
Widget templateswidgets.md

Core Rules

1. User Provides Data

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: ~/Clawic/data/dashboard/stripe/fetch.sh
→ User adds to cron: */15 * * * * ~/Clawic/data/dashboard/stripe/fetch.sh

2. Architecture

[User's Cron] → [fetch.sh] → [data.json] → [index.html]
                    ↓
              Uses $API_KEY from env

Agent generates scripts. User runs them.

3. Fetch Script Template

#!/bin/bash
# Requires: STRIPE_API_KEY in environment
curl -s -u "$STRIPE_API_KEY:" \
  https://api.stripe.com/v1/balance \
  | jq '.' > ~/Clawic/data/dashboard/stripe/data.json

4. Visual QA (Before Delivery)

  • Open in browser, take screenshot
  • Check: no overlap, readable fonts (≥14px), good contrast
  • If issues → fix → repeat
  • Only deliver after visual validation

5. Design Defaults

ElementValue
Background#0f172a (dark) / #f8fafc (light)
Text#e2e8f0 (dark) / #1e293b (light)
Spacing16px, 24px, 32px
Corners8px
KPI48-72px number, 14px label

6. Security

  • 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
Skills enregistrées