Name: Dashboard
Author: Iván

据 AlphaMoat 统计,截至 2026-09,Dashboard 累计下载 4,339 次、获 4 个星标,在全部 5,078 个 AI 技能中排名第 2,266 位,在「数据分析」分类(399 个)中排名第 181 位。

累计安装

126

累计下载

4,339

星标

全站排名

#2,266

全站前 45% · 「数据分析」前 46%

平台	累计安装	累计下载	星标	评论
ClawHub ↗	126	4,123	4	-
SkillHub ↗	121	4,339	4	—

各平台的计数口径不同,统计时间不一致。

这个技能是做什么的

它可创建静态 HTML 看板、配置与数据文件，并提供由用户手动或通过自己的定时任务运行的抓取脚本。代理不会自行执行自动抓取。凭据应由用户安全配置，不要写入公开页面或提交到代码库。保护本地数据，审查抓取脚本，联网开放前配置身份认证。

资料发布于 2026-10-29

可以用来做什么

根据用户提供的数据制作看板
生成可由用户运行的数据抓取脚本
检查本地看板的视觉呈现

什么时候用

需要构建本地数据看板时
执行抓取前由用户核对数据源、凭据、频率和存储位置

示例提示词

以下是根据技能文档生成的示例,不代表实际运行结果。

根据给定数据设计本地看板，并生成需要用户自行运行的抓取脚本及凭据安全说明。

月度数据趋势

累计下载4,339

星标4

2026-09 起统计方法调整:同名技能按作者分别统计,并覆盖全部技能。图中虚线为调整前的月份,与之后的数据不直接比较,也不计算跨越调整的增长。

月份	累计下载	环比	星标
2026-09	4,339	—	4
2026-08	3,935	+6.5%	4
2026-07	3,695	+18.1%	4
2026-06	3,129	+8.2%	3
2026-05	2,893	—	3
2026-03	1,820	—	2

SKILL.md 原文

以下是作者发布的原始文件,按纯文本显示,本站未做修改或审核;其中的链接不可点击,命令请核实后再运行。抓取于 2026-10-23。

2.6 KB · ClawHub v1.0.1

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

## Data Storage

展开全部(共 99 行)


```
~/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 ~/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

| Topic | File |
|-------|------|
| Data source patterns | `sources.md` |
| Visual design rules | `design.md` |
| Widget templates | `widgets.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: ~/dashboard/stripe/fetch.sh
→ User adds to cron: */15 * * * * ~/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
```bash
#!/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
```

### 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
| Element | Value |
|---------|-------|
| Background | `#0f172a` (dark) / `#f8fafc` (light) |
| Text | `#e2e8f0` (dark) / `#1e293b` (light) |
| Spacing | 16px, 24px, 32px |
| Corners | 8px |
| KPI | 48-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