build-dashboard

Build the visual layer of a holaOS dashboard app — TanStack Start + @holaboss/ui + workspace tokens. Use when an app has SDK primitives wired (via app-builder-sdk) AND needs a `src/client/` UI surface. NOT for marketing pages, NOT for snapshot HTML reports.

Quality

86%

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

Quality

Content

85%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced skill body with copy-paste code and strong validation checkpoints; its main weakness is progressive disclosure, because the prominently referenced bundled reference directory does not exist alongside SKILL.md, breaking the intended offloading of the two varying files.

Suggestions

Ship the referenced bundle: create reference/messaging-dashboard/src/client/ with routes/index.tsx, components/messages-table.tsx, and lib/sample-data.ts so the deferred one-level-deep references actually resolve.

Tighten conciseness by collapsing the per-shape swap tables and the inline snippets into a single representation per shape, removing the duplicated keep/change guidance.

If the bundle cannot be shipped, inline the two varying files directly in SKILL.md rather than pointing at an absent reference path.

Dimension	Reasoning	Score
Conciseness	Dense and assumes Claude's competence (no primers on React/Tailwind), but at ~520 lines it repeats copy-paste blocks and restates swap guidance in both tables and prose, leaving a few sections that could be tightened; not a full 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready code for all five shapes plus verbatim foundation files, exact pinned deps with rationale for using 'latest', and exact lint codes — covering the common cases completely.	5 / 5
Workflow Clarity	Clear sequence (pick shape → copy verbatim foundation → swap varying files → wire rest → checklist) with explicit validation checkpoints: register-time lint codes and a numbered 'When you're done' list including a curl check and dark-mode test.	5 / 5
Progressive Disclosure	Well-sectioned body that defers the two per-app-varying files to a bundled 'reference/messaging-dashboard/src/client/' directory, but that referenced bundle is not present in the workspace (no references/ or reference/ dir), so the signaled one-level-deep navigation points at a missing resource.	3 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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

A strong, specific description that clearly states what the skill builds and when to invoke it, with good distinctiveness via explicit negative triggers. Trigger-term coverage is good but skews toward stack jargon and misses some plain-language dashboard terms a user might say.

Dimension	Reasoning	Score
Specificity	Names the domain ('Build the visual layer of a holaOS dashboard app') and several concrete stack-level actions ('TanStack Start + @holaboss/ui + workspace tokens', 'needs a src/client/ UI surface'), with only minor coverage gaps versus the comprehensive 5 anchor.	4 / 5
Completeness	Explicitly answers both what ('Build the visual layer... TanStack Start + @holaboss/ui + workspace tokens') and when ('Use when an app has SDK primitives wired AND needs a src/client/ UI surface'), with concrete trigger phrases and explicit NOT-for exclusions.	5 / 5
Trigger Term Quality	Includes natural terms ('dashboard app', 'UI surface', 'marketing pages', 'snapshot HTML reports') but leans on stack jargon ('SDK primitives wired', 'src/client/ UI surface') and omits common lay variations like 'kanban', 'calendar', or 'let me see my X' that appear in the body.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (dashboard visual layer post-SDK wiring) and adds explicit NOT-for clauses separating it from frontend-design and snapshot reports, minimizing conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (526 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: holaboss-ai/holaOS
Path: runtime/harnesses/src/embedded-skills/build-dashboard/SKILL.md
Commit: 4684714

Reviewed: 12 days 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.