CtrlK
BlogDocsLog inGet started
Tessl Logo

liquid-glass

Implement and review macOS SwiftUI Liquid Glass UI. Use when adopting system glass, removing conflicting custom chrome, or building glass surfaces.

77

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, actionable design reference with a clear workflow and review checklist. Its main gap is progressive disclosure: the detailed per-surface API guidance is kept entirely inline rather than split into reference files.

Suggestions

Move the detailed API guidance for Toolbars, Search, Controls, and Custom Liquid Glass into a references file (e.g. references/glass-api.md) and keep SKILL.md as an overview that links to it, giving one-level-deep progressive disclosure.

Add a short 'Quick reference' table at the top mapping each surface (toolbar, search, sheet, custom glass) to its primary API, so the overview signals where to find detail without reading every section inline.

If splitting into reference files, link them from the relevant Workflow step (e.g. step 4 -> references/glass-api.md) so the disclosure path is explicitly signaled rather than implied by headings.

DimensionReasoningScore

Conciseness

Lean directive prose that assumes SwiftUI competence — it never explains what NavigationSplitView, glassEffect, or toolbars are, and every bullet carries actionable guidance rather than filler.

3 / 3

Actionability

Names specific APIs with clear usage conditions (e.g. 'Wrap nearby custom glass elements in one GlassEffectContainer', 'use glassEffect(... .interactive())'); as an instruction-only design skill the absence of code is not penalized because the guidance is concrete and actionable.

3 / 3

Workflow Clarity

A clearly sequenced 6-step Workflow with an explicit validation step ('Validate that glass grouping, transitions, icon treatment ... are still usable with pointer and keyboard') and a closing Review Checklist acting as a checkpoint.

3 / 3

Progressive Disclosure

Sections are well-organized and easy to navigate, but the body is a sizable inline reference (~165 lines across App Structure, Toolbars, Search, Controls, Custom Liquid Glass) with no bundle files or external references providing one-level-deep detail — all material lives in SKILL.md with heading-level navigation only.

2 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description that clearly covers capabilities, explicit use-when triggers, and a distinctive niche. It avoids fluff and over-claims while naming concrete actions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Implement and review macOS SwiftUI Liquid Glass UI', 'adopting system glass', 'removing conflicting custom chrome', 'building glass surfaces' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly states what it does ('Implement and review macOS SwiftUI Liquid Glass UI') and when to use it via an explicit 'Use when ...' clause, satisfying both what and when.

3 / 3

Trigger Term Quality

'Liquid Glass', 'system glass', 'glass surfaces', and 'custom chrome' are natural terms a developer adopting this design system would say; coverage is strong rather than jargon-only.

3 / 3

Distinctiveness Conflict Risk

The macOS SwiftUI Liquid Glass niche is narrow with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.