explorelisted

Use this whenever you need to know what is actually in a database, warehouse, or DuckDB file before you trust it: ranked inventory of what exists, column profiles, PII detection, grain and data-quality problems, verified join inference, Mermaid ER diagrams, guarded ad-hoc SQL probes, and k-means segmentation, producing a draft map without dumping the whole schema into context. Trigger it on an unmet precondition, not on any particular phrasing: if you are about to write or fix SQL against tables whose columns, types, grain, or join keys you have not verified in this session, use this FIRST. That includes dbt work: building a staging or mart model, fixing a broken model, or debugging wrong numbers, whenever the ticket names source tables without spelling out their schema. It also applies mid-task: if you are partway through and hit a table you have not inspected, stop and use this rather than guessing column names or firing off one-off SELECTs. Also use it for direct questions like "what's in my duckdb", "whic
exmergo/dex · ★ 24 · AI & Automation · score 74

Install: claude install-skill exmergo/dex

# Explore Make sense of a warehouse or a local DuckDB database the way an analytics engineer does: rank what matters, drill selectively, and persist a draft map. This is the flagship, fully read-only skill. It absorbs profiling and relationship inference as capabilities; they are not separate skills. ## How to drive it Run the engine through the wrapper. It prints one sanitized JSON envelope and nothing else; read the envelope and decide the next step. ```bash uv run --no-project --script "${CLAUDE_SKILL_DIR}/scripts/run.py" <subcommand> [flags] ``` dex runs its engine through `uv`, which is a prerequisite and is not installed by Claude Code. If the shell reports `uv: command not found`, stop and tell the user to install it (`curl -LsSf https://astral.sh/uv/install.sh | sh`, or `brew install uv`, or `pipx install uv`), then re-run. Never fall back to raw Python, `pip`, or a database CLI to do the work another way: the guardrails live in the engine, so any other path is unguarded. The first command in a fresh environment installs the engine, so it can take tens of seconds where later ones take well under a second. `--warm` pays that install up front and exits without running anything: ```bash uv run --no-project --script "${CLAUDE_SKILL_DIR}/scripts/run.py" --warm ``` Offer it once at setup. It is not something to run before an ordinary command. If the user has no warehouse to point at and wants to see what dex does, `demo` generates one: a seeded local DuckDB warehou