CtrlK
BlogDocsLog inGet started
Tessl Logo

guide-swiftdata

SwiftData patterns — autosave, relationships, dangerous predicates, CloudKit constraints, indexing, class inheritance. Use when writing, reviewing, or debugging SwiftData code.

70

Quality

86%

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.

An exemplary guide-skill body: lean core instructions, a well-gated conditional review workflow, and clean one-level progressive disclosure into five real reference files. The only improvements are minor — no inline quick-start example and no guidance on synthesizing or prioritizing findings across the reference checks.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with zero padding: no explanation of what SwiftData is, no restating known concepts; every line either sets constraints ("Target Swift 6.2 or later") or routes to a reference. Every token earns its place.

5 / 5

Actionability

The review process is concrete and executable — each step names an exact file ("references/predicates.md") gated on checkable conditions ("If the project targets iOS 18+"). It is not anchor 5 because no inline example or quick-start snippet is present; all substantive guidance is deferred to the reference files, leaving minor gaps if a reference is not loaded.

4 / 5

Workflow Clarity

A clear 5-step conditional review sequence with explicit gating (CloudKit usage, iOS 18+, iOS 26+) and partial-work guidance ("If doing partial work, load only the relevant reference files"). Not anchor 5 because there are no validation checkpoints or guidance on how to prioritize and report findings after checking each reference.

4 / 5

Progressive Disclosure

SKILL.md is a pure overview; all five referenced files (core-rules, predicates, cloudkit, indexing, class-inheritance) exist in references/ and are one level deep, clearly signaled both in the numbered process and the topic table, making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

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

A strong description: it names a clear niche, enumerates concrete coverage areas, and pairs them with an explicit, natural 'Use when...' trigger clause in third-person imperative style. The only gap is that capabilities are expressed as topic nouns rather than actions, and a few synonyms are missing.

DimensionReasoningScore

Specificity

Names the SwiftData domain and six concrete topic areas ("autosave, relationships, dangerous predicates, CloudKit constraints, indexing, class inheritance"), exceeding the 1-2 actions of anchor 3. It falls short of anchor 5 because topics are listed as nouns rather than framed as comprehensive concrete actions.

4 / 5

Completeness

Explicitly answers both questions: the "what" is the enumerated SwiftData pattern areas, and the "when" is a concrete trigger phrase — "Use when writing, reviewing, or debugging SwiftData code" — matching the anchor 5 example structure exactly.

5 / 5

Trigger Term Quality

Includes natural terms users would say — "SwiftData", "CloudKit", "writing, reviewing, or debugging" — giving good keyword coverage. Not anchor 5 because synonyms (e.g., "@Model", "persistent model") and file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

"SwiftData" is an unambiguous niche trigger that would not naturally fire for other skills, and the enumerated subtopics reinforce the clear niche with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
Prisma-Labs-Dev/apple-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.