Name: hig-components-search
Rating: 52.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

hig-components-search

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

Quality

58%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/hig-components-search/SKILL.md

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

Quality

Content

63%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 a well-structured overview with excellent progressive disclosure (real, one-level-deep references) and a clear loose workflow, but it is mildly padded with a filler 'When to Use' section and its principles lean advisory rather than tightly executable. Removing the filler and tightening the principles into concrete specifications would raise the conciseness and actionability scores.

Suggestions

Replace the generic 'When to Use' filler with concrete trigger conditions or remove it entirely.

Tighten advisory principles into executable specifications (e.g. 'Place search fields in the navigation bar / top of list' with the specific UIKit/AppKit control names).

Drop the built-by footer and trim the Related Skills list to only the directly relevant navigation-related siblings to reduce non-operational tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with terse principle statements, but it mildly over-explains concepts Claude already knows and includes a filler 'When to Use' section ('applicable to execute the workflow or actions described in the overview') plus a built-by footer that add tokens without operational value.	3 / 5
Actionability	It gives some concrete guidance (placement of search fields, Command-F activation, scope buttons) but the principles are largely advisory ('should', 'place where users expect them') and the Output Format is abstract, leaving key execution details unspecified.	3 / 5
Workflow Clarity	As a single-purpose guidance skill it qualifies for the simple-skill leniency, and the Questions-to-Ask plus Output Format give a clear, unambiguous loose sequence (ask -> recommend -> specify -> note platform diffs) with only minor gaps and no destructive validation needs.	4 / 5
Progressive Disclosure	The SKILL.md is a clear overview with a well-signaled Reference Index table linking to three real, one-level-deep reference files (search-fields.md, page-controls.md, path-controls.md) with topic and key-content columns, matching the clear-overview + one-level-deep + easy-navigation anchor.	5 / 5
	Total	15 / 20 Passed

Description

53%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 its niche (Apple HIG navigation components) and enumerates the three covered component types, but it lacks any 'when to use' trigger guidance and frames capabilities as a subject rather than concrete actions. Adding a 'Use when...' clause with natural user phrasings would lift completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing or reviewing iOS/iPadOS/macOS/visionOS navigation UIs involving search fields, page controls, or path controls.'

Include natural synonyms users actually say ('search bar', 'breadcrumbs', 'pagination dots') to improve trigger term coverage.

Reframe as concrete actions ('Recommends and specifies navigation components: search fields, page controls, path controls') rather than 'guidance for'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Apple HIG navigation components) and lists three concrete component types (search fields, page controls, path controls), but frames them as a subject ('guidance for') rather than concrete actions, so it sits at the 'names domain and 1-2 concrete actions' level rather than listing several specific actions.	3 / 5
Completeness	It clearly states 'what' the skill covers (HIG guidance for navigation components) but provides no 'when' / trigger guidance at all; per the rubric guideline, a missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant keywords ('search fields, page controls, path controls', 'navigation', 'Apple HIG') a user might say, but omits common synonyms and variations (search bar, breadcrumbs, pagination dots) and any 'Use when...' trigger phrasing, leaving it with some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The niche (Apple HIG navigation-specific components) is mostly distinct from sibling skills, though 'navigation-related components' is broad enough to create minor overlap with related hig-components skills, placing it at 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/hig-components-search/SKILL.md
Commit: 57c135b

Reviewed: 4 days 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.