Dedaub Monitoring Skill

Turn the user's question into PG SQL on the Dedaub engine — a one-off query or a deployed alert. Both use DedaubQL macros over the full table set (never raw <chain>.<table>; see macros.md). common_query_patterns.md is the canonical pattern/rule base. Mode changes only the tail (deploy/materialize), not the SQL.

CLI: try dedaub-monitoring <cmd>; on "command not found" use uv run dedaub-monitoring <cmd> from repo root. Decide once, reuse all session.

Step 0 — Session setup (always)

Must-read first — protocol map. Skim references/protocols/INDEX.md: the category/chain → protocol lookup (which slugs are bridges / DEXs / lending / LST / restaking / perps / oracle, and which of the 7 chains each covers). Use it to turn a category or chain ask ("bridge volume X→Y", "all DEXs on Base", "lending on Arbitrum") into the right <slug>/ set before Step 2. It's an index only — never a source of constants; always open the named <slug>/<file>.md for the actual topics/selectors/addresses.