CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-content

Apple Human Interface Guidelines for content display components.

45

Quality

47%

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 ./skills/hig-components-content/SKILL.md
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-organized reference/advisory skill with strong progressive disclosure through its reference index and component selection tables. Its main weakness is the lack of any concrete code examples — no Swift/SwiftUI snippets for component setup, which limits actionability for a development-focused skill. The content is mostly concise but has some unnecessary trailing sections.

Suggestions

Add at least 2-3 brief, executable Swift/SwiftUI code snippets for the most common components (e.g., a basic Swift Charts setup, a UICollectionView compositional layout, a WKWebView configuration) to improve actionability.

Remove the trailing 'When to Use' boilerplate and the Raintree branding line, as they add no instructional value and consume tokens.

DimensionReasoningScore

Conciseness

Generally efficient with well-structured tables and concise principles. Minor verbosity in some principle explanations (e.g., principle 5 could be tighter), and the trailing 'When to Use' section and Raintree branding are unnecessary filler. But overall it respects Claude's intelligence and avoids over-explaining concepts.

4 / 5

Actionability

Provides useful component selection tables and a clear output format, but lacks any concrete code examples, specific API calls, or executable snippets. The guidance is structured and specific enough to be directional but not copy-paste actionable — it tells Claude what to recommend but not how to implement it with code.

3 / 5

Workflow Clarity

The output format section provides a clear 4-step sequence for responses, and the 'Questions to Ask' section establishes a discovery workflow. For a non-destructive, advisory skill this is appropriate. Minor gap: no explicit decision tree or validation checkpoint for component selection beyond the table lookup.

4 / 5

Progressive Disclosure

Excellent reference index table with 8 clearly signaled one-level-deep references to specific topic files. The component selection guide acts as a navigation aid. However, no bundle files were provided, so the referenced files (references/charts.md, etc.) cannot be verified to exist, and the skill cannot be fully evaluated for structural completeness. The structure itself is well-designed.

4 / 5

Total

15

/

20

Passed

Description

27%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.

This description is essentially a topic label rather than a functional skill description. It identifies the domain (Apple HIG for content display components) but fails to describe any concrete actions the skill performs or when Claude should select it. The lack of a 'Use when...' clause and absence of specific capabilities make it very difficult for Claude to appropriately select this skill from a larger set.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Provides guidance on implementing Apple HIG-compliant content display components including lists, tables, collections, and detail views.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about iOS/macOS UI design, Apple HIG, SwiftUI/UIKit content layouts, or mentions specific components like List, Table, or NavigationStack.'

Include common synonyms and abbreviations users would naturally use, such as 'HIG', 'iOS design', 'macOS UI', 'SwiftUI', 'UIKit', and specific component names.

DimensionReasoningScore

Specificity

Names the domain (Apple Human Interface Guidelines, content display components) but provides no concrete actions—no verbs describing what the skill actually does (e.g., 'applies layout rules', 'validates component usage', 'generates compliant UI code').

2 / 5

Completeness

There is no clear 'what does this do' (no actions described) and no 'when should Claude use it' clause. The description is essentially a topic label rather than a functional description.

1 / 5

Trigger Term Quality

Includes 'Apple Human Interface Guidelines' and 'content display components' which are relevant keywords, but misses natural user phrases like 'HIG', 'iOS UI', 'SwiftUI', 'UIKit', specific component names (e.g., 'lists', 'tables', 'cards'), or abbreviations users would actually say.

3 / 5

Distinctiveness Conflict Risk

'Content display components' narrows the scope somewhat within Apple HIG, but without specifying which components or what actions are performed, it could overlap with other Apple design or UI-related skills.

3 / 5

Total

9

/

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.