CtrlK
BlogDocsLog inGet started
Tessl Logo

hide-show-shell

MUST be used when a Flows/Fusion app needs full-screen "app-only" mode — hiding the Fusion sidebar and topbar so the app gets the whole viewport, and giving users a clear way to bring the shell back. Triggers: hideShell, full screen app, fullscreen mode, hide sidebar, hide topbar, hide shell, hide menu, setHideShell, app-only mode, kiosk mode, custom side nav, full viewport.

74

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 high-quality, actionable skill body with complete executable code, clear sequencing, and well-placed validation and testing checkpoints. It stays focused on non-obvious platform-specific gotchas rather than padding concepts Claude already knows.

Suggestions

Trim the 'Matching the Fusion sidebar's width' table or move it to a reference file; it is peripheral detail that adds length without aiding the core toggle workflow.

The safety-net warning appears in both 'What it does' and a dedicated 'Non-negotiable' section; consolidate to reduce repetition.

Consider moving the full vitest test block (Step 3) into a bundled reference file to keep the main flow lean while keeping tests discoverable.

DimensionReasoningScore

Conciseness

Information-dense and focused on non-obvious gotchas (safety net, flag conditions, import-path quirk, width constants) without padding basic concepts, though the ~275-line body has minor trim opportunities in the width-matching section and repeated safety-net emphasis.

4 / 5

Actionability

Fully executable, copy-paste-ready code throughout: a complete useHideShell hook, a FullScreenToggle TSX component, and a full vitest test file, plus concrete commands like 'npm ls @cognite/app-sdk'.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit validation checkpoints (Step 3 adds tests; Step 5 verifies both directions and reload/navigation behavior) and a gating prerequisite check up front.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is a single cohesive file with clear, navigable section headers and only one-level-deep external pointers to related skills, so the well-organized structure satisfies the no-external-reference case.

5 / 5

Total

19

/

20

Passed

Description

95%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, well-targeted description with explicit what/when guidance and a rich, natural trigger-term list. It uses third-person voice and avoids vague fluff, with only minor room for more complete action enumeration.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('hiding the Fusion sidebar and topbar so the app gets the whole viewport, and giving users a clear way to bring the shell back'), with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (hide/reveal the shell for full viewport) and when ('MUST be used when a Flows/Fusion app needs full-screen app-only mode') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term list including synonyms ('full screen app', 'fullscreen mode'), API identifiers ('hideShell', 'setHideShell'), and user phrasings ('hide sidebar', 'hide topbar', 'kiosk mode').

5 / 5

Distinctiveness Conflict Risk

Clear niche (Fusion shell visibility toggling) anchored by distinctive API terms like 'setHideShell' and 'hideShell' that minimize overlap with related skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 3 suspicious

Warning

Total

14

/

16

Passed

Repository
cognitedata/builder-skills
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.