What problem does it solve? Redis Cluster users frequently hit CROSSSLOT errors when running multi-key operations like MGET, SDIFF, transactions, or pipelines, and overload primaries with read traffic that replicas could serve. This Skill provides guidance for designing keys with hash tags and routing reads to replicas. ## Core Features & Use Cases - Hash Tag Key Design: Force related keys onto the same cluster slot using hash tags like {user:1001} so multi-key commands, transactions, and Lua scripts work without CROSSSLOT errors. - Read Replica Routing: Enable read_from_replicas in Redis Cluster or point a second client at a replica in standalone replication to scale read-heavy workloads. - Use Case: You are building a session store on Redis Cluster and your pipeline of GET commands fails with CROSSSLOT. Apply hash tags scoped to each user entity so all of a user's keys share a slot, then route dashboard reads to replicas to free primary capacity. ## Quick Start Ask the assistant to redesign your Redis keys with hash tags so your multi-key pipeline stops throwing CROSSSLOT errors in cluster mode.