What problem does it solve? Writing correct GoogleSQL for BigQuery's Augmented Analytics TVFs (AI.CAUSAL_EFFECT, ML.CORRELATION, ML.DETECT_CHANGE_POINTS, ML.TREND, ML.SEASONALITY) requires exact named-argument syntax, correct namespace usage, and knowledge of output schemas, while provisioning Conversational Analytics Data Agents demands strict JSON payload and attribution rules that are easy to get wrong. ## Core Features & Use Cases - TVF Reference & Validation: Complete syntax, input requirements, and output schemas for all five Augmented Analytics TVFs, plus AST validation via sqlglot with required named-argument (=>) checks. - Dual-Mode Execution: Scripts probe GCP OAuth scopes and either execute live BigQuery queries with mandatory datacloud:jetski labels or fall back to offline dry-run validation under read-only scopes. - Conversational Analytics Agent Provisioning: Verified JSON payload patterns for Data Agents, including tableReferences grounding, dual published/staging contexts, and un-fenced golden queries covering each TVF. - Use Case: Measure the causal impact of an earnings announcement on a stock's close price by generating an AI.CAUSAL_EFFECT query, validating it offline, and executing it against BigQuery with proper attribution labels. ## Quick Start Ask the assistant to write and validate an AI.CAUSAL_EFFECT query measuring the impact of an event on your BigQuery time-series table, then run scripts/run_augmented_sql.py with your project ID to validate or execute it.