Agent skill

cloudkit-sync

Generate CloudKit sync infrastructure using CKSyncEngine with conflict resolution, sharing, and account monitoring. Use when adding iCloud sync to an iOS/macOS app.

rshankrasgithub.com/rshankrasGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add rshankras/claude-code-apple-skills --skill cloudkit-sync --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 11 KB
Bundled scripts: none
Allowed tools: ReadWriteEditGlobGrepBashAskUserQuestion
Path: skills/generators/cloudkit-sync/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 589
Language: Swift

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# CloudKit Sync Generator Generate production-ready CloudKit sync infrastructure using `CKSyncEngine` (iOS 17+ / macOS 14+), the modern replacement for manual `CKOperation` chains. ## When This Skill Activates Use this skill when the user: - Asks to "add iCloud sync" or "sync data across devices" - Mentions "CloudKit", "CKSyncEngine", or "cloud sync" - Wants to "share data between users" via iCloud - Asks about "conflict resolution" for synced data - Mentions "CKRecord", "CKShare", or "CKRecordZone" ## Pre-Generation Checks ### 1. Project Context Detection Before generating, ALWAYS check: ```bash # Check deployment target (CKSyncEngine requires iOS 17+ / macOS 14+) grep -r "platform" Package.swift 2>/dev/null || true grep -r "IPHONEOS_DEPLOYMENT_TARGET\|MACOSX_DEPLOYMENT_TARGET" --include="*.pbxproj" | head -3 # Find existing CloudKit implementations rg -l "CKSyncEngine\|CKContainer\|CKRecord\|CKOperation" --type swift | head -10 # Check for existing entitlements find . -name "*.entitlements" -exec cat {} \; 2>/dev/null | grep -i "icloud" # Check existing persistence layer rg -l "@Model\|NSManagedObject\|PersistentModel" --type swift | head -5 # Check for existing sync infrastructu

What's inside
Steps it walks through
  1. When This Skill Activates
  2. Pre-Generation Checks
  3. 1. Project Context Detection
  4. 2. Compatibility Verification
  5. 3. Conflict Detection
  6. Configuration Questions
  7. Generation Process
  8. Step 1: Read Templates
  9. Step 2: Create Core Files
  10. Step 3: Determine File Location
  11. Step 4: Customize for Project
  12. Step 5: Entitlements Setup
  13. Entitlements and Capabilities Setup
  14. Required Xcode Capabilities
Ships with 1 file
  • templates.md
Commands it runs
Check deployment target (CKSyncEngine requires iOS 17+ / macOS 14+)
grep -r "platform" Package.swift 2>/dev/null || true
grep -r "IPHONEOS_DEPLOYMENT_TARGET\|MACOSX_DEPLOYMENT_TARGET" --include="*.pbxproj" | head -3
Find existing CloudKit implementations
rg -l "CKSyncEngine\|CKContainer\|CKRecord\|CKOperation" --type swift | head -10
Check for existing entitlements
find . -name "*.entitlements" -exec cat {} \; 2>/dev/null | grep -i "icloud"
Check existing persistence layer
rg -l "@Model\|NSManagedObject\|PersistentModel" --type swift | head -5
Check for existing sync infrastructure
More from claude-code-apple-skills
All skills →
About this skill
What does the cloudkit-sync skill do?

Generate CloudKit sync infrastructure using CKSyncEngine with conflict resolution, sharing, and account monitoring. Use when adding iCloud sync to an iOS/macOS app.

How do I install it?

Run `npx skills add rshankras/claude-code-apple-skills --skill cloudkit-sync --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rshankras/claude-code-apple-skills, a repository with 589 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going