CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-dialogs

Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views.

53

Quality

60%

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-dialogs/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 that efficiently communicates when and how to use Apple HIG presentation components. Its strengths are concise principles, clear progressive disclosure via reference files, and a well-defined output format. Its main weakness is the lack of concrete code examples (SwiftUI/UIKit snippets) that would make the guidance more immediately actionable for implementation tasks.

Suggestions

Add concrete SwiftUI/UIKit code snippets for at least the most common presentation types (e.g., alert and sheet) to improve actionability.

Make the workflow sequence more explicit by numbering the steps: 1) check context file, 2) ask clarifying questions, 3) consult relevant reference file, 4) produce output in specified format.

DimensionReasoningScore

Conciseness

The content is efficient and avoids explaining basic concepts Claude would know. The 10 key principles are concise and informative. Minor verbosity in the 'When to Use' section and the marketing footer, but overall well-trimmed.

4 / 5

Actionability

The skill provides clear design guidance and decision criteria (e.g., when to use alerts vs sheets vs popovers), but lacks concrete code examples or copy-paste ready SwiftUI/UIKit snippets. The output format section gives structure but remains at the instructional level without executable examples.

3 / 5

Workflow Clarity

The workflow is implicit but clear for a design guidance skill: check context file, ask clarifying questions, then produce output in the specified format. The output format section provides a clear 4-step structure. No destructive/batch operations are involved, so validation checkpoints aren't critical. Minor gap: the relationship between 'Questions to Ask' and the output steps could be more explicitly sequenced.

4 / 5

Progressive Disclosure

Good structure with a clear reference index table pointing to 5 separate reference files, plus related skills section. The main content serves as an effective overview. However, since no bundle files were provided, we cannot verify the referenced files exist. The references appear to be one level deep and well-signaled, which is good practice.

4 / 5

Total

15

/

20

Passed

Description

52%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 identifies a clear domain (Apple HIG) and enumerates specific presentation components, which aids distinctiveness and trigger matching. However, it lacks concrete actions beyond 'guidance' and entirely omits a 'Use when...' clause, significantly weakening completeness. Adding explicit trigger phrases and describing what the skill actually does (e.g., provides design rules, generates compliant layouts) would substantially improve it.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about Apple HIG presentation patterns, modal dialogs, alerts, action sheets, or popovers on iOS/macOS.'

Replace the vague word 'guidance' with concrete actions such as 'Provides design rules, layout specifications, and best practices for...'

Include synonyms and related terms like 'modal', 'dialog', 'popup', 'Human Interface Guidelines', 'iOS', 'macOS' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Apple HIG guidance) and lists specific component types (alerts, action sheets, popovers, sheets, digit entry views), but the action is vague — 'guidance' doesn't describe concrete actions like 'provides layout rules' or 'generates compliant code'.

3 / 5

Completeness

Provides a partial 'what' (HIG guidance for presentation components) but has no explicit 'when' clause. The absence of a 'Use when...' clause caps this at 3 per the rubric, and the 'what' itself is vague enough to warrant a 2.

2 / 5

Trigger Term Quality

Includes several natural keywords users might use: 'Apple HIG', 'alerts', 'action sheets', 'popovers', 'sheets', 'digit entry views'. Missing some synonyms like 'modal', 'dialog', 'popup', 'Human Interface Guidelines', or platform terms like 'iOS', 'macOS'.

4 / 5

Distinctiveness Conflict Risk

Fairly distinct by specifying Apple HIG and listing specific presentation component types, which narrows the niche. Minor overlap risk with other Apple HIG skills covering different component categories or general UI design skills.

4 / 5

Total

13

/

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.