Data Storytelling
ynulihao/AgentSkillOS
Transform data into compelling narratives using visualization, context, and persuasive structure.
Design specifications for effective dashboards. An agent skill from nimrodfisher/data-analytics-skills.
Install Dashboard Specification
$ npx skills add nimrodfisher/data-analytics-skills --skill dashboard-specification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nimrodfisher/data-analytics-skills dashboard-specification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nimrodfisher/data-analytics-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/04-data-storytelling-visualization/dashboard-specification .claude/skills/dashboard-specification && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dashboard-specification" agent skill from https://github.com/nimrodfisher/data-analytics-skills/tree/main/04-data-storytelling-visualization/dashboard-specification into .claude/skills/dashboard-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dashboard-specification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nimrodfisher/data-analytics-skills/tree/main/04-data-storytelling-visualization/dashboard-specificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nimrodfisher/data-analytics-skills --skill dashboard-specification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nimrodfisher/data-analytics-skills dashboard-specification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nimrodfisher/data-analytics-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/04-data-storytelling-visualization/dashboard-specification .agents/skills/dashboard-specification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dashboard-specification" agent skill from https://github.com/nimrodfisher/data-analytics-skills/tree/main/04-data-storytelling-visualization/dashboard-specification into .agents/skills/dashboard-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dashboard-specification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nimrodfisher/data-analytics-skills --skill dashboard-specification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nimrodfisher/data-analytics-skills dashboard-specification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nimrodfisher/data-analytics-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/04-data-storytelling-visualization/dashboard-specification .cursor/skills/dashboard-specification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dashboard-specification" agent skill from https://github.com/nimrodfisher/data-analytics-skills/tree/main/04-data-storytelling-visualization/dashboard-specification into .cursor/skills/dashboard-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dashboard-specification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nimrodfisher/data-analytics-skills.git --path 04-data-storytelling-visualization/dashboard-specification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nimrodfisher/data-analytics-skills --skill dashboard-specification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nimrodfisher/data-analytics-skills dashboard-specification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nimrodfisher/data-analytics-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/04-data-storytelling-visualization/dashboard-specification .gemini/skills/dashboard-specification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dashboard-specification" agent skill from https://github.com/nimrodfisher/data-analytics-skills/tree/main/04-data-storytelling-visualization/dashboard-specification into .gemini/skills/dashboard-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dashboard-specification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nimrodfisher/data-analytics-skills dashboard-specificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nimrodfisher/data-analytics-skills --skill dashboard-specification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nimrodfisher/data-analytics-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/04-data-storytelling-visualization/dashboard-specification .github/skills/dashboard-specification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dashboard-specification" agent skill from https://github.com/nimrodfisher/data-analytics-skills/tree/main/04-data-storytelling-visualization/dashboard-specification into .github/skills/dashboard-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dashboard-specification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nimrodfisher/data-analytics-skills --skill dashboard-specification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nimrodfisher/data-analytics-skills dashboard-specification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nimrodfisher/data-analytics-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/04-data-storytelling-visualization/dashboard-specification .opencode/skills/dashboard-specification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dashboard-specification" agent skill from https://github.com/nimrodfisher/data-analytics-skills/tree/main/04-data-storytelling-visualization/dashboard-specification into .opencode/skills/dashboard-specification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dashboard-specification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dashboard-specification- GitHub stars
- 468
- Token cost
- ~741 tokens
- SKILL.md length
- 355 words
- Files
- 4 (incl. references, assets)
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design specifications for effective dashboards. An agent skill from nimrodfisher/data-analytics-skills.
- Works in 6 steps: Define the purpose — write one sentence:… → Profile target users — for each audience… → Define the metric hierarchy — list… → …
- Planning new dashboards
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Improving existing ones
What it does
Dashboard Specification is an agent skill from nimrodfisher/data-analytics-skills. Design specifications for effective dashboards. Use when planning new dashboards, improving existing ones, or documenting dashboard requirements before development starts.
Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files and assets (for example `assets/dashboard_spec_template.md`, `references/dashboard_design_principles.md` and `references/dashboard_requirements_guide.md`).
It sits in Writing & Content, covering Storytelling. The repository describes itself as: A comprehensive list of Claude & Codex skills for a wide range of data analytics tasks. The licence is MIT.
When your agent uses it
- Planning new dashboards
- Improving existing ones
- Documenting dashboard requirements before development starts
Example prompts
- “/dashboard-specification”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Define the purpose — write one sentence: "This dashboard answers [question] for [audience] who need to [decision or action]." If it can't…
- Profile target users — for each audience (executive, manager, IC), document their visit frequency, the primary question they come to…
- Define the metric hierarchy — list primary KPIs (hero numbers at the top), secondary supporting metrics, and detail-level breakdowns. A…
- Design the information architecture — sketch the layout using the hero → trends → breakdowns → details pattern. Position the most…
- Specify interactivity — list global filters (date range, region, segment), drill-down paths, click actions, and hover tooltip content…
- Document data requirements and success criteria — for each metric, record the source table, transformation logic, and refresh frequency…
What it can do on your machine
Read from SKILL.md and the folder at commit 9449d36. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dashboard Specification loads about 741 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 49 tokens; SKILL.md has 355 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nimrodfisher/data-analytics-skills at commit 9449d36, republished under its MIT licence (© nimrodfisher). 355 words, ~741 tokens.
Download SKILL.mdSave it as
.claude/skills/dashboard-specification/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- dashboard-specification
- description
- Design specifications for effective dashboards. Use when planning new dashboards, improving existing ones, or documenting dashboard requirements before development starts.
Dashboard Specification
When to use
- A new dashboard is being built and developers need a clear brief before starting
- An existing dashboard is confusing or underused and needs a structured redesign
- Stakeholders and the data team have different ideas about what a dashboard should show
- Documenting dashboard requirements as part of a broader data product process
- Creating a self-service analytics specification that can be handed off without multiple Q&A rounds
Process
- Define the purpose — write one sentence: "This dashboard answers [question] for [audience] who need to [decision or action]." If it can't be stated in one sentence, the scope needs narrowing first. See
references/dashboard_design_principles.md. - Profile target users — for each audience (executive, manager, IC), document their visit frequency, the primary question they come to answer, and their technical comfort level. Users with different needs usually need different dashboards, not more filters on one.
- Define the metric hierarchy — list primary KPIs (hero numbers at the top), secondary supporting metrics, and detail-level breakdowns. A dashboard with more than 10–12 distinct metrics is trying to do too much.
- Design the information architecture — sketch the layout using the hero → trends → breakdowns → details pattern. Position the most important information in the top-left. Use
references/dashboard_requirements_guide.mdfor layout patterns. - Specify interactivity — list global filters (date range, region, segment), drill-down paths, click actions, and hover tooltip content. Every filter and drill-down adds complexity; justify each one.
- Document data requirements and success criteria — for each metric, record the source table, transformation logic, and refresh frequency. Define how dashboard success will be measured (adoption rate, reduction in ad-hoc requests). Complete
assets/dashboard_spec_template.md.
Show full SKILL.md (89 more words)Show less
Inputs the skill needs
- The business question the dashboard is meant to answer
- A list of candidate metrics (team can provide a rough list; you'll curate it)
- The primary audience (role, visit frequency, decision they make)
- Data availability: confirmed source tables and refresh schedules
- Any constraints: tool (Tableau, Looker, Metabase, etc.), branding guidelines
Output
references/dashboard_design_principles.md— layout hierarchy, chart selection, information density guidelinesreferences/dashboard_requirements_guide.md— how to run requirements gathering, avoid scope creep, and validate the specassets/dashboard_spec_template.md— complete spec: purpose, users, metric hierarchy, layout wireframe, interactivity, data sources, success criteria
© nimrodfisher, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references, assets) in 04-data-storytelling-visualization/dashboard-specification of nimrodfisher/data-analytics-skills.
- SKILL.md
- assets/dashboard_spec_template.md
- references/dashboard_design_principles.md
- references/dashboard_requirements_guide.md
Open the folder on GitHubat commit 9449d36
Compare with similar skills
Dashboard Specification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dashboard Specification this skillnimrodfisher/data-analytics-skills | 468 | — | ~741 | Automated safety check: Pass | MIT | |
| Data Storytellingynulihao/AgentSkillOS | 617 | 15 repos | ~2.8k | Automated safety check: Pass | None | |
| Chinese Novel Writing Systemleenbj/novel-creator-skill | 668 | — | ~3.9k | Automated safety check: Pass | None | |
| Chinese Novelist Chapter WriterPenglongHuang/chinese-novelist-skill | 3.3k | — | ~491 | Automated safety check: Warn | MIT | |
| Liu Run Style Business Column Writerliangdabiao/liurun-bookwriter-skills | 275 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Business Insight Essay Writerliangdabiao/liurun-bookwriter-skills | 275 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Chinese Novel Writing System
leenbj/novel-creator-skill
Guides long-form Chinese novel writing from a rough idea through outlines, chapter drafts and quality gates, with file-based memory for a story meant to reach 300万字.
Chinese Novelist Chapter Writer
PenglongHuang/chinese-novelist-skill
Writes long Chinese novels chapter by chapter through guided questions, outlining, drafting with cliffhangers and automatic validation, with resumable projects.
Liu Run Style Business Column Writer
liangdabiao/liurun-bookwriter-skills
Writes long-form Chinese business commentary in Liu Run's voice, using his eight writing principles, three structures, and SCQA logic patterns.
Business Insight Essay Writer
liangdabiao/liurun-bookwriter-skills
Drafts Chinese business-insight essays, short audio scripts and year-end speeches in a specific public commentator's rhythm, built from his books, talks and broadcasts.
Shakespeare Writing Studio
ZCZHAO-1999/shakespeare-writing-studio
Produce publish-ready Chinese and English writing packages across WeChat articles, Medium/Substack essays, research notes, founder memos, op-eds, speeches, data storytelling, statistical graphics…
More from nimrodfisher/data-analytics-skills
All 31 skills in this repoAb Test Analysis
nimrodfisher/data-analytics-skills
Rigorous A/B test statistical analysis. An agent skill from nimrodfisher/data-analytics-skills.
Analysis Assumptions Log
nimrodfisher/data-analytics-skills
Track and document analytical assumptions and decisions. An agent skill from nimrodfisher/data-analytics-skills.
Analysis QA Checklist
nimrodfisher/data-analytics-skills
Pre-delivery quality assurance for analysis work. An agent skill from nimrodfisher/data-analytics-skills.
Business Metrics Calculator
nimrodfisher/data-analytics-skills
Standard business metric calculation with industry benchmarks.
Cohort Analysis
nimrodfisher/data-analytics-skills
Time-based cohort analysis with retention and behaviour tracking.
Context Packager
nimrodfisher/data-analytics-skills
Efficiently package context for AI-assisted analysis. An agent skill from nimrodfisher/data-analytics-skills.
Related
Categories
Questions about Dashboard Specification
What does Dashboard Specification do?
Design specifications for effective dashboards. An agent skill from nimrodfisher/data-analytics-skills. Dashboard Specification is an agent skill from nimrodfisher/data-analytics-skills. Design specifications for effective dashboards.
When should I use Dashboard Specification?
Dashboard Specification fits situations like: planning new dashboards; improving existing ones; documenting dashboard requirements before development starts.
How do I install Dashboard Specification in Claude Code?
Run `npx skills add nimrodfisher/data-analytics-skills --skill dashboard-specification -a claude-code`. Or copy the skill folder (04-data-storytelling-visualization/dashboard-specification in nimrodfisher/data-analytics-skills) into .claude/skills/dashboard-specification in your project. Claude Code loads it when a task matches its description.
How do I install Dashboard Specification in Codex?
Run `npx skills add nimrodfisher/data-analytics-skills --skill dashboard-specification -a codex`. Or copy the skill folder (04-data-storytelling-visualization/dashboard-specification in nimrodfisher/data-analytics-skills) into .agents/skills/dashboard-specification in your project. Codex loads it when a task matches its description.
Can I use Dashboard Specification in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nimrodfisher/data-analytics-skills --skill dashboard-specification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dashboard-specification, .gemini/skills/dashboard-specification, .github/skills/dashboard-specification and .opencode/skills/dashboard-specification in your project.
What does Dashboard Specification need to run?
SKILL.md names no scripts, command-line tools or credentials: Dashboard Specification is instructions for the agent only.
Does Dashboard Specification access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Dashboard Specification safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dashboard Specification use?
Dashboard Specification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dashboard Specification use?
About 741 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.
What are the alternatives to Dashboard Specification?
Skills that share tags, products or a category with Dashboard Specification: Data Storytelling (ynulihao/AgentSkillOS, 617 stars), Chinese Novel Writing System (leenbj/novel-creator-skill, 668 stars), Chinese Novelist Chapter Writer (PenglongHuang/chinese-novelist-skill, 3.3k stars) and Liu Run Style Business Column Writer (liangdabiao/liurun-bookwriter-skills, 275 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dashboard Specification?
nimrodfisher (a GitHub user) maintains it in nimrodfisher/data-analytics-skills, which has 468 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on September 25, 2026.
Source: nimrodfisher/data-analytics-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.