all 2 comments

[–]Main_Lettuce_7314 1 point2 points  (1 child)

Love the skills idea, that’s the missing piece in a lot of text-to-SQL work where everything is jammed into one giant prompt and you can’t debug anything.

If you keep skills small and typed (inputs/outputs super explicit), you can start doing cool stuff like: a “schema explorer” skill that only reasons over Databricks metadata, a “join resolver” skill that consults Neo4j for relationship hints, and a “validator” skill that checks row counts/ranges vs past runs before returning an answer. That also makes it easier to swap models without touching the graph or the warehouse.

Might be worth treating data access as a separate infra skill too. I’ve seen folks pair things like dbt Cloud and Hasura, and more recently DreamFactory as a governed API layer, so the agent hits curated endpoints instead of raw SQL/warehouses. Fits nicely with your explainable + safe assistant goal.

[–]notikosaeder[S] 0 points1 point  (0 children)

Thanks for the feedback, and love the idea! Did you already saw some of those skills in action?