CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./runtime/harnesses/src/embedded-skills/build-dashboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 with strong validation feedback loops. Its weaknesses are length from inlining material that should live in the (currently missing) reference bundle, which also undermines progressive disclosure.

Suggestions

Ship the referenced `reference/messaging-dashboard/src/client/` bundle so the cited paths resolve; the body repeatedly depends on files that are not present.

Move the five verbatim foundation components out of the body and into the bundle (or a single FOUNDATION.md), keeping only the shape-selection guidance and diffs inline to cut length.

Soften the trigger phrasing in the description with natural user terms (e.g. "build me a dashboard", "let me see my X") alongside the technical conditions to improve trigger-term quality.

DimensionReasoningScore

Conciseness

The body is mostly efficient and concrete, but at ~520 lines it inlines five full verbatim foundation components while also pointing to a bundled reference, which is redundant and could be tightened — matching the score-2 anchor.

2 / 3

Actionability

It provides fully executable, copy-paste-ready code for all five shapes plus package.json, vite.config.ts, server.ts, and concrete lint codes, hitting the score-3 anchor.

3 / 3

Workflow Clarity

The process is clearly sequenced (pick shape → copy foundation → customize → wire deps → server.ts) with explicit validation checkpoints: the lint-enforced setup table and the five-item done-list including light/dark verification and a curl HTML-response check.

3 / 3

Progressive Disclosure

Sections are well-organized and references are signaled, but the cited `reference/messaging-dashboard/` bundle does not exist and content that belongs in separate files (verbatim components, shape implementations) is inlined, matching the score-2 anchor.

2 / 3

Total

10

/

12

Passed

Description

75%

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, third-person description that clearly bounds the skill with explicit use-conditions and exclusions. Its only weakness is trigger phrasing that leans on internal terminology rather than natural user language.

DimensionReasoningScore

Specificity

The description names a concrete domain and stack ("Build the visual layer of a holaOS dashboard app — TanStack Start + @holaboss/ui + workspace tokens") but offers a single primary action rather than multiple listed actions, matching the score-2 anchor.

2 / 3

Completeness

It explicitly answers what ("Build the visual layer of a holaOS dashboard app") and when ("Use when an app has SDK primitives wired... AND needs a `src/client/` UI surface"), with explicit negative boundaries, hitting the score-3 anchor.

3 / 3

Trigger Term Quality

"dashboard" is a natural user term, but the trigger conditions ("SDK primitives wired", "src/client/ UI surface") are internal/technical phrasings rather than language a user would say, so common variations are missing.

2 / 3

Distinctiveness Conflict Risk

The niche is specific (dashboard UI surface for SDK-wired holaOS apps) and the explicit exclusions ("NOT for marketing pages, NOT for snapshot HTML reports") make conflicts with adjacent skills unlikely.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.