# Cloud Data Infra

> Cloud Data Infrastructure & Cost (Router)

- Skill: `methasit-pun/cloud-data-infra` (Agent Skill)
- Install (CLI): `npx skillmds@latest add methasit-pun/cloud-data-infra`
- Raw SKILL.md: https://api.skillmd.com/api/skills/methasit-pun/cloud-data-infra/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: Methasit-Pun (https://skillmd.com/u/methasit-pun)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/methasit-pun/cloud-data-infra

---


# Cloud Data Infrastructure & Cost (Router)

This is a **router skill**. It groups the two skills covering cloud data infrastructure and its cost. Diagnose which sub-area(s) the task touches, then **invoke the matching sub-skill(s) with the Skill tool**.

## How to route

| If the task is about… | Invoke sub-skill |
|---|---|
| Provisioning and architecture: S3/GCS/ADLS partitioning, BigQuery slots, Redshift Spectrum, Snowflake warehouses, IAM/cross-account access, managed-service selection, cloud performance tuning | `cloud-infra-data` |
| The bill: query cost analysis, bytes scanned, partition pruning, slot reservation vs. on-demand, storage tiering, Snowflake credits, cost alerts and budgets | `cost-optimization-data` |

## Routing rules

- **These two almost always travel together.** A "slow BigQuery query" is both a performance (`cloud-infra-data`) and a cost (`cost-optimization-data`) problem — invoke both.
- **"Our bill jumped" or a named expensive query** → lead with `cost-optimization-data` (it starts by finding where the money goes), then `cloud-infra-data` for the structural fix.
- **Choosing/standing up a warehouse or storage layout** → lead with `cloud-infra-data`, then `cost-optimization-data` to price the choice.
- Invoke via the Skill tool by name, e.g. `Skill(skill="cost-optimization-data")`. Combine outputs; don't paraphrase from memory.

## Related groups

- Pipelines deployed onto this infra → [[data-pipelines]]
- Query patterns that drive cost → [[data-modeling]]