use-topbar
Wires the Aura Topbar (@aura/topbar) into Flows/Fusion apps as the single top navigation bar — breadcrumbs, optional center Tabs or Segmented control, right utility strip (Share, notifications, theme menu, Atlas, user Avatar), and light/dark theme switching. Use when adding a topbar, app header, navigation bar, breadcrumbs, or theme switcher to a Flows or Fusion app, or when scaffolding a new Flows/Fusion application.
74
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly communicates specific capabilities (breadcrumbs, tabs, utility strip, theme switching), uses natural trigger terms users would say, and includes an explicit 'Use when...' clause with multiple trigger scenarios. The description is well-scoped to a distinct niche (Aura Topbar in Flows/Fusion apps) making it easy to distinguish from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and components: breadcrumbs, center Tabs or Segmented control, right utility strip with Share/notifications/theme menu/Atlas/user Avatar, and light/dark theme switching. Very detailed about what the skill does. | 3 / 3 |
Completeness | Clearly answers both 'what' (wires Aura Topbar with breadcrumbs, tabs, utility strip, theme switching) and 'when' (explicit 'Use when...' clause listing trigger scenarios including adding a topbar, scaffolding new apps, etc.). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'topbar', 'app header', 'navigation bar', 'breadcrumbs', 'theme switcher', 'Flows', 'Fusion', plus specific component names like '@aura/topbar'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically targets the Aura Topbar component in Flows/Fusion apps. The combination of specific framework names (@aura/topbar, Flows, Fusion) and specific UI components makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that serves as an effective orchestration document for a complex multi-step process. Its strengths are excellent progressive disclosure, a clear sequential workflow with validation, and concise writing that respects Claude's intelligence. The main weakness is that actionable implementation code lives entirely in referenced files, so the skill body itself is more of a coordinator than a self-contained guide — though this is a reasonable design choice given the complexity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what a topbar is conceptually, assumes Claude understands component composition, and every section serves a clear purpose. The checklist items are dense but necessary for compliance verification. | 3 / 3 |
Actionability | The skill provides a clear step-by-step workflow and a concrete JSON snippet for hooks setup, but defers most executable code (install commands, component composition, hook wiring) to IMPLEMENTATION.md. The checklist is specific but the skill itself lacks copy-paste-ready implementation code. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Steps 0–6) with explicit pre-flight inference, a mandatory interview gate before implementation, and a detailed compliance checklist as a final validation step. The 'never build a custom header fallback' constraint and 'surface the blocker' instruction provide clear error-handling guidance. | 3 / 3 |
Progressive Disclosure | The skill is an excellent overview that delegates detailed content to clearly signaled, one-level-deep references: RULES.md for constraints, INTERVIEW.md for the configuration questionnaire, and IMPLEMENTATION.md for install/code details. Navigation is well-organized with section-specific cross-references (e.g., 'RULES.md §1, §11, §12'). | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- cognitedata/builder-skills
- Commit
d6af887
- 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.