dashboard-design
Skill2 starsChanged 4 months agoApache-2.0View on GitHub
Design a Power BI dashboard FROM approved metric contracts in the Seshat BI repo. Use when someone asks to design a report/page, bind visuals to metrics, or produce a dashboard layout for a subject area whose semantic model is ready. This skill is HARD-GATED on semantic_model_ready: pass (no approved metric contracts -> no design); it authors reviewable design guidance only -- a layout plan, a visual list, and a visual->contract binding map where every visual binds to exactly one approved contract. It NEVER invents a metric, NEVER publishes, NEVER opens Power BI Desktop or a DB connection, and NEVER calls the Power BI execution adapter (official Power BI MCP / connection; `pbi-cli` no longer preferred) -- that is feature F016. It authors, runs static seshat check, records dashboard_ready at most as warning, and STOPS.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- adymire/CraftLayertheir own version, first seen Nov 15, 2026
- dmoreq/precepttheir own version, first seen Nov 15, 2026
- RobertoDominguezCampo/lumio-skillstheir own version, first seen Nov 15, 2026
- xsovad06/sovatheir own version, first seen Nov 14, 2026
- thensls/nsls-builder-toolkittheir own version, first seen Nov 13, 2026
- oleg494/coding-kittheir own version, first seen Nov 8, 2026
Used with
Projects with it also use data-visualization, motion-design and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkilldata-visualization
Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.
Also in 4 projects that use this
soilmassSkillmotion-design
Create animations and motion graphics using industry standards. Use when asked to animate UI elements, create video content, implement transitions, or build motion systems. Implements W3C Design Tokens, Material Design 3 baseline, and Lottie specification compliance.
Also in 3 projects that use this
AnthropicSkilldesign-system
Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.
Also in 4 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- abdiraimov-otabek/dashboard-design-skill★ 474same name
- ArnavPuri/designskills★ 17same name
- YepAPI/skills★ 8same name
- Marvellbrazil/my-agentic-skills★ 4same name
- oleg494/coding-kit★ 3same name
- xsovad06/sova★ 3same name
- gmanch94/claude-code-aidlc-template★ 2same name
- RobertoDominguezCampo/lumio-skills★ 2same name
- valewnrt/design-skills★ 2same name
- tines/skills★ 1same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- approval-consoleSkill
- approval-evidence-packSkill
- business-knowledge-interviewSkill
- capabilitiesSkill
- consumer-data-dictionarySkill
- cross-table-lineageSkill
- dagster-orchestration-adapterSkill
- dashboard-intelligenceSkill
- dbt-transformation-adapterSkill
- evidence-pack-generatorSkill
- first-hour-compassSkill
- friendly-pr-reviewerSkill
- grain-confidence-reviewerSkill
- kpi-contract-builderSkill
- pbi-mcp-write-adapterSkill
- pbip-workflowSkill
- pbip-xraySkill
- pbir-authoring-adapterSkill
- portfolio-watchSkill
- powerbi-dashboard-designSkill
- pr-readiness-reviewerSkill
- readiness-viewerSkill
- release-notes-generatorSkill
- report-intent-interviewSkill
- retail-build-warehouseSkill
- retail-control-roomSkill
- retail-discover-portfolioSkill
- retail-governSkill
- retail-initSkill
- retail-onboard-tableSkill
- retail-orchestrateSkill
- retail-scaffoldSkill
- retail-semantic-checkSkill
- retail-validateSkill
- run-next-readinessSkill
- seshat-studioSkill
- showcase-buildSkill
- source-mappingSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- bi-analyst-knowledgeSkill
- bi-bigdata-knowledgeSkill
- bi-dax-knowledgeSkill
- bi-python-knowledgeSkill
- bi-sql-knowledgeSkill
- retail-kpi-knowledgeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
27 rules. 0 are common, 10 are distinctive, and 17 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
17
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 49
Before authoring ANY design, read the subject area's readiness status and verify semantic_model_ready: pass.
- Very specific: line 55
If semantic_model_ready is anything other than pass -- not_started, blocked, or warning -- the gate FAILS.
- Very specific: line 97
If any precondition fails, record the matching dashboard_ready status + blocking reason and STOP.
- Very specific: line 102
Before authoring any layout, read mappings/<table>/narrative-brief.md.
- Very specific: line 116
Read the approved metric contracts (each: name, grain, formula intent, owner + approval) and the business questions the page must answer.
- Very specific: line 151
No orphan visual, either direction (FR-005): every visual MUST bind to one approved contract (present + declared in the brief) AND name >=1 …
- Distinctive: line 156
No unanswered question (FR-005): every ranked brief decision-question MUST be answered by >=1 visual.
- Distinctive: line 159
No page serves nothing: every declared page carries >=1 question-bearing visual.
- Very specific: line 161
No bare-total headline (FR-006): every headline: true (KPI-card class) visual MUST answer at least one stage: overview question.
- Distinctive: line 167
If more approved contracts exist than visuals on the page, record each DROPPED contract with a reason (e.g.
- Very specific: line 173
Before requesting the design review, run seshat narrative-check --table <table> (the brief) and seshat narrative-check --table <table> …
- Distinctive: line 177
STOP: fix the brief/map and re-run.
- Very specific: line 188
Stop at the design-review boundary.
- Very specific: line 194
When a committed PBIR report exists for the subject area, confirm seshat check (rule R1) stays exit 0 -- the report references the governed …
- Very specific: line 204
No committed narrative-brief.md (the narrative gate -- narrative_brief_missing).
- Distinctive: line 237
More approved contracts than visuals: not every contract must appear on the page, but each dropped contract MUST be recorded with a reason …
- Distinctive: line 243
A contract exists but is not approved: treat only APPROVED contracts as bindable -> the visual is an orphan -> STOP.
- Distinctive: line 253
Do NOT invent, define, or alter a metric at design time -- only bind to approved contracts (metric definition is F009).
- Very specific: line 255
Do NOT author any layout before a committed narrative-brief.md exists (the narrative gate, FR-004) -- the brief supplies the …
- Very specific: line 258
Do NOT emit a visual that answers no brief decision-question (narrative orphan), nor a headline visual that answers no overview question …
- Very specific: line 260
Do NOT design any visual before its metric contract exists / before semantic_model_ready: pass (rule 5).
- Very specific: line 262
Do NOT call the Power BI execution adapter (official Power BI MCP / connection.
- Distinctive: line 265
Do NOT open a DB or Power BI Desktop connection.
- Very specific: line 266
Do NOT self-grant dashboard_ready: pass -- the highest this skill records is warning.
- Distinctive: line 268
Do NOT fabricate a confidence score -- use the four statuses + evidence + blockers.
- Distinctive: line 269
Do NOT bake any real connection host or secret into any output (G6).
- Very specific: line 299
When a table is driven end-to-end, the retail-orchestrate conductor sequences this verb after semantic_model_ready is pass and runs the …
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
dashboard-design
Stage 6 of the Tower BI Readiness System, Dashboard Ready
(docs/readiness/dashboard-ready.md):
a report is designed AGAINST approved metric contracts -- never before them. This
skill is the agent VERB that runs that stage. It reads the approved metric
contracts (F009) and the governed PBIP model (F010), then authors a layout plan, a
visual list, and a visual->contract binding map so every visual traces to a
contract that already exists and is approved. It is the agent expression of roadmap
hard rule 5 ("no dashboard design before metric contracts") and hard rule 6 ("no
Power BI execution before semantic-model readiness").
This verb is the gated, contract-binding design step that the broader
powerbi-dashboard-design router (F011A, the visual-design FOUNDATION) hands the
"design a dashboard from approved contracts" intent to. The router carries the
design vocabulary (four surfaces, tokens, theme, blueprints, QA); this verb enforces
the gate and produces the binding map a human signs off.
Scope boundary (read first)
This skill AUTHORS design guidance and STOPS. Authoring is in-scope: a layout plan,
a visual list, a visual->contract binding map, and (optionally) a blank PBIR
scaffold a human fills -- no side effects, no DB/Desktop connection, the same
category as source-mapping authoring mappings/ and retail-build-warehouse
authoring warehouse/migrations/*.sql. EXECUTING the design -- generating the PBIR
report, publishing to a workspace, calling the Power BI execution adapter (official
Power BI MCP / connection; pbi-cli no longer preferred) -- is the deferred,
execution-only F016 adapter seam and is OUT of scope here. The skill authors, runs
static seshat check on any committed report text, and STOPS.
Hard gate (rule 5) -- verify BEFORE authoring anything
Before authoring ANY design, read the subject area's readiness status and verify
semantic_model_ready: pass. "Pass" means BOTH:
- approved metric contracts exist (F009) -- each carries a recorded approval; and
- the governed PBIP model binds each measure to one (F010).
If semantic_model_ready is anything other than pass -- not_started,
blocked, or warning -- the gate FAILS. Author no design, record
dashboard_ready: not_started (the prior stage is not pass) with the concrete
blocking reason, and STOP. A warning prior stage does NOT authorize design (the
thing being awaited is exactly the contract approval). Never invent a metric to
fill a visual when the gate is not pass.
This skill reads the gate; it does NOT re-derive contract approval
(readiness-pipeline.md: "pass"
of the prior stage is the entry condition).
Design vs execution boundary (rule 6)
| In scope (design authoring) | Out of scope (execution owner) |
| layout plan, visual list, visual->contract binding map | native PBIR authoring: official powerbi-report-authoring after the gate |
| optional blank PBIR scaffold a human fills | opening Power BI Desktop or a DB connection |
running static seshat check on committed report text | calling the Power BI execution adapter (official Power BI MCP / connection) |
recording dashboard_ready: warning + evidence | publishing to a workspace / refreshing a model |
The skill authors, checks, and STOPS. Route native PBIR implementation through
powerbi-workflows to Microsoft's official report-authoring skill when
discoverable. Route live semantic-model connection/refresh/query/publish to the
separately parked F016 adapter. Never collapse these owners.
Preconditions (STOP unless ALL hold)
semantic_model_ready: passfor the subject area (the hard gate above).- Approved metric contracts (F009) are readable and each carries a recorded approval (an unapproved-but-present contract is NOT a valid binding target).
- The governed PBIP model (F010) is present and binds measures to those contracts.
- The analyst has supplied the business questions the page must answer. This is a Principle V input -- if missing, ASK for it; do NOT invent a generic page.
- A committed narrative brief exists at
mappings/<table>/narrative-brief.mdconforming to the frozenseshat.narrative-brief/v1schema (bi-analyst-knowledgederivation route). This is the NEW narrative gate (spec 021, FR-004): a design that binds visuals to contracts but cannot say which owner decision each page serves is itself a gap. The brief must exist and be committed BEFORE any layout/visual guidance is authored, exactly as contracts must exist before design. Its ABSENCE is a NAMED BLOCKER, not a warning -- author no layout, record the blocking reason, and STOP.
If any precondition fails, record the matching dashboard_ready status + blocking
reason and STOP.
The narrative gate (rule: no layout before narrative)
Before authoring any layout, read mappings/<table>/narrative-brief.md. If it is
absent, author no design and STOP with the named blocker
narrative_brief_missing (next_action: "author the narrative brief via
bi-analyst-knowledge (the derivation route) and get it committed first"). The
brief supplies the ranked owner decision-questions (each with a stable id Q1,
Q2, ...) that the three-way binding map below binds every visual to. Frame the
analysis, never invent it: the brief cites only approved contracts + the profiled
source; a question the data cannot answer is a [GAP] in the brief, never a
visual. This skill does NOT author the brief -- that is the bi-analyst-knowledge
route's job; this skill CONSUMES it.
Procedure (numbered; do not reorder)
1. Read inputs
Read the approved metric contracts (each: name, grain, formula intent, owner +
approval) and the business questions the page must answer. Confirm the governed
model is semantic_model_ready: pass.
2. Author the layout plan
Author the page/section structure as reviewable text: which business questions the
page answers, in what reading order, one question per region. (For the section
vocabulary -- header / KPI strip / main insight / diagnostic / exception-detail /
filter rail / footer-status -- and design principles, use the F011A foundation:
docs/powerbi/visual-design-system.md and
../powerbi-dashboard-design/workflows/page-blueprint.md.)
3. Author the visual list
For each proposed visual record: its type, the ONE approved metric contract it
binds to, AND the brief decision-question(s) it answers (by id -- Q1, Q5, ...).
Choose the visual type to fit the contract's GRAIN (a single additive measure ->
KPI card; a measure by a dimension -> bar/column; a measure over time -> line;
row-level detail -> table). Two things a visual MUST NOT be: with no backing
approved contract (an unbound orphan), or answering no brief decision-question (a
narrative orphan) -- both are defects (see Blocking reasons).
4. Author the three-way visual -> contract -> decision-question binding map
Author the committed note proving each visual binds to exactly one approved contract AND answers at least one brief decision-question. This is the THREE-WAY map (spec 021, FR-005): the F011 two-way map (visual -> contract) extended with the decision-question leg. It is the artifact the design review signs off.
Give the map a machine-readable seshat.binding-map/v1 fenced-yaml front section
(mirroring the brief) so seshat narrative-check --binding-map can read it. Each
visual records: visual_id, page, region, visual_type, contract
(approved), decision_questions (a LIST of brief question ids -- one visual may
answer more than one owner decision, e.g. a basket-value card that is both a
headline number and the basket-value answer), and headline (true for KPI-card
class). Rules the map obeys, each an orphan/coverage defect:
- No orphan visual, either direction (FR-005): every visual MUST bind to one
approved
contract(present + declared in the brief) AND name >=1decision_questionsentry, each a question the brief declares. A visual missing either leg -- an undeclared/absent contract, or answering no owner decision -- is an orphan. - No unanswered question (FR-005): every ranked brief decision-question MUST be answered by >=1 visual. A decision the design declares but serves no visual for is an orphan question.
- No page serves nothing: every declared page carries >=1 question-bearing visual.
- No bare-total headline (FR-006): every
headline: true(KPI-card class) visual MUST answer at least onestage: overviewquestion. Because the brief forces every overview question to name acomparison(never "none"), this is how "the headline carries a comparison" is enforced -- a bare total on a headline is a defect; offer the framing catalog's comparisons as the fix.
If more approved contracts exist than visuals on the page, record each DROPPED
contract with a reason (e.g. "covered by the Stage 7 handoff pack, not the
dashboard") -- never a silent omission. The generic taught shape lives in
bi-analyst-knowledge/example-specialty-retail.md (the three-way map section).
4a. Run the read-only narrative check (evidence for the review)
Before requesting the design review, run seshat narrative-check --table <table>
(the brief) and seshat narrative-check --table <table> --binding-map (the
three-way map). Both are READ-ONLY, categorical, and grant NO approval -- a clean
check is EVIDENCE for the human review, never a substitute for it. A finding is a
STOP: fix the brief/map and re-run. A missing/malformed brief or map fails closed
(named blocker), never a silent pass.
5. Record readiness (warning, never pass)
Record dashboard_ready: warning with evidence[] (the committed layout plan +
visual list + binding map) and next_action: "get the design review
(visual->contract binding) signed off by the BI report owner". Use the four
statuses only (not_started / blocked / warning / pass) -- NEVER a numeric
confidence score.
6. STOP
Stop at the design-review boundary. The skill never writes dashboard_ready: pass
itself (see No self-granted pass). Hand the design to the BI report owner for the
visual->contract binding review.
R1 / relative-reference note
When a committed PBIR report exists for the subject area, confirm seshat check
(rule R1) stays exit 0 -- the report references the governed model by a RELATIVE
path, not an absolute/remote ref. On failure, record dashboard_ready: blocked
with the reason ("PBIR references the model by absolute/remote path -- R1 fails")
and STOP; the relative-reference fix is the human's. This skill reuses the existing
R1 rule; it adds no new seshat check rule.
Blocking reasons (each maps to a STOP)
semantic_model_readyis notpass(the hard gate -- contracts must exist first).- No committed
narrative-brief.md(the narrative gate --narrative_brief_missing). - A visual has no backing approved metric contract, or one not declared in the brief (unbound orphan visual, FR-005).
- A visual answers no brief decision-question, or an undeclared one (narrative orphan visual, FR-005).
- A brief decision-question is answered by no visual (unanswered question, FR-005).
- A declared page carries no question-bearing visual (page serves no decision).
- A headline (KPI-card class) visual answers no
overviewquestion -- a bare total on the headline (FR-006). - A metric is invented at design time instead of reusing an approved contract.
- The PBIR references the model by an absolute/remote path (R1 fails).
No invented metrics
The skill binds ONLY to existing approved contracts. It NEVER defines, alters, or
invents a metric -- metric definition is F009's job, not this skill's. An
unapproved-but-present contract is not a valid binding target; a visual that would
need it is an orphan -> STOP. If a needed metric does not exist as an approved
contract, the gap is recorded ("orphan visual: no approved contract for
<question>") and the skill STOPS rather than inventing one.
No self-granted pass
The skill NEVER writes dashboard_ready: pass. The highest status it records is
warning, with next_action: "get the design review (visual->contract binding)
signed off by the BI report owner". A pass requires an approvals[] entry --
{stage: dashboard_ready, owner: <bi-report-owner>, at: <date>} -- written by the
REVIEWER, not by this skill. When that approval is recorded by the reviewer,
dashboard_ready may become pass and next_action points to Stage 7
(publish-ready.md).
Edge cases
- More approved contracts than visuals: not every contract must appear on the page, but each dropped contract MUST be recorded with a reason -- no silent omission.
- Grain mismatch (e.g. a row-level contract asked to be a single KPI card):
record a
warning-class design note, propose the grain-appropriate visual, and never silently mis-bind. - A contract exists but is not approved: treat only APPROVED contracts as bindable -> the visual is an orphan -> STOP.
- Subject area spans multiple tables/models: bind visuals only to contracts
within the governed model(s) that are
semantic_model_ready: pass; a visual needing an out-of-model metric is an orphan -> STOP. - No business questions supplied: design is question-driven -- ASK for the questions (a Principle V input); do not invent a generic page.
What the agent must NOT do
- Do NOT invent, define, or alter a metric at design time -- only bind to approved contracts (metric definition is F009).
- Do NOT author any layout before a committed
narrative-brief.mdexists (the narrative gate, FR-004) -- the brief supplies the decision-questions the map binds to; author the brief viabi-analyst-knowledgefirst. - Do NOT emit a visual that answers no brief decision-question (narrative orphan),
nor a headline visual that answers no
overviewquestion (bare-total headline). - Do NOT design any visual before its metric contract exists / before
semantic_model_ready: pass(rule 5). - Do NOT call the Power BI execution adapter (official Power BI MCP / connection;
pbi-clino longer preferred), generate or publish the PBIR, or refresh a model -- that is feature F016 (rule 6), execution-only and gated. - Do NOT open a DB or Power BI Desktop connection.
- Do NOT self-grant
dashboard_ready: pass-- the highest this skill records iswarning;passneeds the reviewer'sapprovals[]entry. - Do NOT fabricate a confidence score -- use the four statuses + evidence + blockers.
- Do NOT bake any real connection host or secret into any output (G6).
Generic, not C086
This skill and any template scaffold it uses are GENERIC (roadmap rule 7). No C086/pharmacy specifics (billing codes, segment rollups, insurance/PII columns, pharmacy grain keys, real metric names) appear in the skill text or any committed template. Worked values belong only to a per-subject-area instance; C086 is the first worked example, not the schema (Principle VII).
See also
- The stage contract:
docs/readiness/dashboard-ready.md. - The prior stage / gate:
docs/readiness/semantic-model-ready.md. - Status + evidence + blockers:
docs/readiness/readiness-model.md. - Hard rules 5/6/7/8:
docs/roadmap/roadmap.md. - The visual-design FOUNDATION this verb reasons with: the
powerbi-dashboard-designrouter skill +docs/powerbi/+templates/+design/+themes/+reports/blueprints/(F011A). - The narrative gate + framing catalog (spec 021): the
bi-analyst-knowledgepack (INDEX.md,derivation-route.md, the eightframing-*.mdcards,story-order.md, and the worked examples). The brief this skill consumes is authored via that route. - The read-only evidence surface:
seshat narrative-check --table <t>(brief) andseshat narrative-check --table <t> --binding-map(three-way map). - Generic scaffolds:
templates/dashboard-layout.md,templates/visual-contract-binding-map.md.
Orchestration
When a table is driven end-to-end, the retail-orchestrate conductor sequences
this verb after semantic_model_ready is pass and runs the self-heal loop
against the gate exit code. This skill stays single-purpose: it authors the design,
records dashboard_ready: warning, and STOPS at the human design-review boundary.
The loop lives only in retail-orchestrate, never here.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

