菜单
Build a small dashboard over their real data. The three numbers that matter, updating when the data does. Use when they say "make a dashboard", keep re-computing the same numbers, or run a club or shop with data worth watching.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/protosphinx/sphinxstack --skill simple-dashboard命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | simple-dashboard |
| category | data |
| description | Build a small dashboard over their real data. The three numbers that matter, updating when the data does. Use when they say "make a dashboard", keep re-computing the same numbers, or run a club or shop with data worth watching. |
Build a small dashboard with someone, on top of data they already keep — their tracker sheet, shop sales, club attendance, game stats. A dashboard earns its name by being looked at repeatedly, so the whole design question is: which few numbers would they actually check next week? Three is the right count to start.
Ask what they would want to know at a glance on a random Tuesday. Push past vanity numbers to ones that change decisions: not "total rows logged" but "streak", "this week vs last week", "cash left this month", "sign-ups still unconfirmed". For each number, have them say what they would do differently if it looked bad. A number with no answer to that question gets cut. Write the three down with exact definitions (what counts, what date range) before building anything — vague definitions are how dashboards drift into lying.
Start in the sheet that already holds the data:
dashboard tab: the three numbers as big cells, computed by
formula from the data tab — never typed in by hand. SUMIF,
COUNTIF, and a date-window filter (this week, this month) cover
most of it.For many people the tab is the finished product. Stop here if so.
If the dashboard is for a team, a club, or their own phone home screen, put it at a URL. Keep it boring: publish the Google Sheet to the web and read it from a single static HTML page (fetch the published CSV, compute the three numbers in a few lines of JS, render big). Deploy on GitHub Pages (ship-on-github skill if present). The sheet stays the single source of truth; the page only reads. Check privacy before publishing: a public URL means public data, so if rows contain other people's names or money details, either keep it as a tab or publish only the aggregated numbers.
Repeated use is a follow-up success measure, not a setup claim. On the first review date, record whether the dashboard was current and what it changed.
Then: track-anything if the data feeding it is thin, or first-sql when the questions outgrow sheet formulas.