use-topbar

Wires the Aura Topbar (@aura/topbar) into Flows/Fusion apps: breadcrumbs, optional Tabs/Segmented, right strip (Share, notifications, theme, Atlas, user Avatar), light/dark. Atlas opens the EOS sidebar — wire context with integrate-fusion-agent; do not embed a chat UI. Use when adding a topbar, header, breadcrumbs, theme switcher, or Atlas launcher.

Quality

83%

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

75%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.

The body is a well-organized, mostly executable workflow with a clear step sequence and a terminal compliance checklist. Its main weakness is progressive disclosure: it relies on RULES.md, INTERVIEW.md, and IMPLEMENTATION.md, none of which ship in the bundle, and it lacks an explicit error-recovery feedback loop.

Suggestions

Ship the referenced bundle files (RULES.md, INTERVIEW.md, IMPLEMENTATION.md) inside the skill so the one-level-deep references actually resolve; currently the references/, scripts/, and assets/ directories are absent.

Add an explicit validate→fix→retry feedback loop, e.g. define what to do when the shadcn CLI install or useThemeMode wiring fails beyond 'surface the blocker', and re-verify the compliance checklist after fixes.

Tighten the introductory prose (e.g., the Step 0 lead sentence) to remove restating-of-purpose language and push conciseness toward anchor 5.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — exact install command, copy-ready hook JSON, a dense compliance checklist — but introductory prose like "Ensure the topbar interview is triggered at the start of every future Cursor session in this project" could be trimmed, keeping it just below anchor 5.	4 / 5
Actionability	Concrete, executable guidance is present (pnpm dlx shadcn command, files to read, full .cursor/hooks.json block, specific checklist rules), but the core install/theme-wiring code and the Q1–Q9 interview live in referenced files rather than inline, leaving minor gaps.	4 / 5
Workflow Clarity	A clear Step 0 → Step 6 sequence with a final compliance checklist ("Verify before finishing") as a validation checkpoint; falls short of anchor 5 because there is no explicit error-recovery/feedback loop (e.g., what to do when the shadcn install fails beyond "surface the blocker").	4 / 5
Progressive Disclosure	Well-signaled one-level-deep references with descriptive labels ("Full rules: RULES.md · Interview: INTERVIEW.md · Install + code: IMPLEMENTATION.md") and an appropriately split overview; held at 4 rather than 5 because none of the three referenced files are present in the skill bundle (no references/, scripts/, or assets/ exist), so the paths do not resolve.	4 / 5
	Total	16 / 20 Passed

Description

92%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.

The description is strong: it states concrete capabilities using named components and an explicit, multi-trigger "Use when" clause that clearly distinguishes the skill. Trigger-term coverage is the only minor weakness, lacking a wider synonym set.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and named components — "Wires the Aura Topbar (@aura/topbar) into Flows/Fusion apps: breadcrumbs, optional Tabs/Segmented, right strip (Share, notifications, theme, Atlas, user Avatar), light/dark" — giving comprehensive, specific coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both halves: the "what" (wires the Topbar with the listed components and light/dark) and a concrete "when" clause ("Use when adding a topbar, header, breadcrumbs, theme switcher, or Atlas launcher").	5 / 5
Trigger Term Quality	"Use when adding a topbar, header, breadcrumbs, theme switcher, or Atlas launcher" supplies five natural trigger phrases a user would say, with topbar/header acting as near-synonyms; falls just short of anchor 5 because it lacks broader synonym/file-extension breadth.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific component (@aura/topbar) and platform (Flows/Fusion) with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
relative_links	Relative link issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: cognitedata/builder-skills
Path: skills/use-topbar/SKILL.md
Commit: c87160a

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