apple-cktoollisted

# Apple cktool Use the stateless `cktool` CLI distributed with Xcode to manage CloudKit schemas and test data from macOS. Keep the target explicit and default all development automation to the development environment. ## Choose the right companion | Need | Use | |---|---| | Shell commands, Xcode schemes, or a macOS runner | This skill | | TypeScript, Node.js, browser tooling, or non-macOS CI | `apple-cktool-js` | | A shell wrapper around a few stable commands | This skill | | Reusable branching logic, typed models, updates, or richer error handling | `apple-cktool-js` | Use both skills when a repository exposes a simple local `cktool` path and a portable CKTool JS CI path. Keep the same team, container, environment, schema file, and safety policy across both implementations. ## Follow the operating workflow 1. **Inspect the local tool.** Run: ```bash xcode-select -p xcrun --find cktool xcrun cktool --version xcrun cktool --help xcrun cktool help <subcommand> ``` Treat local help as authoritative for the installed Xcode. Use `man cktool` for field formats, token precedence, and examples. Do not assume flags from a different Xcode release. 2. **Resolve the complete target.** Record the team ID, container ID, environment, database type, zone, record type, and schema path that apply. Do not infer a production target from an app bundle identifier. Use `get-teams` when the team ID is unknown. 3. **Select the token class.** Use a management token fo