CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-inputs

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

44

Quality

45%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 overview of Apple HIG input principles with an excellent progressive-disclosure layout that points to real, one-level-deep reference files. It is concise and specific at the principle level, though its workflow sequencing and in-body actionability could be tighter.

DimensionReasoningScore

Conciseness

The body uses lean one-line principles grouped by input category without explaining concepts Claude already knows, though the repeated description line and the filler "When to Use" section could be trimmed.

4 / 5

Actionability

Principles give specific design directives ("Don't override system gestures", "Support pressure, tilt, and hover") but the body stays at guideline level with the executable detail deferred to references, leaving minor gaps.

3 / 5

Workflow Clarity

The Output Format and Questions to Ask sections imply a light sequence, but checkpoints are implicit and there is no validation step; acceptable for a non-destructive reference skill yet the sequence is not crisply defined.

3 / 5

Progressive Disclosure

A well-signaled Reference Index table links 13 one-level-deep reference files, all of which exist in references/, with the overview appropriately split from the detailed material for easy navigation.

5 / 5

Total

15

/

20

Passed

Description

25%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 fails to describe what the skill does or when to use it, instead giving a generic behavior rule about consulting a context file. It lacks domain keywords, a capability statement, and explicit trigger guidance, making it indistinguishable from related skills.

Suggestions

Rewrite the description to state the capability first, e.g. "Provides Apple Human Interface Guidelines for input methods (touch, pencil, keyboard, pointer, eyes, controllers) across platforms."

Add an explicit trigger clause: "Use when designing input interactions, gestures, or keyboard/pointer accessibility for Apple platforms."

Replace the procedural context-file instruction with domain-specific natural keywords (gestures, Scribble, focus system, MFi controllers) so the skill surfaces for the right requests.

DimensionReasoningScore

Specificity

The description gives two concrete procedural actions ("Check for .claude/apple-design-context.md" and "only ask for information not already covered") but never names the skill's actual domain (Apple HIG input design), so capabilities remain minimal and generic.

2 / 5

Completeness

It states no real "what" (the skill's capability is unstated) and lacks an explicit "Use when..." trigger clause, offering only a behavioral directive; the missing trigger guidance caps it well below a passing level.

2 / 5

Trigger Term Quality

Only generic terms like "asking questions" and "context" appear; none of the natural phrases a user would say (HIG, gestures, inputs, platforms, Apple) are present.

2 / 5

Distinctiveness Conflict Risk

The context-checking instruction is broad procedural advice that could apply to any skill using a context file, creating high overlap risk with sibling HIG skills rather than a distinct niche.

2 / 5

Total

8

/

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.