Click any tag below to further narrow down your results
Links
SLayer is an open-source Python semantic layer that sits on top of a data warehouse so AI agents and people can query metrics without writing SQL by hand. You define a column like revenue once, then query it with expressions such as avg(revenue) or time_shift(sum(revenue), -1, 'year').
- Unlike traditional BI semantic layers, which need every metric and aggregation predefined, SLayer lets agents combine metrics, apply transforms like time shifts, and change aggregations on the fly.
- It handles read-only database connectivity, SQL generation, and row-level security, so the LLM doesn't have to write raw SQL.
- It exposes the same definitions over MCP, REST, CLI, Python, Flight SQL, and a Postgres-style SQL API, and imports configs from dbt, Cube, and Ossie.
- Install is via uv, and it can be added to Claude Code as an MCP server with a demo Jaffle Shop database for a quick start. It sends aggregated usage stats once a day unless you opt out.
Jevflake is a dbt package that lets you query Snowflake data using TypeSafe AI's Jev decision model, which returns typed answers (yes/no probabilities, category picks, or scored ratings) that you can filter and join like regular SQL. It handles API setup, creates SQL functions, and manages answer caching so you don't re-query the same data.
- Jev returns structured answers (probabilities for yes/no, picks with confidence for categories, weighted scores for ratings) rather than text, making answers usable directly in SQL operations
- The package stores answers in an incremental table keyed by row ID and question, so rows are only sent to the API again if their content changes or you modify the questions
- Setup splits between admin (network/integration) and dbt role (function creation), requiring Snowflake external access enabled and a TypeSafe API key
dbt-doctor scans dbt projects for maintainability issues like missing documentation, weak test coverage, schema drift risks, and DAG problems. It generates a health score (0–100) and can run locally, in pre-commit hooks, or as a GitHub Actions quality gate.
- Detects 122 rules across 9 categories including missing docs/tests, stale models, naming convention violations, and governance gaps
- Integrates into CI/CD with GitHub Actions, outputs sticky PR comments, and can fail builds based on error/warning thresholds
- Configurable via presets (default/strict/enterprise), inline suppressions, and .dbt-doctor config file; respects .gitignore and .sqlfluff rules
Claire Gouze lays out a practical process to build and test a context layer your data agents can trust. She shows how to start small with dbt docs and markdown files, write evals, clean up data models, and iterate until you reach around 90% reliability.
- Adding query logs and profiling alone got the agent stuck around 40% accuracy; reworking the data model and documentation pushed it to 90%.
- Treat context like code: store it in files/markdown, version in Git, add CI/CD evals, and iterate on failure cases rather than plugging agents directly into raw databases.
- Start small—10 to 20 core tables with existing dbt docs—rather than trying to cover the whole warehouse at once.
- Evals should come from real BI query history or autogenerated question sets, reviewed by teams and tracked over time to build trust in the agent.
SQLBuild plugs into an existing dbt project to fingerprint models, skip unchanged work, and clone production tables in development instead of rebuilding them. It stores all state in append-only warehouse tables, adds ingestion and Python nodes, and offers built-in testing, audits, and incremental processing with no external services.
- Wraps your existing dbt project (no file edits, no new models) by fingerprinting models/seeds/functions/Python nodes and skipping anything unchanged, even cloning unchanged prod tables instead of rebuilding them.
- All state stored as append-only tables in the warehouse itself—no external service, manifest files, or state machine required.
- Runs audits before data lands: full builds stage until checks pass, incremental models validate each microbatch before merging.
- One pip install gets you a runnable sample project, and it already supports DuckDB, MotherDuck, Snowflake, BigQuery, Databricks, Postgres, and SQL Server.