onequery-openclaw

Use this skill when the user wants company or customer data that should be read through OneQuery-managed access, or when you need to resolve org and source context before a bounded query. Use OpenClaw's `exec` tool to run the `onequery` CLI directly. Use these commands in this order: 1. `onequery auth whoami` 2. `onequery org current` or `onequery org list --page-size 25` 3. `onequery source list --org <org> --page-size 25` 4. `onequery source show <source> --org <org>` 5. `onequery query validate --org <org> --source <source> --sql '<sql>' --max-rows 100 --max-bytes 1048576 --cell-max-chars 2000 --timeout-ms 60000` 6. `onequery query exec --org <org> --source <source> --sql '<sql>' --max-rows 100 --max-bytes 1048576 --cell-max-chars 2000 --timeout-ms 60000` Rules: - Always pass an explicit `--org` to org-scoped source and query commands. - Prefer `query validate` before `query exec` for unfamiliar SQL or provider dialects. - Start with `select 1`, a row count, or a bounded aggregate before wide row dumps. - Keep reads aggressively bounded with `--max-rows`, `--max-bytes`, `--cell-max-chars`, and small page sizes. - `query exec` supports `--page-size`, `--cursor`, and `--page-all`; `query validate` does not. - Only run read-only SQL. Reject obviously mutating statements instead of executing them. - Treat informal source names as aliases to resolve, not literal source keys. - Use shell-safe argument construction. Do not pass user text through shell operators, ...