CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swiftui-layout-components

Build SwiftUI stacks, grids, lists, scroll views, forms, controls, search interfaces, and overlays. Use for ordinary layout and container decisions; route cross-size adaptation, clipping or overlap diagnosis, state architecture, navigation policy, animation choreography, and runtime profiling to dedicated skills.

Quality

94%

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

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

A well-structured decision-guide skill: lean, concrete, with proper progressive disclosure into substantive one-level-deep references and a useful validation checklist. The only weaknesses are mild redundancy in reference listings and an implicit rather than stated workflow sequence.

Suggestions

Consolidate the reference listings: keep either the inline per-topic pointers under Container Selection or the References section, not both, and drop the Contents TOC in a document this short to tighten conciseness.

Make the workflow sequence explicit (e.g., a short ordered note: check scope/compatibility, select container from the table, read the mapped reference, then verify against the Review Checklist) to strengthen workflow clarity.

Add brief error-recovery or verification guidance for the trickiest cases (e.g., what to check when taps fail on transparent rows or when lazy cells thrash), turning the Common Mistakes list into a diagnose-then-fix loop.

DimensionReasoningScore

Conciseness

The body is dense and assumes SwiftUI competence with no basic-concept padding, but the reference list is duplicated (inline under Container Selection and again in the References section) and the 9-line Contents TOC adds overhead in an already short document. Minor trimming is available, so it sits at anchor 4 rather than 5.

4 / 5

Actionability

Guidance is concrete and executable throughout: a need-to-container decision table, named APIs (containerRelativeFrame, onGeometryChange, .searchable, reorderable(), .contentShape(Rectangle())), and specific mistake-to-cause pairs. Specific examples appropriately live in the well-signaled reference files, matching the instruction-only skill pattern.

5 / 5

Workflow Clarity

Explicit checkpoints exist (inspect deployment target before versioned modifiers, read the reference before substantial containers, closing Review Checklist), but the end-to-end sequence is only implied by section order and no error-recovery guidance is given. This matches anchor 4 (clear sequence, most checkpoints, minor validation gaps) rather than 5.

4 / 5

Progressive Disclosure

Scored against the actual bundle: all five referenced files exist, are substantive (79-255 lines), and are one level deep with only a sibling cross-reference. The body signals when to read each reference (per-topic mapping plus a References index) while keeping SKILL.md a lean overview, matching the top anchor.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: third-person, concise, concrete in both capabilities and triggers, and deliberately de-scoped against adjacent skills to minimize routing conflicts. It matches the top anchor on every dimension with no fluff or over-claims.

DimensionReasoningScore

Specificity

The description enumerates eight concrete capability objects ("stacks, grids, lists, scroll views, forms, controls, search interfaces, and overlays") under a concrete build verb, giving comprehensive coverage of the layout domain with no material gaps.

5 / 5

Completeness

It clearly answers "what" (build SwiftUI stacks, grids, lists, forms, controls, search, overlays) and explicitly answers "when" with an explicit "Use for ordinary layout and container decisions" trigger clause, further sharpened by an enumerated negative scope. The 'when' is explicit and specific, not merely present, so it exceeds anchor 4.

5 / 5

Trigger Term Quality

It covers the natural vocabulary users say for this domain — stack, grid, list, form, scroll view, search, overlay, layout, container — plus boundary terms (clipping, overlap, state, navigation, animation, profiling); this is richer than the anchor-4 example with only a few terms missing.

5 / 5

Distinctiveness Conflict Risk

It explicitly routes cross-size adaptation, clipping/overlap diagnosis, state architecture, navigation policy, animation choreography, and runtime profiling to dedicated skills, establishing a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

20

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

thienqo/ios-skills

Path

skills/swiftui-layout-components/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.