CtrlK
BlogDocsLog inGet started
Tessl Logo

macos-liquid-glass

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

65

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 ./.agents/skills/macos-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 body is a well-organized, API-specific reference that assumes Claude's SwiftUI competence and provides a clear workflow plus a review checklist. Its main gap is the absence of concrete code examples, though its guidance is otherwise executable at the API-name level.

Suggestions

Add one or two short executable SwiftUI snippets (e.g. a minimal glassEffect + GlassEffectContainer grouping) to lift actionability from API-name guidance to copy-paste-ready code.

Consider trimming the Guardrails section, which largely restates the affirmative rules above it as negations, to improve token efficiency.

Add an explicit validate-and-iterate checkpoint (e.g. build, run as .app bundle, confirm glass grouping visually, fix and re-check) to the Workflow to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

The body is dense and largely free of concept explanations Claude already knows, listing API names and rules directly; it edges toward verbosity in the repeated 'Do not ...' Guardrails restating the affirmative rules, but every token is mostly load-bearing.

4 / 5

Actionability

It names concrete, specific SwiftUI APIs to use (glassEffect, GlassEffectContainer, glassEffectID, ToolbarSpacer, sharedBackgroundVisibility, scrollEdgeEffectStyle, etc.) with clear applicability guidance, but provides no complete executable code examples for the common cases.

4 / 5

Workflow Clarity

The numbered Workflow gives a clear sequence and a closing Review Checklist that serves as a validation checkpoint, with pointer and keyboard usability validation in step 5; it lacks an explicit validate-and-retry feedback loop, but the operations are design adjustments rather than destructive batch operations.

4 / 5

Progressive Disclosure

No bundle files exist; the skill is a self-contained, well-sectioned body under ~170 lines with clear headers (Overview, Workflow, App Structure, Toolbars, Search, Controls, Custom Liquid Glass, Review Checklist, Guardrails), fitting the simple-skill exception for scoring 5 without external references.

5 / 5

Total

17

/

20

Passed

Description

78%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 well-formed with an explicit 'Use when' clause covering both what and when, and uses natural trigger language. It is slightly limited in action specificity since the verbs are scoped to a single adoption theme.

DimensionReasoningScore

Specificity

Names the macOS SwiftUI Liquid Glass domain and the concrete actions 'Implement and review', plus specific sub-tasks ('adopting system glass', 'removing conflicting custom chrome', 'building glass surfaces'), but these are scoped adoption activities rather than a comprehensive list of distinct operations.

3 / 5

Completeness

It clearly answers 'what' ('Implement and review macOS SwiftUI Liquid Glass UI') and 'when' with an explicit 'Use when' clause listing three concrete trigger conditions.

5 / 5

Trigger Term Quality

'Liquid Glass UI', 'system glass', 'custom chrome', and 'glass surfaces' are natural terms a developer would say; minor common synonyms or extension-style phrasing are absent but coverage is solid.

4 / 5

Distinctiveness Conflict Risk

The 'macOS SwiftUI Liquid Glass' niche is specific and distinct, though it has minor overlap with general SwiftUI/macOS design skills; the trigger phrases narrow it well.

4 / 5

Total

16

/

20

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
robinebers/openusage
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.