CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudkit

Implement, review, or improve CloudKit and iCloud sync in iOS/macOS apps. Use when working with CKContainer, CKRecord, CKQuery, CKSubscription, CKSyncEngine, CKShare, NSUbiquitousKeyValueStore, or iCloud Drive file coordination; when syncing SwiftData models via ModelConfiguration with cloudKitDatabase; when handling CKError codes for conflict resolution, network failures, or quota limits; or when checking iCloud account status before performing sync operations.

Quality

93%

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

The canonical home for this skill is dpearson2699/swift-ios-skills

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 high-quality reference body: executable Swift for every core CloudKit surface, hard numeric limits, expert-level gotchas, and a workflow with genuine feedback loops and a safety rule against blind full resyncs. Its main costs are mild duplication between the error table, the error-handling switch, and the checklist, and a longer-than-necessary main body relative to its well-signposted reference file.

DimensionReasoningScore

Conciseness

The body is dense and expert-facing: tables, executable Swift, hard limits ('Max 1 MB per record (excluding CKAsset data)', 'Max 1024 keys, 1 MB total'), and gotchas, with almost no teaching of concepts Claude already knows. It falls short of anchor 5 because the CKError table and the handleCloudKitError switch restate the same strategies, and the Review Checklist duplicates earlier sections; better than anchor 3 because the padding is deliberate structure, not explanation.

4 / 5

Actionability

Fully executable, copy-paste-ready Swift covering the common cases: CRUD, all three subscription types with notification handling, a complete CKSyncEngineDelegate, SwiftData ModelConfiguration, the NSUbiquitousKeyValueStore change-reason switch, account-status gating, and a concrete three-way merge. Placeholders like mergeValues/markSynced are inherently app-specific logic, which does not reduce executability of the covered cases. Matches anchor 5.

5 / 5

Workflow Clarity

The Workflow section sequences setup verification, durable local change, token/state persistence, adversarial testing ('Test offline edits, partial failure, rate limiting, token expiry, conflict, account loss, zone deletion, and relaunch'), and error classification with a rerun-the-same-scenario feedback loop and an explicit guard ('Never restart a full sync blindly after partial success'), backed by a Review Checklist. Matches anchor 5's explicit validation and feedback loops.

5 / 5

Progressive Disclosure

A real, one-level-deep bundle file (references/cloudkit-patterns.md) exists and is signposted twice with its contents enumerated (shares, assets, batch operations, Dashboard), and the TOC makes navigation easy. Falls short of anchor 5 because the ~480-line body inlines substantial detail (full conflict-merge code, the full KVO observer, error table plus switch) that could have been split into the reference; still well above anchor 3's 'buried references'.

4 / 5

Total

18

/

20

Passed

Description

95%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 states concrete capabilities in third person, provides an explicit and multi-conditioned 'Use when...' trigger clause covering the full CloudKit surface (containers, records, queries, subscriptions, sync engine, SwiftData, KVS, Drive, errors, account status). Its only weakness is that the 'what' verb list is slightly more generic than its trigger detail.

DimensionReasoningScore

Specificity

Names three concrete actions ('Implement, review, or improve CloudKit and iCloud sync in iOS/macOS apps') and enumerates concrete sub-areas (conflict resolution, network failures, quota limits, account status), but the action list is less granular than the anchor-5 pattern of enumerating each distinct operation. Above anchor 3's 1-2 actions; anchor 5 would require fuller enumeration of the specific operations.

4 / 5

Completeness

Explicitly answers what ('Implement, review, or improve CloudKit and iCloud sync in iOS/macOS apps') and when via a full 'Use when...' clause with four concrete trigger conditions. Matches the anchor-5 example structure exactly; not anchor 4 because the when-clause is specific and multi-conditioned rather than merely serviceable.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage: exact class names users would type ('CKContainer', 'CKRecord', 'CKSyncEngine', 'NSUbiquitousKeyValueStore') plus plain phrases ('iCloud sync', 'iCloud Drive file coordination', 'quota limits', 'account status') and the SwiftData 'cloudKitDatabase' configuration keyword. Matches the anchor-5 example's breadth including synonyms and API-specific terms.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Apple CloudKit/iCloud sync) with API-name triggers no other skill would claim, so overlap risk is minimal. Matches anchor 5's 'clear niche with distinct triggers'.

5 / 5

Total

19

/

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

dpearson2699/swift-ios-skills

Path

skills/cloudkit/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.