CtrlK
BlogDocsLog inGet started
Tessl Logo

swiftui-liquid-glass

Implement or review SwiftUI Liquid Glass APIs with correct fallbacks and modifier order.

64

Quality

78%

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/swiftui-liquid-glass/SKILL.md

The canonical home for this skill is swiftui-liquid-glass in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 actionable and well-structured with executable snippets and a clean decision tree, pointing detail out to a real reference file; its only real gap is the absence of explicit verification/build checkpoints in the workflow.

Suggestions

Add an explicit verification step to each workflow branch (e.g., build for an iOS 26 target and confirm the fallback path compiles under an earlier deployment target).

Trim overlap between Core Guidelines and the Review/Implementation checklists so each list adds distinct value.

In Resources, note briefly what the reference file contains so readers know when to consult it versus the inline snippets.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding explaining what SwiftUI or Liquid Glass is, though the Core Guidelines and Review/Implementation checklists repeat a few points that could be tightened.

4 / 5

Actionability

Copy-paste-ready Swift snippets cover the common cases (single glass element with fallback, GlassEffectContainer grouping, glass button style) alongside specific modifier and API names.

5 / 5

Workflow Clarity

A three-branch decision tree (review / improve / implement) plus review and implementation checklists give a clear sequence, but there are no explicit build/verify checkpoints to confirm the result compiles or renders.

4 / 5

Progressive Disclosure

The SKILL.md is a clear overview split into focused sections with a well-signaled one-level-deep reference (references/liquid-glass.md, which exists) in the Resources section.

5 / 5

Total

18

/

20

Passed

Description

70%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 specific and distinct, naming concrete actions and a clear niche, but it omits any explicit trigger/"when to use" guidance, which limits its completeness.

Suggestions

Add an explicit "Use when..." clause naming the trigger situations (e.g., adopting or reviewing Liquid Glass in SwiftUI UI, handling iOS 26+ availability/fallbacks).

Include a couple of natural synonyms users might say, such as "glass effect" or "glass button styles", to broaden trigger coverage.

Consider mentioning the iOS 26+ availability context directly in the description so the version-gated scope is immediately clear.

DimensionReasoningScore

Specificity

"Implement or review SwiftUI Liquid Glass APIs with correct fallbacks and modifier order" names the domain plus two concrete actions (implement, review) and specific quality concerns (fallbacks, modifier order), with only minor coverage gaps.

4 / 5

Completeness

It states a clear "what" (implement/review Liquid Glass APIs with fallbacks and modifier order) but has no "Use when..." clause or explicit "when" guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say are present ("SwiftUI", "Liquid Glass", "fallbacks", "modifier order"), though a few common synonyms or explicit API names like "glass effect" are missing.

4 / 5

Distinctiveness Conflict Risk

"SwiftUI Liquid Glass APIs" is a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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.