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.

53

Quality

60%

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

67%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured design guidance skill that efficiently communicates Apple HIG principles for status and progress components. Its main strengths are clear organization, a useful reference index, and good progressive disclosure. Its primary weakness is the lack of concrete code examples (SwiftUI/UIKit snippets) that would make the guidance immediately actionable, and some minor verbosity in explaining concepts Claude already understands.

Suggestions

Add concrete SwiftUI/UIKit code snippets for common patterns (e.g., ProgressView with determinate vs indeterminate states) to improve actionability.

Remove the vacuous 'When to Use' section at the bottom, which adds no information beyond restating the obvious.

DimensionReasoningScore

Conciseness

Generally efficient with numbered principles that are concise and informative. Minor over-explanation in a few places (e.g., 'A filling progress bar gives users a clear sense of remaining work' and 'A spinner communicates work is happening without promising a timeframe' explain things Claude already understands). The 'When to Use' section at the bottom is vacuous filler.

4 / 5

Actionability

The skill provides clear design guidelines and decision criteria (determinate vs indeterminate, when to hide status bars), but lacks any concrete code examples, SwiftUI snippets, or copy-paste ready implementations. The guidance is specific enough to follow conceptually but not executable.

3 / 5

Workflow Clarity

For a guidance/instruction skill, the workflow is reasonably clear: check context file first, use the numbered principles for decisions, consult the output format for structuring responses, and ask clarifying questions. The 'Questions to Ask' and 'Output Format' sections provide good structure. However, there's no explicit sequencing of steps or validation checkpoints, though this is a non-destructive advisory skill where that matters less.

4 / 5

Progressive Disclosure

Good structure with a clear reference index table pointing to three separate reference files with topic descriptions. The main skill provides an overview with principles while deferring details to references. However, no bundle files were provided to verify the references exist, and the Related Skills section adds useful cross-references. Minor gap: the reference table could better describe what specific content each file contains.

4 / 5

Total

15

/

20

Passed

Description

52%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 identifies a clear niche (Apple HIG status and progress components) and lists specific component types, but it lacks an explicit 'Use when...' clause and doesn't describe what actions the skill performs (e.g., reviewing designs, providing implementation guidance, generating code). The description reads more like a topic label than an actionable skill description.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about Apple HIG progress indicators, loading states, status bars, or activity rings in iOS/macOS apps.'

Specify what the skill actually does — e.g., 'Provides design guidance and implementation recommendations for...' rather than just listing component types.

Include synonym coverage such as 'loading spinner', 'progress bar', 'Human Interface Guidelines', 'iOS design', 'macOS design' to improve trigger term matching.

DimensionReasoningScore

Specificity

Names the domain (Apple HIG, status and progress UI components) and lists a few concrete items (progress indicators, status bars, activity rings), but doesn't describe what actions the skill performs with them (e.g., 'provides guidance on implementing', 'reviews designs against').

3 / 5

Completeness

Provides a partial 'what' (guidance for status and progress UI components) but lacks any explicit 'when' clause. There is no 'Use when...' or equivalent trigger guidance, which per the rubric should cap completeness at 3, and the 'what' itself is vague about the actual actions performed.

2 / 5

Trigger Term Quality

Includes several natural keywords users might use: 'Apple HIG', 'progress indicators', 'status bars', 'activity rings'. Missing some variations like 'loading spinner', 'progress bar', 'Human Interface Guidelines', or 'iOS/macOS design guidelines'.

4 / 5

Distinctiveness Conflict Risk

Fairly distinct by narrowing to Apple HIG and specifically status/progress UI components. Minor overlap risk with a broader Apple HIG skill or a general UI component design skill, but the specific component types help differentiate it.

4 / 5

Total

13

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

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.