Check which data the report may show
Read the blacklist so protected tables and fields cannot land in the result. If the data is off limits, go back to its owner; do not work around policy by rewriting the query.
dbcli blacklist listAnalytical delivery
Operations asks, “Which plan lost the most customers?” Don’t answer with a screenshot.
That question will start the next meeting. The result needs to show where data came from, what was queried, and which limits apply; a polished agent response is not enough when nobody can check it.
The question: Operations wants to compare this month’s churn by plan. The analyst checks the permitted data and live
subscriptions fields, then reuses the reviewed monthly-churn query to deliver a UI people can discuss.From question to a useful delivery
Inspect the schema before naming “plan”
Look at the actual table before asking an agent for a bounded query. This prevents a plausible dashboard built from a similarly named but wrong field.
dbcli schema subscriptions --format jsonUse the team query for an interactive delivery
Search for a saved snippet first; only then run the confirmed query with the interactive UI. Existing permissions, blacklists, and row limits still apply.
dbcli queries search churn
dbcli q @monthly-churn --ui