CtrlK
BlogDocsLog inGet started
Tessl Logo

swiftui-expert-skill

Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.

64

Quality

77%

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

Quality

Content

67%Scale 1-5

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

This is a well-structured, comprehensive SwiftUI skill that covers state management, view composition, performance, animations, accessibility, and Liquid Glass adoption with clear workflows and extensive cross-references. Its main weaknesses are redundancy between the core guidelines and the review checklist (which largely duplicate each other), and a lack of inline code examples in most guideline sections beyond the Liquid Glass quick reference. The progressive disclosure structure is strong with 14 reference files, though the main file could be leaner.

Suggestions

Consolidate the review checklist and core guidelines sections — either keep the checklist as the primary reference and trim the prose guidelines, or merge them into a single section to eliminate duplication.

Add 1-2 brief executable code examples to the State Management and Animation core guidelines sections (e.g., showing correct @StateObject vs @ObservedObject usage, or .animation(_:value:) vs withAnimation).

DimensionReasoningScore

Conciseness

The skill is comprehensive but noticeably verbose. The review checklist largely duplicates the core guidelines section, and many items in the workflow decision tree repeat the same references. The property wrapper table is useful but the surrounding text could be tighter. Some sections (like View Composition guidelines) state things Claude already knows ('keep view body simple and pure').

3 / 5

Actionability

The skill provides concrete, actionable guidance with specific property wrapper rules, a useful quick reference table, and executable Liquid Glass code examples with fallback patterns. However, most sections are rule-based rather than code-example-driven — the core guidelines for state management, performance, and animations lack inline code snippets, relying instead on references to external files.

4 / 5

Workflow Clarity

The workflow decision tree clearly sequences three distinct workflows (review, improve, implement) with ordered steps and cross-references. Each workflow starts with consulting latest-apis.md, which is good. However, there are no explicit validation checkpoints or feedback loops — the review checklist serves as a post-hoc verification but isn't integrated into the workflow steps themselves. Since this isn't a destructive/batch operation, the missing feedback loops don't trigger the cap at 3.

4 / 5

Progressive Disclosure

The skill has excellent structure with a clear overview, decision tree, core guidelines, quick reference, review checklist, and a well-organized references section pointing to 14 separate reference files. References are one level deep and clearly signaled. However, since no bundle files were provided, we cannot verify the referenced paths actually exist. The main SKILL.md is quite long (~200+ lines) and the review checklist could arguably live in a separate reference file to reduce the main file's length.

4 / 5

Total

15

/

20

Passed

Description

87%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.

This is a strong skill description that clearly communicates both what the skill does and when to use it. It covers a well-defined niche (SwiftUI development) with specific sub-domains and includes an explicit 'Use when' clause with concrete trigger scenarios. Minor improvements could include additional natural trigger terms and more granular capability enumeration.

DimensionReasoningScore

Specificity

Lists several concrete actions (write, review, improve) and specific domains (state management, view composition, performance, Liquid Glass adoption), though it could enumerate more specific capabilities like 'create custom views, implement navigation, handle animations'.

4 / 5

Completeness

Clearly answers both 'what' (write, review, improve SwiftUI code following best practices for state management, view composition, performance, and Liquid Glass adoption) and 'when' (building new SwiftUI features, refactoring existing views, reviewing code quality, adopting modern SwiftUI patterns) with explicit trigger phrases.

5 / 5

Trigger Term Quality

Includes strong natural keywords like 'SwiftUI', 'state management', 'view composition', 'iOS 26+', 'Liquid Glass', 'refactoring', 'code quality'. Missing some common synonyms or terms users might say like 'UI layout', 'modifiers', '@State', '@Binding', 'preview', or 'Xcode'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with clear niche targeting SwiftUI specifically, including the very specific 'iOS 26+ Liquid Glass adoption' differentiator. Unlikely to conflict with generic coding skills or other UI framework skills.

5 / 5

Total

18

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

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.