data-autocleaning

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill data-autocleaning-smileafterburn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data-autocleaning
Source: https://github.com/SmileAfterBurn/pani-dumka-ai/tree/main/.gemini/skills/data-autocleaning
Command: npx skills add https://github.com/SmileAfterBurn/pani-dumka-ai --skill data-autocleaning-smileafterburn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Moving or ingesting data from BigQuery or Google Cloud Storage without profiling leads to hidden data quality issues like garbage values, inconsistent formats, and unexpected NULLs. This Skill enforces a Dataplex-driven profiling and verification workflow so every transformation is evidence-based and validated before completion. ## Core Features & Use Cases - Dataplex-Based Profiling: Automatically scans source tables (with dynamic sampling for tables over 1M rows) to detect null rates, distinct values, and anomalies before writing any transformation. - SQL Transformation Generation: Produces cleaning 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 cleansing 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 data from a BigQuery table or GCS path into a destination table, and it will profile, transform, and verify the data automatically.

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 from GCS to BigQuery?▼

Create an external table over the GCS source, run a Dataplex data profile scan to detect anomalies, then generate SQL transformations for schema alignment, type conversion, and garbage value handling. Verify the result by profiling a temporary output table and comparing profiles.

How to profile BigQuery tables with Dataplex before transformation?▼

Use the dataplex_scanner.py script with table IDs in project.dataset.table format, a specific region like us-central1, and an output directory. It handles concurrent scans, dynamic sampling for tables over 1M rows, and saves results as JSON.

Does Dataplex scanning work in multi-region locations like 'us'?▼

No, Dataplex data profile scans require a specific Google Cloud region such as us-central1. Multi-region locations like 'us' are not supported, so always pass a regional location to the scan command.

Can I use ad-hoc BigQuery queries instead of Dataplex for profiling?▼

No, the workflow mandates Dataplex profiling for both pre-transformation and post-transformation verification. Ad-hoc SQL profiling is only permitted as a fallback when the user explicitly denies scan execution approval.

How are JSON and array columns handled during BigQuery data cleaning?▼

JSON strings are parsed with SAFE.PARSE_JSON and extracted with JSON_VALUE or JSON_QUERY only when the destination schema requires it. Arrays are filtered to remove NULL elements after SAFE_CAST, deduplicated with DISTINCT, and unnested only when the target schema demands it.