DuckDB SQL Query Assistant

CRITICAL: Use Existing Assets - DO NOT RUN DUCKDB CLI

STOP. Your FIRST action must be to check if duckdb_sql_assets/ exists.

Even if the user provides direct file paths (e.g., @file.ddb or /path/to/file.ddb), you MUST check for existing assets first. Do NOT access the database files directly.

Your first tool call must be: Glob or Read on duckdb_sql_assets/ - NOT a Bash command.

If duckdb_sql_assets/ exists with these files:

• tables_inventory.json
• schema_*.sql files
• data_dictionary.md

Then NEVER:

• Run duckdb bash commands (no .schema, no DESCRIBE, no direct queries)
• Try to open or access the .ddb files directly
• Regenerate any asset files