data-autocleaning

Profiles and cleans BigQuery and GCS data using Dataplex scans and SQL transformations.

1|Updated Aug 30, 2026
One-click install
npx skills add https://github.com/FeexSystems/3WM-SONIK-LABS --skill data-autocleaning-feexsystems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-autocleaning
Source: https://github.com/FeexSystems/3WM-SONIK-LABS/tree/main/.gemini/skills/data-autocleaning
Command: npx skills add https://github.com/FeexSystems/3WM-SONIK-LABS --skill data-autocleaning-feexsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Moving or ingesting data from BigQuery or Google Cloud Storage often introduces hidden data quality issues like malformed dates, garbage values, inconsistent units, and schema mismatches. This Skill automates profiling, cleansing, and verification so pipelines built on Dataform, dbt, or BigQuery start from trustworthy data. ## Core Features & Use Cases - Dataplex-Based Profiling: Runs automated data profile scans on source tables (with dynamic sampling for tables over 1M rows) to detect nulls, anomalies, and format variance before writing any transformation. - SQL Transformation Generation: Produces cleansing SQL covering schema alignment, type conversion with SAFE.PARSE functions, JSON parsing, array handling, and STRUCT field mapping. - Quality Review Loop: Re-profiles a temporary output table after transformation and compares profiles column-by-column to catch regressions like unexpected NULL increases. - Use Case: When asked to copy a GCS dataset into a BigQuery destination table, the Skill profiles the source, generates cleaning SQL matched to the destination schema, and verifies the result with a post-transformation Dataplex scan. ## Quick Start Ask the agent to clean and load a BigQuery or GCS source into a destination table, for example: profile and clean the table my-project.raw.events and load it into my-project.curated.events.

Frequently Asked Questions about data-autocleaning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean data when moving it into BigQuery?▼

Profile the source table with a Dataplex data profile scan, then generate SQL transformations that fix detected issues such as malformed dates, garbage values, and unit inconsistencies. Verify the result by profiling a temporary output table and comparing it against the source profile.

How do I profile a BigQuery table with Dataplex?▼

Run the dataplex_scanner.py script with the table ID in project.dataset.table format, a specific region like us-central1, and an output directory. The script creates a one-time Dataplex data profile scan, polls for results, and saves the profile as JSON.

Does Dataplex profiling work with GCS data sources?▼

Yes, but GCS sources require creating an external table in BigQuery first before running the Dataplex scan. After that, the same profiling and cleansing workflow applies as with native BigQuery tables.

Why does my Dataplex scan fail in a multi-region location?▼

Dataplex data profile scans do not support multi-region locations like 'us'. You must specify a specific Google Cloud region such as us-central1 when creating the scan.

How are large BigQuery tables handled during profiling?▼

Tables with more than 1 million rows are automatically sampled by the scanner script, which calculates a sampling percentage to keep scan costs down. Empty tables are skipped entirely.

When should JSON fields be flattened during data cleaning?▼

JSON fields should only be flattened or extracted when a destination schema explicitly requires it. Use SAFE.PARSE_JSON for casting and JSON_VALUE or JSON_QUERY accessors, keeping the original string if parsing returns NULL.