neki
Guidance for Neki, PlanetScale's distributed (sharded) Postgres. Load when working with a Neki database — connecting, data topology and shard keys, query routing and fanout, cross-shard transactions, schema changes, resharding and migration, NK013 errors — or when scaling and sharding Postgres.
Install
With your agent
Install OMGSkills skill "planetscale/database-skills:neki" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/planetscale/database-skills /tmp/database-skills && ln -s /tmp/database-skills/skills/neki ~/.claude/skills/nekiFrom README
PlanetScale Neki Docs: https://planetscale.com/docs/neki · https://neki.dev/ Platform Preview: Neki is in PlanetScale Platform Preview (a Beta Feature under the PlanetScale Terms of Service; no SLA). Single-instance, non-HA configurations are not supported during the preview. See Platform preview limitations. Overview Neki is distributed (sharded) Postgres by PlanetScale. Every shard is real Postgres; Neki places a router in front of the shards and adds per-instance sidecars and a control plane (topology service, admin, Replicator) to route, coordinate, and operate Postgres across many shards — all behind one Postgres connection string on port 5432. Applications use standard Postgres clients, drivers, and ORMs. Neki is built by the maintainers of Vitess but is a from-scratch system for Postgres, not a Vitess port.
More from this repo
mysql
Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations.
postgres
PostgreSQL best practices, query optimization, connection troubleshooting, and performance improvement.
vitess
Vitess best practices, query optimization, and connection troubleshooting for PlanetScale Vitess databases.