From dbhub
Explores database schemas token-efficiently using DBHub tools with progressive disclosure. Use before writing SQL against an unfamiliar schema.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dbhub:exploreThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `search_objects` with progressive disclosure — always coarse to fine:
Use search_objects with progressive disclosure — always coarse to fine:
object_type: "table", detail_level: "names" (pattern defaults to %, matching all). Cheap even on large schemas.detail_level: "summary" for the tables that matter (row/column counts, comments), using a pattern like %order% rather than listing everything.detail_level: "full" only for the tables you will actually query (complete columns, types, keys) — never as a first, pattern-less call on an unfamiliar schema.Searching object_type: "column" with a pattern like %email% is the fastest way to find which tables hold a concept.
LIMIT (or TOP on SQL Server) when sampling data — start with LIMIT 10. Prefer aggregates (COUNT, GROUP BY) over pulling rows to characterize data.full detail before writing JOINs so you use real column names — don't guess and retry.npx claudepluginhub bytebase/dbhub --plugin dbhubGuides safe database workflows: schema inspection before queries, read-before-write previews for mutations, user confirmations, and post-change verification.
Generates detailed profiles of database tables including metadata, row counts, column statistics, cardinality analysis, sample data, and quality checks for completeness, uniqueness, and freshness.
Discover and explore databases, tables, columns, and data shares in MotherDuck. Use when you need to understand what data is available, preview table contents, or search the data catalog.