CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-search

Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.

55

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

The canonical home for this skill is hig-components-search in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 overview with excellent progressive disclosure via a clear reference index to real bundle files, but its workflow is only implicitly sequenced and its actionable guidance is moderately concrete without executable specifics. Conciseness is good apart from a redundant trailing 'When to Use' section.

Suggestions

Number the operating sequence explicitly (check apple-design-context.md → ask clarifying questions → produce the output format) and place 'Questions to Ask' before 'Output Format'.

Remove or replace the filler 'When to Use' line with a concrete trigger for when to invoke this skill.

Add one short concrete example (e.g. a sample output for a search-field recommendation) to lift actionability.

DimensionReasoningScore

Conciseness

The body is lean, lists concise directives without re-explaining what HIG or the components are, and assumes Claude's competence; minor padding exists in the redundant trailing 'When to Use' section ('applicable to execute the workflow or actions described in the overview') and the promotional footer, fitting the 'efficient; minor instances that could be trimmed' anchor.

4 / 5

Actionability

It gives specific design directives (e.g. 'Command-F and system search shortcuts should activate search', 'Show current page and total count') and a concrete 3-part output format, but as an instruction-only skill it lacks executable commands/code and leaves key specifics (e.g. exact scope-control patterns) to the references, matching 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

An implicit sequence exists (check for apple-design-context.md, ask the listed questions, produce the specified output format) but it is not numbered as a workflow and the 'Questions to Ask' section is ordered after 'Output Format', leaving the sequence implicit without checkpoints; no destructive/batch operations are present so no lower cap applies.

3 / 5

Progressive Disclosure

The body is a concise overview with a well-signaled 'Reference Index' table pointing one level deep to real files (references/search-fields.md, page-controls.md, path-controls.md, all present), content is appropriately split, and navigation is easy, matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

15

/

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 names the domain and concrete components but uses a generic 'guidance for' action and omits any explicit 'Use when...' trigger clause, which caps completeness. Trigger term coverage is good with minor synonym gaps.

Suggestions

Replace 'guidance for' with concrete actions, e.g. 'Recommends and specifies Apple HIG navigation components (search fields, page controls, path controls) with platform-specific behavior'.

Add an explicit trigger clause, e.g. 'Use when designing or reviewing search, paging, or file-path navigation UIs on Apple platforms'.

Include natural synonyms such as 'search bar' and 'breadcrumbs' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Apple HIG guidance') and three concrete components ('search fields, page controls, and path controls'), but the action verb ('guidance for') is generic rather than enumerating what the skill does, matching the anchor that names the domain and a few concrete items without comprehensive action coverage.

3 / 5

Completeness

It clearly answers 'what' (Apple HIG guidance for these navigation components) but provides no 'Use when...' trigger clause, so per the guideline a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

It surfaces several natural terms a user would say — 'search fields', 'page controls', 'path controls', 'navigation-related components' — with good coverage, though a few natural synonyms (e.g. 'search bar', 'breadcrumbs') are missing, fitting the 'good keyword coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The niche (Apple HIG search fields, page controls, path controls) is mostly distinct with clear triggers, though there is minor overlap risk with the sibling hig-components-controls skill that also covers search-interface controls.

4 / 5

Total

14

/

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.