Skip to content
Skills Library
Data & analytics · Tool integration

data-platform

/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.

Author
i9wa4 ↗
Repository
dotfiles ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
12
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/databricks-libs.py

What it does and when to use it

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

Original author description

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

How it works

  1. 1. Scope
  2. 2. Workflow
  3. 3. References
Original SKILL.md headings · 49 lines, 249 words
SKILL.md preview
---
name: data-platform
license: MIT
metadata:
  version: "1.0.0"
description: |
  USE FOR: Repo-local BigQuery, Databricks, dbt, restricted BigQuery/dbt safety, and cloud auth workflows. DO NOT USE FOR: harness, diagrams, or generic code.
---

# 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)
Files in this package (12)
  • SKILL.md 2 KB
  • evals/eval.yaml 1 KB
  • evals/tasks/negative-trigger-1.yaml 1 KB
  • evals/tasks/positive-trigger-1.yaml 1 KB
  • evals/tasks/positive-trigger-2.yaml 1 KB
  • examples/staging-model.sql 1 KB
  • references/bigquery.md 2 KB
  • references/cloud-auth.md 1 KB
  • references/databricks.md 4 KB
  • references/dbt.md 2 KB
  • references/restricted-bigquery-dbt.md 1 KB
  • scripts/databricks-libs.py 6 KB

Versions

The database has no other skills named data-platform.

Database snapshot: 13.11.2026 · package version f4f8a77e5c03 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95dbt-bigquery
    Expert guidance for creating, modifying, and optimizing dbt pipelines for BigQuery. Use this skill whenever user asks for generating or modifying a dbt model or project. Activate this skill when the user - Creates, modifies, or troubleshoots **dbt models or pipelines** - Needs…
  • 100dbt-bigquery
    Expert guidance for creating, modifying, and optimizing dbt pipelines for BigQuery. Use this skill whenever user asks for generating or modifying a dbt model or project. Activate this skill when the user - Creates, modifies, or troubleshoots **dbt models or pipelines** - Needs…
  • 90dbt-bigquery
    Use when creating, changing, testing or running dbt models on BigQuery: layering, incremental strategies, ds snapshots, SCD2, partitioning and clustering, sources and freshness, contracts and safe runs against dev targets.
  • 100dbt-migration-bigquery
    Convert Google BigQuery DDL to dbt models compatible with Snowflake. This skill should be used when converting views, tables, or stored procedures from BigQuery to dbt code, generating schema.yml files with tests and documentation, or migrating BigQuery SQL to follow dbt best practices.
  • 100dbt-migration-bigquery
    Convert Google BigQuery DDL to dbt models compatible with Snowflake. This skill should be used when converting views, tables, or stored procedures from BigQuery to dbt code, generating schema.yml files with tests and documentation, or migrating BigQuery SQL to follow dbt best practices.
  • 100migrating-dbt-project-across-platforms
    Use when migrating a dbt project from one data platform or data warehouse to another (e.g., Snowflake to Databricks, Databricks to Snowflake) using dbt Fusion's real-time compilation to identify and fix SQL dialect differences.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.