bigquery-and-dataform-platform-engineering — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited bigquery-and-dataform-platform-engineering (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when BigQuery is the center of gravity for analytics engineering and data delivery on GCP. It helps agents decide what should run in BigQuery, what belongs in Dataform, and when the workflow should move to Dataflow, Dataproc, or external orchestration.
BigQuery physical modelsDataform, dbt, Dataflow, or Dataproc responsibilitiesGCPBigQueryDo not treat BigQuery as a universal default for every preprocessing and orchestration need.
Clarify:
BigQuery physical layout intentionally.Cover:
Consider:
Dataform for warehouse-native SQL transformation workflowsdbt when the team already standardizes thereDataflow or Dataproc when preprocessing or runtime requirements exceed warehouse-native fitInclude:
Require:
| Rationalization | Reality |
|---|---|
| "Everything on GCP should run in BigQuery." | Some preprocessing, streaming, or protocol-heavy work belongs in Dataflow, Dataproc, or upstream services. |
| "Dataform is just a SQL wrapper." | It changes how transformation workflows, dependencies, testing, and deployment are managed. |
| "Partitioning and clustering can be tuned later." | Poor physical design often becomes a long-term cost and performance tax. |
Dataform, Dataflow, and Dataproc are unclear~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.