← ClaudeAtlas

cloud-cost-comparelisted

Build an evidence-grade cloud cost comparison workbook across AWS, Azure, GCP (and on-prem/other vendors) from a spec, a use case, or an architecture description. Prices every option from first-party SKU feeds, then cross-verifies each total against the vendor's own public pricing calculator driven through Claude in Chrome, and gates the result on a variance check. Use when asked to compare cloud costs, price a workload across providers, validate a published price comparison, or produce a cost dashboard.
thecloudranger/cloud-cost-compare · ★ 0 · DevOps & Infrastructure · score 62
Install: claude install-skill thecloudranger/cloud-cost-compare
# Cloud Cost Compare Produce a multi-tab Excel workbook that prices one workload across several clouds and proves every number twice: once from the vendor's machine-readable SKU feed, once from the vendor's own public pricing calculator. A figure that has not survived both is not reportable. ## The one rule that matters most **Never state what a provider does or does not offer from memory. Check the vendor's own catalogue first, every time, for every provider.** Model training data goes stale in weeks. GPU SKUs, regions and machine families change constantly. Asserting "provider X has no equivalent" without a lookup produces confidently wrong work, wastes the user's time, and destroys trust in every other number in the workbook. Before you claim availability in any direction — present or absent — you must have run a lookup **in this session** against the sources in `references/pricing-sources.md`. If you have not looked it up, you do not know. Concretely, before writing a single price: - List candidate SKUs per provider from the live catalogue, not from recall. - Confirm the region actually carries the SKU (catalogue presence != region presence). - Confirm the shape (vCPU / RAM / accelerator count / VRAM) from the vendor's own spec page, not from the pricing feed, which usually omits it. ## Workflow Work through these in order. Do not skip to pricing. ### 1. Establish the target workload The user will give you one of three things. Convert whichever you get into a