Name: apple-hig
Rating: 51.2 (1 reviews)
Author: nexu-io

apple-hig

Apple Human Interface Guidelines as 14 agent skills covering platforms, foundations, components, patterns, inputs, and technologies for iOS, macOS, visionOS, watchOS, and tvOS.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/apple-hig/SKILL.md

Quality

Content

51%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 concise and well-structured as a catalogue pointer, but it offers almost no actionable guidance: the only concrete command is opening a URL, with no install instructions, no HIG usage guidance, and no validation steps. It works as a discovery stub but not as a standalone skill body.

Suggestions

Provide the concrete install command for the upstream bundle (e.g., the exact clone/copy path into the agent's skills directory) instead of 'inspect the upstream README for exact paths'.

Add at least one concrete usage example showing how the agent applies an HIG skill once installed (a sample invocation with expected output).

Include a verification step confirming the bundle is installed and invokable before directing the agent to use it.

Dimension	Reasoning	Score
Conciseness	The body is lean (~25 lines) and assumes Claude's intelligence without over-explaining HIG concepts; the only inefficiency is mild repetition of the catalogue description already present in the frontmatter.	4 / 5
Actionability	Concrete guidance is minimal — the only executable line is `open https://github.com/raintree-technology/apple-hig-skills`, with the rest being high-level hints ('inspect the upstream README', 'install the upstream bundle', 'ask the agent to invoke this skill') and no specific steps to execute.	2 / 5
Workflow Clarity	A rough sequence exists (inspect README → install bundle → invoke by name/trigger), but steps are poorly defined with no actual install command and no validation, matching the 'rough sequence present but many gaps; validation absent' anchor.	2 / 5
Progressive Disclosure	No bundle files exist and the body is a short, well-sectioned catalogue entry with a single clearly signaled one-level-deep external reference (the upstream repo URL), so navigation is trivial and structure is appropriate.	5 / 5
	Total	13 / 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 identifies a niche (Apple HIG across five platforms) with natural trigger terms, but it functions as a catalogue blurb rather than a capability statement: it enumerates coverage areas without naming concrete actions, and it lacks any 'Use when...' guidance, capping completeness. Adding explicit trigger guidance and one or two concrete verbs would lift the weaker dimensions.

Suggestions

Add a 'Use when...' clause stating when Claude should reach for this skill (e.g., designing or reviewing UI for iOS/macOS/visionOS/watchOS/tvOS).

Replace catalogue-style coverage enumeration with concrete actions the skill performs (e.g., 'Apply Apple HIG patterns to UI mockups and review designs for compliance').

Expand trigger terms with natural variations users say, such as 'UI guidelines', 'design guidelines', and 'watchOS/tvOS design'.

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates coverage areas ("platforms, foundations, components, patterns, inputs, and technologies" for five OSes) but lists no concrete actions the skill performs, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor at its lower bound.	3 / 5
Completeness	It gives a clear 'what' (a catalogue of 14 HIG skills across five Apple platforms) but includes no 'Use when...' clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Trigger terms like "apple hig", "human interface", "ios design", "macos design", "visionos design" are natural phrases a user would say, but common variations such as "UI guidelines", "design guidelines", and watchOS/tvOS design variants are missing.	4 / 5
Distinctiveness Conflict Risk	"Apple Human Interface Guidelines" tied to specific OS names is a clear niche with minimal overlap risk; it is mostly distinct, with only minor overlap against a generic design-system skill.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/apple-hig/SKILL.md
Commit: 1a7a23d

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.