CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-components-controls

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

43

Quality

44%

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

The canonical home for this skill is hig-components-controls 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 body is a well-structured overview of Apple HIG selection/input controls with concrete per-control heuristics, a clear output template, and an excellent one-level reference index to 14 real files. Its main weakness is filler — a duplicated preamble, a boilerplate "When to Use", and a promotional footer — that slightly dilutes an otherwise lean skill.

DimensionReasoningScore

Conciseness

The Key Principles are tight and useful, but the body carries unnecessary filler — the intro line repeats the frontmatter instruction, the "When to Use" section is generic boilerplate ("applicable to execute the workflow or actions described in the overview"), and the promotional footer adds nothing — so it sits at anchor 3 rather than 4.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete: specific heuristics like "2-5 items, roughly equal importance, short labels", "changes take effect immediately" vs "commit on confirmation", and a four-part Output Format with an information-gathering question list; minor gaps (no platform/keyboard-type specifics inline) keep it just below anchor 5.

4 / 5

Workflow Clarity

The advisory workflow is legibly sequenced via Questions to Ask (gather data type, option count, platform, screen context) feeding the Output Format (recommendation, state management, validation, accessibility); it is a simple non-destructive skill so no validation cap applies, but it is advisory rather than a strict checkpointed process.

4 / 5

Progressive Disclosure

The Reference Index table signals one-level-deep links to 14 real reference files (all present in references/) with topic and key-content columns, keeping the body a navigable overview while detail lives in separate files — a clean match for anchor 5.

5 / 5

Total

16

/

20

Passed

Description

17%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 is a generic behavioral preamble about checking a context file before asking questions rather than a statement of what the skill does or when to use it. It omits the actual domain (Apple HIG selection/input controls) and any trigger guidance, so it fails to distinguish the skill or invite correct invocation.

Suggestions

Rewrite the description to state the skill's purpose, e.g. "Recommends Apple HIG selection and input controls (toggles, segmented controls, sliders, pickers, steppers, text fields, combo boxes, token fields) with state, validation, and accessibility guidance."

Add an explicit trigger clause: "Use when choosing or designing selection/input controls for Apple platforms, or when the user mentions toggles, pickers, sliders, segmented controls, or HIG controls."

Move the "check .claude/apple-design-context.md before asking questions" instruction into the body as a workflow note rather than occupying the description field.

DimensionReasoningScore

Specificity

The description states concrete meta-actions ("Check for .claude/apple-design-context.md before asking questions", "Use existing context and only ask for information not already covered") but never names the skill's actual domain — Apple HIG selection and input controls — so it stays at the generic-action level rather than anchor 1 or 3.

2 / 5

Completeness

It offers only a vague, misdirected 'what' (a context-checking procedure) and no 'when'/"Use when..." clause describing the skill's purpose; the judging guideline caps completeness at 3 for a missing trigger clause, and this is below that.

2 / 5

Trigger Term Quality

No natural trigger terms a user would say to invoke this skill (e.g. toggles, segmented controls, pickers, Apple HIG) appear; the language ("before asking questions", "existing context") is entirely generic, matching anchor 1.

1 / 5

Distinctiveness Conflict Risk

The text is broad boilerplate that could prefix almost any Apple-design skill; the only narrowing cue is the literal filename apple-design-context.md, leaving high overlap risk rather than the entirely-generic anchor 1.

2 / 5

Total

7

/

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.