iCloud

Setup

On first use, read setup.md for secure integration guidelines.

When to Use

Use this skill when the user wants agents to interact with their own iCloud account: list devices, retrieve Find My status, inspect iCloud Drive, or pull photo metadata/files. Use it for operational automation with strict safety gates, not for bypassing Apple account security.

Architecture

Memory lives in ~/icloud/. See memory-template.md for structure and status fields.

~/icloud/
|-- memory.md               # Status, integration mode, and current account scope
|-- operations-log.md       # Executed commands, result checks, and rollback notes
|-- device-map.md           # Known device aliases and stable IDs
|-- drive-map.md            # iCloud Drive folder map and verified paths
`-- safety-events.md        # Confirmed risky actions and explicit approvals

Quick Reference

Load only the file needed for the current task.

Core Rules

1. Authenticate Locally, Never Through Chat

• Never ask the user to paste Apple password, 2FA code, session token, or app password in conversation.
• Use interactive local auth with terminal prompts or secure local input prompts only.

2. Start Read-Only, Then Escalate

• Run read-only discovery first: account reachability, device list, folder listing, metadata checks.
• Do not run write operations until read checks pass and scope is explicit.

3. Require Explicit Confirmation for Risky Actions

• Treat lost mode, message push, file rename/delete, and bulk upload as risky.
• Before running risky actions, summarize target, effect, and rollback option, then request explicit confirmation.

4. Use Deterministic Verification After Every Action

• After each operation, verify expected state with a second read call.
• Never report success from command exit code alone.

5. Keep Operations Narrow and Idempotent

• Operate on one device ID or one file path per step when possible.
• Prefer repeat-safe commands and avoid broad wildcard operations.

6. Handle 2FA and Session Expiry as Normal State

• If Apple invalidates the session, pause destructive operations and re-auth first.
• Continue only after session trust is restored and read checks succeed again.

7. Persist Only Minimal Operational Context

• Store only what improves reliability (IDs, verified paths, successful patterns).
• Never persist secrets or raw credential material in local memory files.

Common Traps