yugabytedb-sizing SKILL.md skillA
yugabytedb-sizing from srinivasa-vasu/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add srinivasa-vasu/agent-skills/yugabytedb-sizing@git:20261007.886b94cPins git:20261007.886b94c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- srinivasa-vasu/agent-skills
- Path
yugabytedb-sizing/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261007.886b94c, committed Oct 7, 2026
- First version recorded
- May 15, 2026
- Size
- 13,004 bytes
- Repository stars
- 3
- License
- none declared
Calculate and recommend optimal YugabyteDB cluster sizing based on workload inputs. Use this skill whenever the user asks about YugabyteDB cluster sizing, capacity planning, node count, vCPU requirements, storage sizing, memory recommendations, or wants to know how many nodes they need for a given workload. Trigger when user mentions "size my cluster", "how many nodes", "YugabyteDB capacity", "YugabyteDB hardware requirements", QPS with YugabyteDB, or asks about CPU/storage/memory for a…
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
# YugabyteDB Cluster Sizing Calculator Size a YugabyteDB cluster from workload inputs: node count, vCPU, memory, storage, IOPS, disk throughput, network and failure resilience, targeting ≤65% CPU. **Always run the bundled script** (`scripts/sizing_calc.py`) — never compute by hand. Rules: - RF must be 1, 3, 5 or 7 (the script rejects others). Never recommend RF=1 for production. - **Always state that the sizing is indicative** and that the user should test with their actual workload to fine-tune production sizing. - CPU comes from measured CPU cost per operation (transactional, point-select and YCQL key-value benchmarks), not from latency. Details: [references/cpu-model.md](references/cpu-model.md). ## Workflow 1. **Pick the API.** `--api ysql` (default) or `--api ycql`. Cassandra, CQL, port 9042, partition keys or TTL → YCQL; PostgreSQL, SQL, joins or port 5433 → YSQL. Ask if unclear. 2. **Gather inputs** (table below). Ask for the required ones; use defaults for the rest. 3. **Choose the CPU basis, best first:** 1. *Calibration* — if the user has a running cluster or PoC with a similar mix, ask for its QPS …
Read the whole file at its exact version.
How to install
mdr add srinivasa-vasu/agent-skills/yugabytedb-sizing@sha256:8bb085b36f6c04e9The line at the top of this page pins the label git:20261007.886b94c, 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_jq57hpnwfsxfgtlp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 15, 2026 and Oct 7, 2026, about one every 36 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.886b94c latest | 2026-10-07 | 886b94c | 13,004 B | A | view · diff |
| git:20261007.4b60dbc | 2026-10-07 | 4b60dbc | 13,273 B | A | view · diff |
| git:20261002.5280fb0 | 2026-10-02 | 5280fb0 | 12,281 B | A | view · diff |
| git:20260811.118a369 | 2026-08-11 | 118a369 | 24,968 B | A | view · diff |
| git:20260515.41fccec | 2026-05-15 | 41fccec | 21,314 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 (13004 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
srinivasa-vasu/agent-skills · 3 stars · license none declared · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jq57hpnwfsxfgtlp GET https://markdownregistry.com/api/v1/resolve?ref=srinivasa-vasu/agent-skills/yugabytedb-sizing GET https://markdownregistry.com/api/v1/blob/8bb085b36f6c04e9b9b24657e17be5204d38168fd2bf08bed4a73135ddd62a83
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.