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.

60

Quality

70%

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

78%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 well-organized, concise overview that delegates detail to real one-level-deep reference files, with concrete actionable HIG guidance and a clear question-then-output workflow.

DimensionReasoningScore

Conciseness

The body is lean: ten one-sentence principles, a reference table, and brief output/question lists with no padding of concepts Claude already knows, though the footer credit and the generic 'When to Use' line are minor trimmable fluff.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete and specific (e.g. 'destructive button style (red text)', 'cancel appears at the bottom, separated', 'Button labels should be specific verbs'), with only minor gaps in coverage of edge cases.

4 / 5

Workflow Clarity

A clear sequence exists (clarifying Questions to Ask, then a four-part Output Format), but it is an advisory skill without validation checkpoints, so it stops short of the explicit feedback-loop structure of a 5.

4 / 5

Progressive Disclosure

The body is a concise overview with a well-signaled Reference Index table linking one level deep to five real reference files, each annotated with topic and key content, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

61%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 clearly scopes a specific domain and lists concrete component types with good natural keywords, but it lacks an explicit "Use when..." trigger clause and uses only a generic action verb.

Suggestions

Add an explicit 'Use when...' clause naming trigger situations, e.g. 'Use when designing or choosing iOS/iPadOS/macOS presentation UI such as alerts, sheets, or popovers.'

Replace the generic verb 'guidance for' with concrete actions like 'Guides selection and design of...'.

Include platform synonyms (iOS, iPadOS, macOS, dialog, modal) to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Apple HIG guidance for presentation components") and enumerates five concrete component types (alerts, action sheets, popovers, sheets, digit entry views), but the only action verb is the generic "guidance for" rather than concrete actions like 'design' or 'choose'.

3 / 5

Completeness

The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural UI terms a developer would say ("alerts", "action sheets", "popovers", "sheets") are present, but common synonyms like "dialog", "modal", and platform names (iOS/iPad/Mac) are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and specific (Apple HIG presentation components), but closely related HIG skills exist (menus, controls, patterns) creating minor overlap risk rather than minimal conflict.

4 / 5

Total

14

/

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.

Validation15 / 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
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.