CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-layout

Apple Human Interface Guidelines for layout and navigation components.

54

Quality

61%

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-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 well-structured and token-efficient, with a strong reference index pointing to real one-level-deep files and concrete, actionable guidance grounded in named APIs and a decision table. Main gaps are a filler 'When to Use' line and the absence of explicit validation checkpoints.

Suggestions

Remove the generic '## When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.') and replace it with a concrete trigger clause.

Add a short validation/review checkpoint to the Output Format (e.g. 'Verify the chosen pattern satisfies every item in the Layout Adaptation Checklist before finalizing').

Consider trimming or relocating the built-by footer to keep the skill body focused.

DimensionReasoningScore

Conciseness

The body is largely lean — tables and short bullets with no padding about what a sidebar is — but the generic '## When to Use' filler line and the built-by footer are trimmable, matching the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

As an instruction skill it gives concrete, specific guidance — named APIs (NavigationSplitView, UISplitViewController, TabView, .sidebarAdaptable) and a structure-to-pattern decision table — with only minor gaps versus fully copy-paste-ready recipes, matching the 'mostly executable guidance' anchor.

4 / 5

Workflow Clarity

The 'Output Format' section sequences the deliverable (pattern → hierarchy → platform adaptation → size-class behavior) and a checklist/Questions section provide a clear sequence, but explicit validation checkpoints are absent, matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

A concise overview body links one-level-deep to 12 real references/*.md files via a well-signaled index table giving topic and key content for each, matching the 'clear overview with well-signaled one-level-deep references; easy navigation' anchor.

5 / 5

Total

17

/

20

Passed

Description

45%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 identifies a clear domain but states no concrete actions and omits any 'Use when' trigger guidance, capping completeness and distinctiveness. It reads as a topic label rather than an action-oriented, trigger-rich description.

Suggestions

Add concrete actions, e.g. 'Recommends navigation patterns, sizes layouts across platforms, and selects system components for iOS/iPadOS/Mac/visionOS apps.'

Append a 'Use when...' clause with natural triggers: 'Use when designing or reviewing app navigation, choosing tab bars vs. sidebars, or adapting layouts across iPhone/iPad/Mac/visionOS.'

Narrow the scope relative to sibling HIG skills (e.g. 'layout and navigation component selection') to reduce overlap and conflict risk.

DimensionReasoningScore

Specificity

The description names a concrete domain ('layout and navigation components') but lists no concrete actions, matching the 'Names the domain but actions are minimal or generic' anchor; it is above a 1 because it is not purely abstract.

2 / 5

Completeness

It gives a clear 'what' (Apple HIG for layout/navigation components) but no 'when'/Use-when clause; per guidelines a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'layout', 'navigation', and 'components' are relevant keywords users might say, but it lacks natural variations, synonyms, and explicit trigger phrasing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Apple-HIG layout/navigation niche is somewhat specific but the broad 'Human Interface Guidelines' scope overlaps with sibling skills (hig-foundations, hig-platforms, hig-patterns, hig-components-content), matching the 'somewhat specific but could still overlap' anchor.

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