CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-menus

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

41

Quality

41%

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 ./skills/hig-components-menus/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Scale 1-5

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 design guidance skill with strong progressive disclosure and good conciseness. Its main weakness is actionability — it provides principles and references but lacks concrete examples of recommended outputs or specific implementation patterns (e.g., showing what a good component recommendation looks like). The reference index is a standout feature that makes navigation easy.

Suggestions

Add a concrete example in the Output Format section showing what a complete response looks like (e.g., a sample recommendation for a macOS menu bar app with component choice, hierarchy, and platform notes).

Include at least one specific SwiftUI or UIKit code snippet illustrating a recommended button or menu pattern to improve actionability.

DimensionReasoningScore

Conciseness

The content is mostly efficient and well-structured. The key principles are concise and informative without over-explaining. Minor verbosity in the 'When to Use' section and the promotional footer, but overall respects Claude's intelligence. The 'Questions to Ask' section is lean and useful.

4 / 5

Actionability

The skill provides design guidance principles and a clear reference index, but lacks concrete, executable examples. There are no code snippets, SwiftUI/UIKit examples, or specific implementation patterns. The output format section describes what to produce but doesn't show an example of a good response. For a design guidance skill (instruction-only), the principles are reasonably specific but could benefit from concrete examples of correct vs incorrect menu/button usage.

3 / 5

Workflow Clarity

The skill has a clear implicit workflow: check context file → consult principles → reference detailed docs → produce output in specified format → ask clarifying questions if needed. The output format section provides a clear 4-point structure. However, there's no explicit sequencing of steps or validation checkpoints. As a non-destructive, advisory skill, this is acceptable but could be slightly more explicit about the decision process.

4 / 5

Progressive Disclosure

Excellent progressive disclosure structure. The SKILL.md provides a concise overview of 10 key principles, then a well-organized reference table pointing to 11 specific reference files with clear topic descriptions. References are one level deep, clearly signaled with a table format, and the content is appropriately split between overview and detailed reference material. However, no bundle files were provided to verify the references actually exist.

5 / 5

Total

16

/

20

Passed

Description

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

This description fails as a skill description because it reads as an internal procedural instruction rather than describing what the skill does or when it should be selected. It provides no information about the skill's capabilities, domain, or trigger conditions, making it nearly impossible for Claude to correctly select this skill from a pool of available options.

Suggestions

Add a clear 'what' clause describing the skill's actual purpose, e.g., 'Guides Apple platform UI/UX design following Apple Human Interface Guidelines' or whatever the skill actually does.

Add a 'Use when...' clause with natural trigger terms users would say, such as 'Use when designing iOS apps, macOS interfaces, Apple design patterns, or HIG compliance.'

Move the procedural instruction about checking .claude/apple-design-context.md into the skill body rather than the description, as it is an implementation detail, not a selection criterion.

DimensionReasoningScore

Specificity

The description contains no concrete actions or capabilities. It only describes a procedural instruction about checking a file and avoiding redundant questions, with no indication of what the skill actually does.

1 / 5

Completeness

Neither 'what does this do' nor 'when should Claude use it' is answered. The description only provides an internal procedural instruction without explaining the skill's purpose or trigger conditions.

1 / 5

Trigger Term Quality

The only potentially useful trigger terms are 'apple-design-context' and the file path, but these are internal references rather than natural user language. A user would never say 'check for .claude/apple-design-context.md'.

2 / 5

Distinctiveness Conflict Risk

While the specific file path '.claude/apple-design-context.md' is unique, the description is so vague about what the skill does that it could overlap with any Apple-related or design-related skill. The lack of defined purpose creates ambiguity.

2 / 5

Total

6

/

20

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.