CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-liquid-glass

Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.

57

Quality

64%

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

Quality

Content

82%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 content is a highly actionable, well-sequenced audit prompt with concrete grep patterns, copy-paste Swift recommendations, and explicit per-pattern verification checkpoints. Its main weakness is progressive disclosure: everything lives in one long file with no bundle references, and a few explanatory columns add minor verbosity.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no generic explanations of SwiftUI/PDF concepts), with concrete grep patterns and code; minor over-explanation in the Phase 3 "Why it matters" column and framing prose could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready Swift code recommendations and exact executable Grep/Glob patterns covering the common adoption cases across all 7 detection patterns.

5 / 5

Workflow Clarity

Phases 1–5 are clearly sequenced with explicit "Verify: Read matching files" checkpoints and an evidence requirement, but as a read-only audit it lacks a true validate→fix→retry feedback loop, leaving a minor gap.

4 / 5

Progressive Disclosure

Structure is well-organized into phases/patterns with one-level-deep external references in the Related section, but the single 300-line SKILL.md inlines pattern detail and large tables that could be split into reference files (no bundle files exist).

4 / 5

Total

17

/

20

Passed

Description

47%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 functions as a pure trigger clause: it clearly signals when to invoke the skill but omits any statement of what the skill does. Trigger terms are natural and fairly specific, but the missing capability statement caps completeness and specificity.

Suggestions

Add a leading capability clause stating what the skill does, e.g. "Audits Liquid Glass adoption opportunities and gaps in iOS 26+ SwiftUI/UIKit codebases."

Combine what + when in one sentence: "Audits Liquid Glass adoption... Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration."

Keep the existing trigger phrases but precede them with concrete actions (audit, detect, recommend) to lift specificity above 2.

DimensionReasoningScore

Specificity

The description names the domain ("Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration") but states no concrete actions the skill performs — it only lists trigger topics, so actions are minimal/generic.

2 / 5

Completeness

It provides an explicit "Use when..." trigger (the "when") but never states what the skill does (no "what"), matching the anchor where only "when" is present without "what".

2 / 5

Trigger Term Quality

It includes several natural phrases a user would say ("Liquid Glass review", "iOS 26 UI updates", "toolbar improvements", "visual effect migration"), giving good keyword coverage though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

"Liquid Glass" is a distinct niche with minimal conflict risk, though the broader terms "toolbar improvements" and "iOS 26 UI updates" create minor overlap with general iOS UI skills.

4 / 5

Total

12

/

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
CharlesWiltgen/Axiom
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.