Yes so it is possible to generate questions automatically, just so I understand the CSV use case better. Is it because you don't trust the application enough to connect a database to the application?
In tons of enterprise and just general office settings, you'll be given a CSV file, rather than a database dump. Heck, even scientific lab equipment will output CSV for you. It's basically the lowest common denominator for all kinds of tabular data.
So anything that makes using CSV files easier with your product is likely going to be a welcome change for a lot of people.
Realistically, your database engine can probably ingest the CSV file in a simple import statement, so you're likely 98% done already with this. :)
I do work for an mid-sized company, and they are drowning in CSV files. They don't have a database, really. They have lots of different enterprise software systems that they use, each of which exports differently formatted CSV files that need to be combined in various ways to produce either different CSV outputs (for importing into different systems or to be sent to some other organisation) or some other output (like a list of PDFs that are sent to some other organisation or individual) or reports for business intelligence purposes.
I use BigQuery as the database, which is a competitor to SnowFlake which you already support. I also already use ChatGPT-4 a lot nowadays to create and edit the SQL queries (although they can sometimes be so large that ChatGPT can't cope with them so I sometimes use cut-down/contrived examples to write chunks of a query then construct a much bigger query from those smaller examples).
So you could replace my job if you could allow people to name their data warehouse provider of choice, drag and drop umpteen CSV files into it, write some instructions like "Give me a CSV file with all the BLAH matching BLAH" or "Create PDF documents with BLAH information in them" and get the outputs they need on the other end.
Not the original commenter, but I have often been asked by non-technical colleagues to answer questions about a spreadsheet they've sourced from someone/somewhere else. "So-and-so shared this spreadsheet with me. Can you please take a look at let me know if ...". Sometimes this is delegation, but frequently comes down to a lack of skill.
So anything that makes using CSV files easier with your product is likely going to be a welcome change for a lot of people.
Realistically, your database engine can probably ingest the CSV file in a simple import statement, so you're likely 98% done already with this. :)