build-dashboard

Build a source-backed dashboard or monitoring view with clear metrics, filters, visual hierarchy, definitions, refresh context, and QA.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/opencode/src/skill/builtin/.bundle/data-analytics/workflows/build-dashboard/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-sequenced with strong validation and QA steps, but it is not self-containedly actionable because it points to specification files that are absent from the bundle. Adding or inlining the referenced specs would resolve the two lowest dimensions.

Suggestions

Ship the referenced specification files (specifications/streamlit-dashboard.md and specifications/html-dashboard.md) in the bundle, or inline the key build steps so the skill is actionable without missing dependencies.

Verify that ../visualize-data/SKILL.md resolves to a real file in the deployed bundle, or describe the visualization guidance inline so a broken cross-reference does not block execution.

Add at least one concrete executable snippet or template (e.g. a minimal Streamlit/HTML scaffold) so actionability is not entirely deferred to external specs.

Dimension	Reasoning	Score
Conciseness	The ~35-line body is lean and assumes Claude's competence — short imperative steps and bullet checklists with no padding or explanation of concepts Claude already knows, matching the score-3 'every token earns its place' anchor.	3 / 3
Actionability	Gives concrete checklists ('formula, numerator/denominator, unit, grain, time window, filters...') but no executable code, and the implementation detail is deferred to specification files that are not present in the bundle, so guidance is incomplete and missing key details per the score-2 anchor.	2 / 3
Workflow Clarity	A clearly sequenced 8-step workflow with explicit validation (step 3 validates joins/completeness/duplicates before trust) and a dedicated QA-and-handoff checklist with testing of empty/partial/error states, matching the score-3 anchor of clear sequence plus explicit validation and checklists.	3 / 3
Progressive Disclosure	Sections are well-organized and references are one level deep and clearly signaled ('read specifications/streamlit-dashboard.md'), but those referenced files (and ../visualize-data/SKILL.md) do not exist in the bundle, so navigation is broken rather than easy, which keeps it below the score-3 anchor.	2 / 3
	Total	10 / 12 Passed

Description

60%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific about deliverable components but lacks any explicit 'when to use' trigger clause, capping completeness, and its trigger terms have limited variation. Adding a Use-when clause with natural trigger phrasing would lift the two lowest dimensions.

Suggestions

Add a 'Use when...' clause naming the user situations that should trigger this skill, e.g. when the user asks to build a dashboard, monitoring view, recurring KPI report, or exploration surface rather than a one-time report.

Broaden natural trigger terms with common variations users would say (e.g. 'dashboard', 'monitoring', 'KPI view', 'metrics view', 'reporting surface').

Sharpen distinctiveness by contrasting with one-time reports or ad-hoc charts so it is unlikely to trigger for generic visualization skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete deliverables — 'clear metrics, filters, visual hierarchy, definitions, refresh context, and QA' — which is more comprehensive than the score-2 anchor that names only a domain and a couple actions; not vague like the score-1 anchor.	3 / 3
Completeness	Clearly states what the skill does ('Build a source-backed dashboard...') but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Contains natural terms a user would say ('dashboard', 'monitoring view', 'metrics', 'filters'), but lacks common variations and any explicit trigger phrasing, matching the score-2 anchor of 'some relevant keywords but missing common variations' rather than the broad coverage of score 3.	2 / 3
Distinctiveness Conflict Risk	The dashboard/monitoring niche is somewhat specific but could overlap with general data-visualization or reporting skills (it even points to ../visualize-data/SKILL.md), matching the score-2 'somewhat specific but could still overlap' anchor rather than a clearly distinct niche.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/data-analytics/workflows/build-dashboard/SKILL.md
Commit: ff87d47

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.