interface-design

This skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns).

Quality

78%

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 ./runtime/harnesses/src/embedded-skills/interface-design/SKILL.md

Quality

Content

85%

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

The body is a well-structured, actionable design-principles skill with a clear workflow, explicit validation checkpoints, and properly signaled one-level-deep references. Its main weakness is verbosity: several sections restate the same intent-vs-defaults argument and could be consolidated to respect the token budget.

Suggestions

Consolidate the overlapping motivational sections ("The Problem", "Where Defaults Hide", "Sameness Is Failure", "Intent Must Be Systemic", "Every Choice Must Be A Choice") into one tighter intent section to reduce redundancy.

Consider moving the extended "Spatial Composition" Q&A into a reference file, keeping only the decision prompts inline, to shorten SKILL.md.

Either reference references/example.md from the body or note it as supplementary, since it currently exists as an unreferenced bundle file.

Dimension	Reasoning	Score
Conciseness	The body delivers genuine craft guidance Claude would not inherently know, but ~430 lines with overlapping motivational sections ("The Problem", "Where Defaults Hide", "Sameness Is Failure", "Intent Must Be Systemic", "Every Choice Must Be A Choice") restate the same intent-vs-defaults theme and could be tightened; not score 1 because it does not explain basic concepts Claude already knows.	2 / 3
Actionability	For an instruction-only skill it gives concrete, specific guidance: a fill-in "Before Writing Each Component" template, specific values ("1280x800 viewport", "240-320px" sidebar, "grid-cols-3 / grid-cols-4 / grid-cols-6"), numbered required outputs with minimums, and named checks (swap, squint, signature, token).	3 / 3
Workflow Clarity	The "If No system.md" workflow is a clear 6-step sequence (Explore, Propose, Confirm, Build, Evaluate, Offer to save) with an explicit validation checkpoint ("Evaluate -- Run the mandate checks before showing") and a feedback loop ("If any check fails, iterate before showing").	3 / 3
Progressive Disclosure	The "Deep Dives" section signals one-level-deep references (references/principles.md, references/validation.md, references/critique.md) with a description of each; all referenced paths are real files, and the body keeps core principles inline while delegating deeper material to the references.	3 / 3
	Total	11 / 12 Passed

Description

72%

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 distinctive and uses natural trigger terms, with strong negative-scope guidance that prevents conflicts. Its main weakness is the missing explicit "Use when..." clause and the absence of concrete action verbs, which cap both completeness and specificity.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when building or redesigning dashboards, admin panels, SaaS tools, or data interfaces."

Lead with concrete action verbs ("Design and build", "Lay out", "Style") rather than the passive "This skill is for" framing.

Keep the marketing-design exclusion — it is the strongest part of the description for reducing conflict risk.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists specific product types ("dashboards, admin panels, apps, tools, and interactive products") but uses no concrete action verbs, so it stops short of the score-3 anchor that lists multiple specific actions.	2 / 3
Completeness	It states what the skill is for, but provides no explicit "Use when..." trigger clause; the when-to-use is only implied via the product-type list, and the guidelines cap completeness at 2 without explicit trigger guidance.	2 / 3
Trigger Term Quality	Terms like "dashboards", "admin panels", "apps", "landing pages", "marketing sites", and "interface design" are natural phrases a user would say when requesting this skill, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The explicit negative scope ("NOT for marketing design (landing pages, marketing sites, campaigns)") plus the redirect to /frontend-design carves a clear niche and makes wrong-skill triggering unlikely.	3 / 3
	Total	10 / 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: holaboss-ai/holaOS
Path: runtime/harnesses/src/embedded-skills/interface-design/SKILL.md
Commit: 74c7b6f

Reviewed: 6 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.