CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hig-components-menus

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Quality

47%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/hig-components-menus/SKILL.md

The canonical home for this skill is hig-components-menus in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 content is a competently structured overview-plus-reference-index skill: one-line design principles, a verified 11-file reference layer, concrete clarifying questions, and a defined output shape. Its weaknesses are the absence of any explicit workflow ordering, output templates that stay at the label level, and a few padded sections (duplicated description, filler 'When to Use').

Suggestions

Add a short numbered workflow (check the context file → answer the Questions to Ask → consult the matching reference file(s) → produce the Output Format) so the sequence of steps is explicit rather than implied by section order.

Flesh out the Output Format with a concrete worked example or mini-template of the four-part answer, so 'Component recommendation -- which menu or button type and why' becomes directly usable guidance.

Delete the duplicated first paragraph and the auto-generated 'When to Use' filler section ('This skill is applicable to execute the workflow or actions described in the overview.') to reclaim wasted tokens.

DimensionReasoningScore

Conciseness

The body is mostly lean (one-line Key Principles, a compact reference table), but it re-states the frontmatter description verbatim ("Check for `.claude/apple-design-context.md` before asking questions..."), carries a filler "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview."), and inlines generic cross-links that add tokens without guidance. These are unnecessary sections that could be trimmed, matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the clearly-efficient level 4.

3 / 5

Actionability

Concrete decision rules exist ("Pop-up buttons for mutually exclusive choices", "Pull-down buttons for action lists") and the Questions to Ask are specific ("Which platforms?", "macOS menu bar app?"), but the Output Format entries are one-line labels ("Component recommendation -- which menu or button type and why") with no worked example or template, and there is no guidance on how to apply the 11 reference files to reach an answer. This is concrete-but-incomplete guidance, sitting at anchor 3 rather than the mostly-executable level 4.

3 / 5

Workflow Clarity

The implied process (check context file → consult references → ask clarifying questions → produce the four-part output) is discernible from the sections, but the steps are never sequenced — the body never tells the reader in what order to use the Reference Index, the Questions, or the Output Format. It is not a destructive or batch operation, so no validation cap applies, but checkpoints are only implicit, matching anchor 3 ('steps listed but sequence/checkpoints missing or implicit') rather than anchor 4's explicitly ordered flow.

3 / 5

Progressive Disclosure

The body is a genuine overview with a well-signaled, one-level-deep Reference Index table covering 11 topics with 'Key content' hints, and all 11 referenced files (menus.md, context-menus.md, dock-menus.md, edit-menus.md, the-menu-bar.md, toolbars.md, buttons.md, action-button.md, pop-up-buttons.md, pull-down-buttons.md, disclosure-controls.md) exist in references/. Minor organization gaps — the duplicated description line, the auto-generated 'When to Use' filler below the footer — keep it at anchor 4 rather than the fully-polished anchor 5.

4 / 5

Total

13

/

20

Passed

Description

17%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 fails at its primary job: it describes a housekeeping behavior (check a context file, don't re-ask known information) rather than the skill's actual capability of choosing Apple HIG menus and buttons. It contains no trigger terms, no 'use when' clause, and nothing that would let a user or model select this skill over any other. The description field should be rewritten to state the design capability and its triggers.

Suggestions

Rewrite the description to state the actual capability in third person, e.g. 'Selects and specifies Apple HIG menus and buttons (context menus, toolbars, pop-up and pull-down buttons, action buttons) with platform-specific placement and keyboard shortcuts.'

Add a 'Use when...' clause with natural trigger terms: 'Use when choosing or designing menus, context menus, toolbars, or button styles for iOS, iPadOS, macOS, or visionOS apps, or when the user mentions Apple HIG or menu/button design.'

Move the context-file housekeeping rule ('Check for .claude/apple-design-context.md before asking questions') into the body's workflow instead of spending the description on it, and mention the file by its plain purpose (existing Apple design context) rather than only its path.

DimensionReasoningScore

Specificity

The description names one semi-concrete action ("Check for .claude/apple-design-context.md before asking questions") plus a generic second clause ("only ask for information not already covered"), but it never states the skill's actual capability — menu and button selection per Apple HIG — so no design domain is named at all. This falls below anchor 3 (which requires a named domain plus 1-2 concrete actions) and only marginally clears anchor 2, whose actions are 'minimal or generic'.

2 / 5

Completeness

The description is missing both a real 'what' (what the skill does — it describes a meta-behavior, checking a context file, instead of menu/button guidance) and any 'when' trigger — there is no 'Use when...' clause or equivalent, which caps completeness at 3 by guideline and the vague pseudo-'what' pushes it further down. It best fits anchor 2 ('has a vague what and no when'), not anchor 3, because the stated action is not the skill's capability.

2 / 5

Trigger Term Quality

There are no natural keywords a user would say when needing this skill — 'menu', 'button', 'toolbar', 'context menu', 'Apple', 'HIG', 'design' are all absent. The only content is a technical file path (".claude/apple-design-context.md") and generic phrasing about asking questions, matching anchor 1 ('no natural keywords; only technical jargon or entirely generic language').

1 / 5

Distinctiveness Conflict Risk

Stripped of the path reference, the text ("Use existing context and only ask for information not already covered") is generic advice that would equally match any skill that asks clarifying questions, giving high overlap risk as in anchor 2. It is not entirely content-free like anchor 1's example — the specific .claude path and the implied design context give it one distinguishing detail — so it sits between anchors 1 and 2, closer to 2.

2 / 5

Total

7

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/hig-components-menus/SKILL.md

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.