CtrlK
BlogDocsLog inGet started
Tessl Logo

hig-technologies

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

38

Quality

36%

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

The canonical home for this skill is hig-technologies 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 body is a well-structured overview that leverages progressive disclosure effectively, with concise per-technology principles and a clean reference index to detailed files. Its main weakness is workflow clarity: the output guidance lacks explicit validation or verification steps.

Suggestions

Add a brief validation step to the Output Format, e.g. cross-check each checklist item against the cited reference file and confirm required vs optional items map to App Store review criteria.

Make the workflow more sequenced by ordering the Output Format into an explicit produce-then-verify flow rather than a flat list of deliverables.

Tighten a few principle clauses that restate obvious guidance to push conciseness toward fully lean.

DimensionReasoningScore

Conciseness

The body is efficient — each Key Principle is a single bolded sentence with a brief clause, and no time is spent explaining concepts Claude already knows; only minor trimming opportunities exist.

4 / 5

Actionability

As an instruction-only skill the guidance is concrete per technology (e.g. 'Standard Apple Pay button styles', 'Every element has a meaningful VoiceOver label'), but the Output Format describes what to produce rather than giving specific executable steps, leaving guidance partly abstract.

3 / 5

Workflow Clarity

The Output Format and Questions to Ask sections provide a rough sequence, but there are no validation checkpoints or feedback loops for verifying the produced guidance against the source references, so checkpoints are implicit.

3 / 5

Progressive Disclosure

The Reference Index is a clear overview table linking to 28 one-level-deep reference files, all of which exist on disk, with topics and key content clearly signaled for easy navigation.

5 / 5

Total

15

/

20

Passed

Description

8%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 frontmatter description fails to describe the skill's purpose: it omits any mention of Apple HIG technologies, gives no natural trigger terms, and provides neither a clear 'what' nor a 'when'. It reads as a generic behavioral directive rather than a skill description.

Suggestions

Rewrite the description to state the actual capability, e.g. 'Provides Apple Human Interface Guidelines for platform technologies (Siri, Apple Pay, HealthKit, CarPlay, AR, etc.) to review and design app integrations.'

Add an explicit 'Use when...' clause naming natural triggers such as 'Apple HIG', 'Apple technologies', 'App Store review', or specific frameworks like 'Apple Pay' or 'HealthKit'.

Remove the context-file behavioral instruction from the description and move it into the body, so the description conveys capability and triggers instead of internal process.

DimensionReasoningScore

Specificity

The description names one concrete action ('Check for .claude/apple-design-context.md before asking questions') but never states the skill's actual domain (Apple HIG technologies) or any capability actions, leaving it minimal and generic rather than entirely vacuous.

2 / 5

Completeness

It answers neither 'what does this do' (no mention of Apple technology guidance) nor 'when should Claude use it' (no Use-when clause), satisfying the anchor for missing both.

1 / 5

Trigger Term Quality

It contains no natural keywords a user would say when needing this skill — only the technical file path 'apple-design-context.md' and a behavioral instruction, with no terms like 'Apple HIG', 'technologies', or platform names.

1 / 5

Distinctiveness Conflict Risk

The instruction to check for a context file and only ask uncovered questions is generic behavioral guidance that could apply to nearly any skill, creating high overlap risk and no niche-specific triggers.

2 / 5

Total

6

/

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.