Fetches axiom-cloud-sync from charleswiltgen/axiom and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/axiom-cloud-sync
Restart Cursor to activate axiom-cloud-sync. Access via /axiom-cloud-sync in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
// ✅ CORRECT: Offline-first architectureclassOfflineFirstSync{privatelet localStore:LocalDatabase// GRDB, SwiftData, Core Dataprivatelet syncEngine:CKSyncEngine// Write to LOCAL first, sync to cloud in backgroundfuncsave(_ item:Item)asyncthrows{// 1. Save locally (instant)tryawait localStore.save(item)// 2. Queue for sync (non-blocking) syncEngine.state.add(pendingRecordZoneChanges:[.saveRecord(item.recordID)])}// Read from LOCAL (instant)funcfetch()asyncthrows->[Item]{returntryawait localStore.fetchAll()}}// ❌ WRONG: Cloud-first (blocks on network)funcsave(_ item:Item)asyncthrows{// Fails when offline, slow on bad networktryawait cloudKit.save(item)tryawait localStore.save(item)}
Conflict Resolution Strategies
Conflicts occur when two devices edit the same data before syncing.
Strategy 1: Last-Writer-Wins (Simplest)
// Server always has latest, client accepts itfuncresolveConflict(local:CKRecord, server:CKRecord)->CKRecord{return server // Accept server version}
Use when: Data is non-critical, user won't notice overwrites
Strategy 2: Merge (Most Common)
// Combine changes from both versionsfuncresolveConflict(local:CKRecord, server:CKRecord)->CKRecord{let merged = server.copy()as!CKRecord// For each field, apply custom merge logic merged["notes"]=mergeText( local["notes"]as?String, server["notes"]as?String) merged["tags"]=mergeSets( local["tags"]as?[String]??[], server["tags"]as?[String]??[])return merged
}
Use when: Both versions contain valuable changes
Strategy 3: User Choice
// Present conflict to userfuncresolveConflict(local:CKRecord, server:CKRecord)async->CKRecord{let choice =awaitpresentConflictUI(local: local, server: server)return choice ==.keepLocal ? local : server
}
Use when: Data is critical, user must decide
Common Patterns
Pattern 1: SwiftData + CloudKit (Recommended for New Apps)
importSwiftData// Automatic CloudKit sync with zero configuration@ModelclassNote{var title:Stringvar content:Stringvar createdAt:Dateinit(title:String, content:String){self.title = title
self.content = content
self.createdAt =Date()}}// Container automatically syncs if CloudKit entitlement presentlet container =tryModelContainer(for:Note.self)
Limitations:
Private database only (no public/shared)
Automatic sync (less control over timing)
No custom conflict resolution
Pattern 2: CKSyncEngine (Custom Persistence)
// For GRDB, SQLite, or custom databasesclassMySyncManager:CKSyncEngineDelegate{privatelet engine:CKSyncEngineprivatelet database:GRDBDatabasefunchandleEvent(_ event:CKSyncEngine.Event)async{switch event {case.stateUpdate(let update):// Persist sync stateawaitsaveSyncState(update.stateSerialization)case.fetchedDatabaseChanges(let changes):// Apply changes to local DBfor zone in changes.modifications {awaithandleZoneChanges(zone)}case.sentRecordZoneChanges(let sent):// Mark records as syncedfor saved in sent.savedRecords {awaitmarkSynced(saved.recordID)}}}}
See axiom-cloudkit-ref for complete CKSyncEngine setup.
Pattern 3: iCloud Drive Documents
importUIKitclassMyDocument
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
