CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-status

Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings.

60

Quality

70%

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-status/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-organized, lean overview that appropriately offloads detail to three real one-level-deep reference files and provides concrete HIG guidance with a clear output structure. Minor gains are available from trimming boilerplate and naming concrete framework APIs.

DimensionReasoningScore

Conciseness

The body is mostly lean — short bolded principles with brief HIG-specific rationale and a reference table — with only minor trims needed (the generic 'When to Use' boilerplate and the Raintree footer add little).

4 / 5

Actionability

Concrete, specific guidance is given (determinate vs indeterminate, 'longer than a second or two', 'Use HealthKit APIs', ring color conventions), though it stops short of naming concrete SwiftUI/UIKit components like ProgressView or UIProgressView.

4 / 5

Workflow Clarity

The 'Output Format' section gives a clear sequence of deliverables and 'Questions to Ask' frames discovery; no destructive/batch operation requires validation checkpoints, so the absence of explicit checkpoints is acceptable.

4 / 5

Progressive Disclosure

A concise overview with a well-signaled Reference Index table linking three real one-level-deep reference files (progress-indicators.md, status-bars.md, activity-rings.md, all confirmed present in ./references/), making navigation easy.

5 / 5

Total

17

/

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 with good keyword coverage, but it only states what the skill covers and omits any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause would materially raise completeness and trigger discoverability.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when designing or reviewing status/progress UI — progress indicators, status bars, or activity rings — per Apple HIG.'

Include a few natural synonyms/users' phrasings ('spinner', 'loading indicator', 'iOS/watchOS status bar') to broaden trigger coverage.

Mention concrete actions the skill performs ('recommends indicator type', 'audits placement and accessibility') rather than only 'guidance for'.

DimensionReasoningScore

Specificity

Names the domain ('Apple HIG guidance for status and progress UI components') and enumerates three concrete component types (progress indicators, status bars, activity rings), but describes no concrete actions beyond 'guidance for'.

3 / 5

Completeness

The 'what' is clear (HIG guidance for these status/progress components) but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural HIG-domain keywords are present ('Apple HIG', 'progress indicators', 'status bars', 'activity rings'); a few common synonyms users might say are missing ('spinner', 'loading indicator', platform names like iOS/watchOS).

4 / 5

Distinctiveness Conflict Risk

A clear niche (Apple HIG status/progress components) with distinct triggers, but minor overlap risk with sibling HIG skills (hig-components-system, hig-inputs, hig-technologies) noted in the body.

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.