cache-sharding-and-replication SKILL.md skillA
cache-sharding-and-replication from robsonkades/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add robsonkades/agent-skills/cache-sharding-and-replication@git:20261016.c769bd8Pins git:20261016.c769bd8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- robsonkades/agent-skills
- Path
skills/cache-sharding-and-replication/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261016.c769bd8, committed Oct 16, 2026
- First version recorded
- Sep 6, 2026
- Size
- 14,123 bytes
- Repository stars
- 3
- License
- Apache-2.0
Topology for a cache that no longer fits one node: client-side sharded, proxy-fronted, clustered, and fully replicated, compared on failure behaviour, cost and client complexity; and why replication alone does not guarantee read-your-writes. Estimates origin load when a cache node fails from its measured request share and the surviving copies, routing and capacity — mitigated by replication, warming, coalescing and admission control. Use when choosing between client sharding, a proxy and…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Cache Sharding And Replication ## Purpose Decide how a cache is laid out across nodes, and what happens when one of those nodes goes away. This is a topology skill only: whether to cache, how long to keep an entry, and how to invalidate it are `caching-strategies`, and everything here assumes those decisions are already made. The failure this prevents is the one that never looks like a cache incident. A cache node is restarted for a routine upgrade; with N balanced nodes, consistent hashing and no replicas, about 1/N of the keyspace loses its cached copy. After fail-fast remapping, requests for those keys can reach the origin until refill, while survivors continue serving. The cache tier reports a modest dip in hit rate. The database saturates. Nobody investigating the database is looking at the cache, because the cache is up. ## Workflow Before recommending changes, reuse the request, configuration and existing measurements: cache product/version, relevant clients and runtimes, routing/retry configuration, replica placement, working-set bytes, per-node request share and origin capacity at the required SLO. Ask only about …
Read the whole file at its exact version.
How to install
mdr add robsonkades/agent-skills/cache-sharding-and-replication@sha256:f94cc265820af007The line at the top of this page pins the label git:20261016.c769bd8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_gw4chi3mqltjywm5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 6, 2026 and Oct 16, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.c769bd8 latest | 2026-10-16 | c769bd8 | 14,123 B | A | view · diff |
| git:20260927.9ecadfd | 2026-09-27 | 9ecadfd | 14,136 B | A | view · diff |
| git:20260923.832673e | 2026-09-23 | 832673e | 12,852 B | A | view · diff |
| git:20260911.37b054b | 2026-09-11 | 37b054b | 12,529 B | A | view · diff |
| git:20260906.e6ad4bd | 2026-09-06 | e6ad4bd | 11,161 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14123 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
robsonkades/agent-skills · 3 stars · license Apache-2.0 · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gw4chi3mqltjywm5 GET https://markdownregistry.com/api/v1/resolve?ref=robsonkades/agent-skills/cache-sharding-and-replication GET https://markdownregistry.com/api/v1/blob/f94cc265820af0073b66dc57f2ad6d4ef59a5e6ce82d56555f53daa549e84f67
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.