pscale-neki

Use this skill for Neki-specific PlanetScale CLI operations. Prefer --format json, pass explicit --org, inspect current state before writes, and verify by reading the target back after every mutation.

For exact command surfaces, read references/commands.md. Its help fences are captured from the verified binary; do not infer flags from older Postgres or Vitess commands.

Safety model

• Creating Neki databases, branches, shards, config profiles, routers, and capacity changes can incur cost.
• Treat data-topology replacement, shard assignment, shard deletion, default-profile changes, admin/router/profile/sidecar updates, maintenance, and cancellation of pending changes as writes that require explicit user approval for the exact org, database, branch, and target.
• Use --format json for reads and writes, then poll or re-read the resource. Async profile/router/sidecar/admin changes must be checked through their changes commands until terminal.
• Never log or commit secrets, connection strings, role passwords, or SQL that contains sensitive data.
• JSON input for branch data-topology update must be a JSON object. --format json only controls output; it does not make stdin JSON.
• Sidecars and admins are managed as branch-owned components; use the CLI's show/list/update surfaces and do not assume they can be created or deleted independently.

Branch-wide change requests

Use branch changes for one inventory across Neki admin, cluster, configuration-profile, router, and sidecar requests. Per-resource changes commands remain useful when the target component is already known.