# Data Platform

> USE FOR: Repo-local BigQuery, Databricks, dbt, restricted BigQuery/dbt safety, and cloud auth workflows. DO NOT USE FOR: harness, diagrams, or generic code.

- Skill: `i9wa4/data-platform` (Agent Skill, multi-file: 12 files)
- Install (CLI): `npx skillmds@latest add i9wa4/data-platform`
- Raw SKILL.md: https://api.skillmd.com/api/skills/i9wa4/data-platform/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: MIT
- Author: i9wa4 (https://skillmd.com/u/i9wa4)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/i9wa4/data-platform

---


# Data Platform

Owns repo-local data-platform guardrails. These references are self-contained
for local safety and workflow rules; broad provider skill packs are
reference-only unless deliberately promoted into the active runtime bundle.

## 1. Scope

- BigQuery cost-aware query patterns, GoogleSQL guardrails, table design, and
  slot usage checks.
- Databricks Queries API, VARIANT/JSON patterns, dashboard API notes, dbt
  integration, and Jupyter kernel execution.
- Local dbt target setup and Databricks SQL dialect caveats.
- Restricted BigQuery/dbt safety workflows that keep local runs out of
  production schemas.
- Cloud authentication workflows that must run through a user-authenticated
  pane instead of the agent pane.

Out of scope:

- Agent harness runtime, Home Manager agent config, hooks, postman routing, or
  installed agent outputs; use `dotfiles`.
- GitHub issue, PR, review, or public-surface mechanics; use
  `dev-platform-workflow`.
- Diagram authoring or export workflows; use `diagramming`.
- Generic Bash, Python, Nix, Markdown, or implementation-loop work; use
  `programming`.

## 2. Workflow

1. Inspect the relevant files, current repo conventions, and `git status`.
2. Select the focused reference below before changing files or running data
   commands.
3. For any command that can write cloud or warehouse state, verify the target,
   schema, and approval requirements before execution.
4. Keep repo-local safety constraints in focused references and keep the owner
   skill as the primary trigger surface.
5. Run the fastest focused check during iteration, then the nearest repo
   validation surface before reporting success.

## 3. References

- [BigQuery](references/bigquery.md)
- [Databricks](references/databricks.md)
- [dbt](references/dbt.md)
- [Restricted BigQuery dbt Safety](references/restricted-bigquery-dbt.md)
- [Cloud Auth](references/cloud-auth.md)