Name: scene-menu-bar
Rating: 72 (1 reviews)
Author: PostHog

scene-menu-bar

Conventions for adding or editing the SceneMenuBar above a scene's <SceneTitleSection>. Use when adding new menu items, moving items between menus, gating behind feature flags, building a new scene's menubar, or wiring rich inputs (tags, combobox) into the bar.

Quality

87%

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

82%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 well-structured, highly actionable conventions reference with concrete props, file paths, and code examples. The main weaknesses are a slightly long prose section on empty menus and a broken absolute-path reference to a Desktop file.

Suggestions

Tighten the 'Empty menus' and 'Layout-aware bleed' prose to bullet rules; the rationale is specialized but currently runs long.

Replace the '/Users/adamlethp/Desktop/scene-menu-bar-grouping.md' pointer with a relative path inside the skill bundle or move that inventory into a bundled reference file so it resolves for other users.

Add an explicit confirmation/verification step to the destructive-actions rule (e.g. confirm before delete/archive) so the destructive workflow has a validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly tables/rules with no padding about basic concepts, assuming React/kea/PostHog competence; a few prose sections (e.g. empty menus, layout-aware bleed) run slightly long and could be trimmed.	4 / 5
Actionability	It provides concrete component names, specific props (variant="destructive", opensFloatingUi, withIconBlank={false}), real file paths, and two copy-paste-ready tsx code blocks covering the common cases.	5 / 5
Workflow Clarity	The optimistic-saves section is a clear numbered sequence with feedback checkpoints (breakpoint bail, set-equality check) and the auditing section is a numbered checklist, but the destructive-actions guidance lacks an explicit verification/confirmation checkpoint.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections and tables with no nested references; however everything is inlined in one ~170-line file and the one external pointer is a non-portable absolute Desktop path that won't resolve for other users.	4 / 5
	Total	17 / 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.

A strong, specific description that clearly names its niche (PostHog SceneMenuBar conventions) and provides an explicit 'Use when' trigger list covering the main scenarios. Trigger term coverage is good though a few natural synonyms could be added.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions ('adding new menu items, moving items between menus, gating behind feature flags, building a new scene's menubar, or wiring rich inputs (tags, combobox)'), giving comprehensive coverage of what the skill addresses.	5 / 5
Completeness	It explicitly states both the 'what' ('Conventions for adding or editing the SceneMenuBar above a scene's <SceneTitleSection>') and the 'when' via a concrete 'Use when...' clause listing specific triggers, satisfying both halves explicitly.	5 / 5
Trigger Term Quality	It includes natural trigger phrases a developer would say ('adding new menu items', 'moving items between menus', 'feature flags', 'rich inputs (tags, combobox)'), with good coverage but a few common synonyms/variations absent.	4 / 5
Distinctiveness Conflict Risk	The references to 'SceneMenuBar', '<SceneTitleSection>', and scene menubar conventions carve out a narrow niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 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: PostHog/posthog
Path: .agents/skills/scene-menu-bar/SKILL.md
Commit: 06292db

Reviewed: 19 minutes 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.