CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swiftui-liquid-glass

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

Quality

76%

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 ./skills/swiftui-liquid-glass/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 skill body is well structured with a clear decision tree, actionable checklists, and executable code snippets, backed by an appropriately referenced detail guide. Its main weakness is redundancy: the same guidance is restated across Core Guidelines, the Implementation Checklist, and the decision tree.

Suggestions

Merge Core Guidelines into the Implementation Checklist (or vice versa) to eliminate the repeated container, modifier-order, interactive, and fallback rules.

Trim the Overview line "Prioritize native APIs... Keep usage consistent, interactive where needed, and performance aware", which restates points made in Core Guidelines.

DimensionReasoningScore

Conciseness

The body is mostly efficient and skill-specific, but Core Guidelines, Implementation Checklist, and the decision tree restate the same rules (GlassEffectContainer, modifier order, interactive, fallback) three times over, which goes beyond minor trimmable redundancy.

3 / 5

Actionability

Three complete, executable Swift snippets (availability-gated glass with fallback, GlassEffectContainer grouping, .buttonStyle(.glassProminent)) cover the common cases and are copy-paste ready, with specific API names used throughout.

5 / 5

Workflow Clarity

The three-path decision tree (review/improve/implement) gives a clear sequence, and the Review Checklist serves as verification checkpoints; however, there is no error-recovery feedback loop, keeping it below the top anchor.

4 / 5

Progressive Disclosure

The ~90-line overview body is appropriately split from a real 280-line reference guide (references/liquid-glass.md, verified to exist) that is one level deep and clearly signaled in the Resources section.

5 / 5

Total

17

/

20

Passed

Description

65%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 highly distinctive, with a clear statement of what the skill does, but it entirely lacks a "when to use" trigger clause and misses natural trigger terms like iOS 26. Adding an explicit usage trigger would raise completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when adopting, implementing, or reviewing Liquid Glass in SwiftUI on iOS 26+."

Mention key API names such as glassEffect, GlassEffectContainer, and glass button styles to strengthen trigger matching and specificity.

Include natural user phrasings like "glass effect" or "iOS 26 design" so the description matches how users actually ask.

DimensionReasoningScore

Specificity

The description names the domain ("SwiftUI Liquid Glass APIs") and two actions ("Implement or review") with correctness qualifiers ("correct fallbacks and modifier order"), but lists no concrete API names and is not comprehensive, matching the 'domain plus 1-2 concrete actions' anchor.

3 / 5

Completeness

The "what" is clear (implement or review Liquid Glass APIs with correct fallbacks and modifier order), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

"SwiftUI" and "Liquid Glass" are natural phrases users would say, giving good keyword coverage; a few natural terms are missing, such as "iOS 26" and the standalone "glass effect".

4 / 5

Distinctiveness Conflict Risk

"SwiftUI Liquid Glass APIs" is a clear niche with distinct triggers; virtually no other skill would match this description, so conflict risk is minimal.

5 / 5

Total

15

/

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.

Validation — 15 / 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

Path

skills/swiftui-liquid-glass/SKILL.md

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.