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.

56

Quality

65%

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-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

68%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-organized, concise HIG reference with concrete actionable principles and a clean one-level-deep reference structure, but it presents a reference layout rather than an explicitly sequenced workflow with validation checkpoints.

Suggestions

Add an explicit numbered workflow (e.g. 1. Read .claude/apple-design-context.md → 2. Ask the unanswered Questions to Ask → 3. Produce the Output Format) so the sequence is explicit.

Trim the inline principles to a true overview and defer fuller detail to the reference files to make progressive disclosure leaner.

Add a validation/check step for the output (e.g. confirm accessibility and platform coverage are addressed before finalizing).

DimensionReasoningScore

Conciseness

The body is a tight set of bold principles each followed by a single short explanation, with no padding of concepts Claude already knows; only minor explanatory phrasing could be trimmed.

4 / 5

Actionability

Though code-free, it gives concrete actionable directives ('Show progress for operations longer than a second or two', 'Use HealthKit APIs', color conventions), satisfying the instruction-only exception with only minor gaps.

4 / 5

Workflow Clarity

A loose advisory process is implied (check .claude/apple-design-context.md → ask the listed questions → produce output in the given format), but the sequence is implicit with no validation checkpoints; no destructive/batch operations trigger the 3-cap, yet it still lacks explicit sequencing.

3 / 5

Progressive Disclosure

A Reference Index table links to three real, one-level-deep reference files (progress-indicators.md, status-bars.md, activity-rings.md) with clear navigation, though the inline principles are fairly substantial rather than a minimal overview pointing to detail.

4 / 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 scopes the skill to Apple HIG status and progress components with good trigger-term coverage and low conflict risk, but it lacks an explicit 'Use when...' trigger clause and relies on the generic verb 'guidance for' rather than naming concrete actions.

Suggestions

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

Replace the generic 'guidance for' with concrete action verbs ('Designs, evaluates, and documents status and progress UI components').

Include a few natural synonyms users might say ('spinner', 'loading indicator', 'spinner') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Apple HIG', 'status and progress UI components') and enumerates three concrete subcomponents (progress indicators, status bars, activity rings), but the only action verb is the generic 'guidance for', with no concrete design/review actions listed.

3 / 5

Completeness

The 'what' is clear (HIG guidance for status/progress components), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms a designer would say — 'progress indicators', 'status bars', 'activity rings', 'Apple HIG' — giving good keyword coverage, though a few common synonyms ('spinner', 'loading bar') are absent.

4 / 5

Distinctiveness Conflict Risk

It carves a distinct niche (Apple HIG status/progress components) with specific triggers, carrying only minor overlap risk with sibling HIG skills like hig-components-system and hig-inputs.

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.