CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-patterns

Apple Human Interface Guidelines interaction and UX patterns.

52

Quality

59%

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

The canonical home for this skill is hig-patterns 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 body is a well-structured overview that delegates detail to a comprehensive, verified reference index and gives concrete, actionable pattern-selection guidance. Its main weaknesses are a terse/generic description-driven entry and minor boilerplate padding rather than any structural defect.

DimensionReasoningScore

Conciseness

The body is efficiently organized as concise principle bullets, a compact reference index, and a selection table without explaining concepts Claude already knows; only the marketing footer and generic 'When to Use' boilerplate are trimmable padding.

4 / 5

Actionability

Concrete, specific guidance is given — quantified rules ('Three screens max'), a user-goal-to-pattern table mapping goals to recommended patterns and anti-patterns, plus an explicit output format — though it is advisory rather than executable code.

4 / 5

Workflow Clarity

The Output Format gives a clear 4-step sequence (recommend pattern with rationale → step-by-step implementation → platform variations → common pitfalls) supported by a Questions-to-Ask intake step; no validation checkpoints, but none are required for an advisory skill.

4 / 5

Progressive Disclosure

A clear overview with a well-signaled one-level-deep reference index of 25 references (all verified present in references/), each with topic and key-content columns, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

40%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 is a terse topic label rather than a capability statement: it identifies the domain well but specifies no concrete actions and gives no trigger guidance for when to use it. Adding verbs and a 'Use when...' clause would substantially improve it.

Suggestions

Add concrete verbs/actions, e.g. 'Recommends Apple HIG interaction patterns, maps user goals to UX patterns, and flags HIG violations for iOS/macOS/watchOS/visionOS apps.'

Append an explicit trigger clause: 'Use when designing or reviewing Apple-platform interaction flows, modality, feedback, onboarding, or navigation patterns.'

Include natural synonyms users say — 'HIG', 'Apple design guidelines', 'iOS UX patterns' — to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description 'Apple Human Interface Guidelines interaction and UX patterns.' names the domain clearly but lists no concrete actions at all, sitting between the vague anchor (1) and the minimal-actions anchor (2).

2 / 5

Completeness

It offers only a vague noun-phrase 'what' with no verbs, and provides no 'when' / 'Use when...' trigger guidance, matching the 'vague what and no when' anchor.

2 / 5

Trigger Term Quality

It includes relevant keywords ('Apple Human Interface Guidelines', 'interaction', 'UX patterns') a user might say, but lacks common variations/synonyms like 'HIG', 'Apple design', or 'iOS/macOS guidelines'.

3 / 5

Distinctiveness Conflict Risk

'Apple Human Interface Guidelines interaction and UX patterns' targets a clear niche with low conflict risk against generic skills, though it could overlap with sibling hig-* skills.

4 / 5

Total

11

/

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.