CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-system

Apple HIG guidance for system experience components: widgets, live activities, notifications, complications, home screen quick actions, top shelf, watch faces, app clips, and app shortcuts.

57

Quality

66%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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, token-efficient overview that excels at progressive disclosure with a clean reference index to real files. Its main weakness is actionability: the body gives concrete design directives but defers most executable detail to the references, and a couple of low-value filler lines could be trimmed.

Suggestions

Inline one or two concrete, copy-paste-ready specifics per major surface (e.g. a WidgetFamily list or a Live Activity size budget) so the body is actionable without forcing a reference load.

Remove the generic 'When to Use' filler ('This skill is applicable to execute the workflow...') and the promotional footer, or replace them with a concrete trigger clause.

Tie 'Questions to Ask' explicitly into the 'Output Format' as a numbered workflow so the gather-then-recommend sequence is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and glanceable, using terse numbered design directives that assume Claude's competence; only the promotional 'Built by Raintree Technology' footer and the generic 'When to Use' line are trim candidates.

4 / 5

Actionability

Per-surface directives are concrete ('3-4 most common tasks', 'relevant SF Symbol icons', 'Design for Dynamic Island and Lock Screen'), but the executable depth is deferred to the reference files, leaving the body's guidance incomplete on its own.

3 / 5

Workflow Clarity

A clear sequence is present via 'Questions to Ask' (gather context) feeding the five-part 'Output Format' (recommendation, content strategy, update frequency, size variants, deep link); as advisory output it needs no validation checkpoints.

4 / 5

Progressive Disclosure

The body is a well-organized overview with a Reference Index table linking to nine real one-level-deep reference files, each labeled with topic and key content, making navigation easy and appropriately splitting detail from summary.

5 / 5

Total

16

/

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 scopes a distinct Apple HIG niche and surfaces many natural platform terms, but it lists domains rather than concrete actions and omits any explicit 'when to use' trigger clause. Adding a 'Use when...' sentence with concrete design verbs would lift completeness and specificity.

Suggestions

Append a 'Use when...' clause naming concrete trigger situations, e.g. 'Use when designing widgets, Live Activities, complications, or other system-experience surfaces for Apple platforms.'

Replace the generic 'guidance for' with concrete design verbs (e.g. 'Design and validate widgets, Live Activities, notifications...') to raise specificity.

Add natural synonyms/variations users say (e.g. 'lock screen widgets', 'Dynamic Island', 'Siri shortcuts') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description enumerates nine concrete component domains (widgets, live activities, notifications, complications, etc.), but the only stated action is the generic 'guidance for', with no concrete verbs like 'design', 'configure', or 'generate'.

3 / 5

Completeness

The 'what' is clear (Apple HIG guidance for system experience components), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

It includes many natural platform terms a developer would say ('widgets', 'live activities', 'complications', 'app clips', 'app shortcuts'), though synonyms/variations and an explicit trigger phrase are absent.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Apple HIG system experience components) with distinct triggers, but sibling HIG skills (status, inputs, technologies) create minor overlap risk with closely related skills.

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.