CtrlK
BlogDocsLog inGet started
Tessl Logo

hig

Fact lookup: Apple Human Interface Guidelines corpus (greppable markdown). Query on demand for accessibility and ergonomic minimums (hit-target sizes, Dynamic Type), platform terminology, system component capabilities, and App-Review-relevant conventions. Not design direction.

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/hig/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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-organized and concise with a genuinely useful escalation workflow, but its core premise is broken: every referenced local documentation file is missing from the bundle, so the advertised greppable corpus and all grep examples do not work. This is the dominant defect; secondary issues are the thrice-repeated 'not design direction' framing and Quick Facts content duplicated from the (absent) reference files.

Suggestions

Ship the referenced markdown files (hig-index.md, color.md, buttons.md, etc.) in the skill bundle, or restructure the body around the sosumi.ai fetch path if local files are not distributed — the current broken references are the skill's central failure.

State the 'facts, not design direction' boundary once and cut the repetitions in the intro paragraphs.

Either drop the Quick Facts section (its content belongs in the referenced files) or trim it to a few facts not otherwise available, to avoid duplicating the greppable corpus.

DimensionReasoningScore

Conciseness

The body is efficient — compact file tables, grep examples, and no explanation of concepts Claude already knows — but the "facts, not design direction" framing is repeated three times (intro, the bolded paragraph, and the use-it paragraph) and the Quick Facts section duplicates content that belongs in the referenced files, matching anchor 4's minor trimmable over-explanation.

4 / 5

Actionability

The grep commands are concrete and copy-paste shaped, but they target files (color.md, buttons.md, hig-index.md) that do not exist in the skill bundle, so the primary lookup commands fail as written; only the sosumi.ai fallback path is actually executable — anchor 3's concrete-but-missing-key-details fit.

3 / 5

Workflow Clarity

"Fetching More Docs" lays out a clearly sequenced three-step escalation (local grep, then other installed skills, then the sosumi.ai mirror with a concrete URL-mapping example), and the skill is read-only so no validation cap applies; it stops short of anchor 5 because "Searching the Docs" and the escalation path are presented as separate sections rather than one integrated lookup workflow.

4 / 5

Progressive Disclosure

The body's entire structure rests on 30+ referenced local markdown files and asserts "All key HIG documentation is available locally", yet none of those files exist in the bundle — every link and grep example is broken, defeating navigation for the skill's primary use case despite otherwise clear organization, matching anchor 2 over higher anchors that assume the references actually resolve.

2 / 5

Total

13

/

20

Passed

Description

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

A distinctive, concrete description that clearly states what the skill does and draws a sharp boundary against design-aesthetics skills. Its main weakness is the absence of any explicit 'Use when...' trigger guidance and the missing 'HIG' acronym and platform synonyms that users would naturally say.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about Apple HIG rules, iOS/macOS design conventions, or App Review design requirements" — this would raise completeness from 3 to 4-5.

Include the acronym "HIG" and natural synonyms like "iOS design guidelines" or "Apple design conventions" alongside the full "Apple Human Interface Guidelines" phrase for better trigger-term coverage.

DimensionReasoningScore

Specificity

The description names several concrete capability areas ("accessibility and ergonomic minimums (hit-target sizes, Dynamic Type), platform terminology, system component capabilities, and App-Review-relevant conventions"), but the action surface is a single one (fact lookup/query) with minor coverage gaps, matching anchor 4 rather than the multi-action comprehensiveness of anchor 5.

4 / 5

Completeness

The "what" is explicit and concrete ("Fact lookup: Apple Human Interface Guidelines corpus (greppable markdown). Query on demand for..."), but there is no "Use when..." clause or equivalent explicit trigger guidance; "Query on demand" only weakly implies when, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keywords are present ("Apple Human Interface Guidelines", "accessibility", "hit-target sizes", "Dynamic Type", "App-Review"), but common variations users would actually say are missing — notably the "HIG" acronym itself, "iOS/macOS design", and "Apple design guidelines" — so it falls short of anchor 5's synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear, unambiguous niche (Apple HIG fact lookup) and explicitly separates itself from design-direction skills with "Not design direction", giving minimal conflict risk with closely related skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 32 missing

Warning

Total

14

/

16

Passed

Repository
Prisma-Labs-Dev/apple-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.