CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-layout

Apple Human Interface Guidelines for layout and navigation components.

56

Quality

63%

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/skills/hig-components-layout/SKILL.md

The canonical home for this skill is hig-components-layout 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 reference skill: lean, actionable, and excellently organized via a one-level-deep reference index and a pattern-selection table. Its only real weakness is the vague, filler "When to Use" section and the absence of an explicit recovery/feedback step in the workflow.

DimensionReasoningScore

Conciseness

The body is mostly efficient—key principles, tables, and checklists carry their weight without re-explaining concepts Claude knows—though the trailing "When to Use" line ("applicable to execute the workflow or actions described in the overview") and the promotional footer are minor padding that keeps it just below a 5.

4 / 5

Actionability

Concrete, executable design guidance is provided throughout—specific APIs (NavigationSplitView, UISplitViewController, TabView), a pattern-selection table mapping app structure to a recommended pattern, and a defined output format—minor gaps (no worked example of a full layout hierarchy) keep it at 4 rather than 5.

4 / 5

Workflow Clarity

A clear sequence is present (check the context file, ask the listed questions, select a pattern, emit the specified output format) with the questions-to-ask and output-format sections acting as checkpoints; it is not a 5 because validation/recovery steps are implicit rather than explicit, and not a 3 because the sequence is unambiguous and not destructive.

4 / 5

Progressive Disclosure

The SKILL.md is a clean overview with a well-signaled reference-index table pointing one level deep to 12 real reference files (all confirmed present in references/), each labeled with topic and key content, matching the score-5 anchor for clear overview with one-level-deep references.

5 / 5

Total

17

/

20

Passed

Description

48%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 identifies its domain but is a topic statement rather than an action + trigger statement: it names no concrete actions and omits any "Use when..." guidance, which caps completeness. Adding explicit triggers and one or two concrete actions would lift specificity and completeness.

Suggestions

Append a "Use when..." trigger clause, e.g. "Use when designing or reviewing iOS/iPadOS/macOS/visionOS layout, navigation, or screen structure."

Add 1-2 concrete actions to the description, e.g. "Selects navigation patterns (tab bars, sidebars, split views) and maps them to platform size classes."

Include natural synonyms users say, such as "HIG", "tab bar", "sidebar", and "NavigationSplitView", to improve trigger coverage.

DimensionReasoningScore

Specificity

The description "Apple Human Interface Guidelines for layout and navigation components" names the domain clearly but states no concrete actions, matching the score-2 anchor ("Names the domain but actions are minimal or generic"); it does not reach 3 because no 1-2 concrete actions are listed.

2 / 5

Completeness

There is a clear "what" (Apple HIG for layout and navigation components) but no "Use when..." trigger clause, so per the judging guideline completeness is capped at 3 and the when is only weakly implied.

3 / 5

Trigger Term Quality

Terms "layout", "navigation", "components", and "Apple Human Interface Guidelines" are relevant but missing common natural variations users might say (e.g. "HIG", "tab bar", "sidebar"); fits the score-3 anchor of some relevant keywords missing synonyms.

3 / 5

Distinctiveness Conflict Risk

The layout/navigation-components niche is mostly distinct and would rarely misfire, though it has minor overlap risk with sibling HIG skills (hig-foundations, hig-components-content), matching the score-4 anchor.

4 / 5

Total

12

/

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.