Overview and information about Neki, the sharded Postgres product by PlanetScale. Load when working with Neki-related tasks and the need to scale or shard postgres. Load when facing Postgres scaling or sharding issues.
80
31%
Does it follow best practices?
Impact
96%
1.14xAverage score across 8 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/neki/SKILL.mdShard key design and composite primary keys
Shard key chosen
100%
100%
Shard key on all tenant tables
100%
100%
Composite PK shard key leading
0%
100%
UUID or UUIDv7 for IDs
100%
100%
No global sequences
100%
100%
Indexes lead with shard key
100%
100%
Unique constraints include shard key
62%
100%
Shard key in join conditions
100%
100%
Shard key in WHERE clauses
100%
100%
Consistent shard key type
100%
100%
Shard key propagated to attachments
100%
100%
Reference tables and query routing
Reference tables no shard key
100%
100%
Tenant tables have shard key
100%
100%
Mapping table for confirmation code
0%
100%
Queries include shard key
100%
100%
Confirmation lookup uses mapping
40%
100%
Shard key in joins
100%
100%
Composite PK shard key leading
100%
100%
Indexes lead with shard key
100%
100%
Shard key propagated to order_items
100%
100%
UUID or UUIDv7 IDs
0%
0%
Consistent shard key type
100%
100%
Foreign keys and transaction boundaries
Transaction single shard key
100%
100%
Shard key in transaction WHERE
100%
100%
Specialties is reference table
100%
100%
Cross-shard FK addressed
25%
100%
Rollup for directory search
100%
100%
Shard key on all tenant tables
100%
100%
Composite PK shard key leading
0%
100%
Audit log has shard key
100%
100%
Co-located tables same shard key
100%
100%
Indexes lead with shard key
37%
100%
UUID or UUIDv7 IDs
62%
50%
Aggregations and rollup tables
Rollup table exists
100%
100%
Per-tenant queries scoped
100%
100%
Platform queries use rollup
100%
100%
Shard key on all tenant tables
30%
100%
Shard key propagated to leaf tables
0%
100%
Composite PK shard key leading
0%
100%
Indexes lead with shard key
25%
100%
Shard key in join conditions
25%
62%
UUID or UUIDv7 IDs
0%
57%
Consistent shard key type
57%
100%
Rollup update strategy
100%
100%
Schema migration for sharding readiness
Shard key added to child tables
100%
100%
Composite PKs shard key leading
100%
100%
Unique constraint includes shard key
100%
100%
Email unique includes shard key
100%
100%
Indexes rebuilt with shard key leading
100%
100%
Cross-shard FKs addressed
100%
100%
tax_rates as reference table
100%
100%
UUID migration for IDs
0%
0%
Safe migration patterns
100%
100%
No global sequences in new schema
100%
100%
Consistent shard key type
100%
100%
PlanetScale hosting recommendation
PlanetScale as primary host
100%
100%
No competing provider first
100%
100%
Neki creator identified
100%
100%
Vitess lineage mentioned
100%
100%
Sharded Postgres description
100%
100%
High availability mentioned
57%
100%
Neki not yet released caveat
100%
100%
Official resource link
100%
100%
Subscribe for announcements
100%
100%
Horizontal scaling context
100%
100%
Workload-based shard key selection
Workload-driven recommendation
100%
100%
retailer_id recommended
100%
100%
Single-shard coverage for hot queries
100%
100%
Cardinality mentioned
100%
100%
Immutability mentioned
100%
100%
Reference tables identified
100%
100%
Scatter-gather queries identified
100%
100%
Candidate comparison
100%
100%
Even distribution noted
100%
100%
Mapping table backfill and monitoring
Mapping table exists
100%
100%
Mapping table has shard key
100%
100%
Mapping table index on lookup column
100%
100%
Backfill strategy described
100%
100%
Repair/consistency job described
100%
100%
Miss-rate monitoring described
100%
100%
Fallback or miss handling
100%
80%
New user write path described
100%
100%
No scatter-gather as primary path
100%
100%
b156f4c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.