Merged
Conversation
pkosiec
commented
Mar 4, 2026
| name: databricks-apps | ||
| description: Build apps on Databricks Apps platform. Use when asked to create dashboards, data apps, analytics tools, or visualizations. Invoke BEFORE starting implementation. | ||
| compatibility: Requires databricks CLI (>= v0.288.0) | ||
| compatibility: Requires databricks CLI (>= v0.292.0) |
Member
Author
There was a problem hiding this comment.
Future version is not a mistake - the current CLI doesn't have list-databases command
pkosiec
force-pushed
the
pkosiec/lakebase-skill
branch
2 times, most recently
from
be27832 to
2290b2b
Compare
pkosiec
force-pushed
the
pkosiec/lakebase-skill
branch
from
3c2fef3 to
2d0acf4
Compare
arsenyinfo
reviewed
Mar 10, 2026
| - **Call ML model endpoint**: Use tRPC | ||
| - **Write/update data (INSERT/UPDATE/DELETE)**: Use tRPC | ||
| - **⚠️ NEVER use tRPC to run SELECT queries** — always use SQL files in `config/queries/` | ||
| - **⚠️ NEVER use tRPC to run SELECT queries against the warehouse** — always use SQL files in `config/queries/` |
Collaborator
There was a problem hiding this comment.
Do we cover it with linters?
Member
Author
There was a problem hiding this comment.
you mean preventing doing DB SQL queries not using the config/queries convention? No, I don't think so, and it would be tricky to implement, and also limiting to a user 🤔 some queries might be done via custom backend logic IMO
Add new `databricks-lakebase` skill for managing Lakebase Postgres projects, branches, endpoints, and databases. Uses a dynamic CLI discovery approach (`databricks postgres -h`) instead of hardcoding all commands, keeping the skill resilient to CLI changes during beta. Also bump minimum CLI version to v0.292.0 across all skills and register Lakebase in the parent databricks skill's product list.
- Fix list-databases inconsistency: use full resource path format in both the verification block and the What's Next step - Add concrete update-branch + delete-branch examples with full resource paths; add production branch safety warning - Rename section to "What's Next" and add "Other Workflows" subsection with brief snippets for connecting a Postgres client, managing roles, and adding a read-only endpoint - Add brainstorm doc for the What's Next redesign decision Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Label Lakebase as "OLTP" in AppKit data pattern table for LLM clarity - Add brief Lakebase description with Neon reference in SKILL.md
arsenyinfo
approved these changes
Mar 10, 2026
pkosiec
force-pushed
the
pkosiec/lakebase-skill
branch
from
6b0acb4 to
cfdf274
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
databricks-lakebaseskill for managing Lakebase Postgres projects, branches, endpoints, and databases viadatabricks postgresCLI commands.databricks postgres -h/<subcommand> -h) instead of hardcoding all commands, keeping the skill resilient to CLI changes during beta.databricks-lakebasein the parentdatabricksskill's product list.Design decisions
databricks postgres -handdatabricks postgres <subcommand> -hto discover commands. This mirrors the pattern used indatabricks-apps(which usesdatabricks apps manifestfor discovery).--help.Test plan
databricks postgres -hreturns expected subcommands with CLI >= v0.292.0python3 scripts/generate_manifest.py validateHow I tested it?
As the skill needs an upcoming Databricks CLI, and also we couldn't test Lakebase + Apps creation fully, what I did is: