Run any Skill in Manus with one click

Get Started

onequery-openclaw

Stars17

Forks1

UpdatedJune 4, 2026 at 04:25

Use OpenClaw's exec tool to inspect orgs, sources, and run bounded read-only SQL through the OneQuery CLI directly.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

wordbricks

wordbricks/onequery

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	onequery-openclaw
description	Use OpenClaw's exec tool to inspect orgs, sources, and run bounded read-only SQL through the OneQuery CLI directly.
metadata	{"openclaw":{"requires":{"bins":["onequery"]},"homepage":"https://onequery.dev"}}

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:

onequery auth whoami
onequery org current or onequery org list --page-size 25
onequery source list --org <org> --page-size 25
onequery source show <source> --org <org>
onequery query validate --org <org> --source <source> --sql '<sql>' --max-rows 100 --max-bytes 1048576 --cell-max-chars 2000 --timeout-ms 60000
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, command substitution, or chained commands.
For long or quote-heavy SQL, write it to a temporary UTF-8 file and use --file <path> instead of forcing brittle shell escaping.
If onequery is unavailable, ask the operator to install it or expose it on PATH.
If exec runs under restrictive approval or allowlist policy, ask the operator to allow the resolved onequery binary or enable skill-bin auto-allow.
In your final answer, report the org, source, and any request id returned by the CLI.

Recovery:

Auth issues: rerun onequery auth whoami, then ask the user to refresh the OneQuery CLI session if needed.
Org ambiguity: onequery org list --page-size 25
Source ambiguity: onequery source list --org <org> --page-size 25, then onequery source show <source> --org <org>
SQL shape issues: onequery query validate ...

More from this repository

same repository

transitions-dev

wordbricks/onequery

Production-ready CSS transition snippets for web apps. Use when adding or reviewing UI motion for badges, dropdowns, modals, panel/page reveals, card resizes, number pop-ins, text/icon swaps, success checks, avatar-group hovers, and validation shakes. Supports namespaced commands: transitions reveal (list catalog), transitions review (audit project fit), and transitions apply (install the best-fit snippet with hooks and reduced-motion handling).

2026-05-2217

seo-geo

wordbricks/onequery

SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility, search optimization, search ranking, AI visibility, ChatGPT ranking, Google AI Overview, indexing, JSON-LD, meta tags, or keyword research.

2026-05-2117

onequery-blog-images

wordbricks/onequery

Generate or replace OneQuery blog thumbnail images and article diagram images for apps/landing. Use when Codex needs to create blog list thumbnails, social share thumbnails, in-article architecture diagrams, update blog imageSrc references, follow the OneQuery diagram design system, or use the bundled assets/diagram-design-system.png visual reference.

2026-05-0317

babysit-pr

wordbricks/onequery

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

2026-04-3017

code-breaking-changes

Breaking changes

Test authoring guidance

2026-04-3017

name	onequery-openclaw
description	Use OpenClaw's exec tool to inspect orgs, sources, and run bounded read-only SQL through the OneQuery CLI directly.
metadata	{"openclaw":{"requires":{"bins":["onequery"]},"homepage":"https://onequery.dev"}}

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:

onequery auth whoami
onequery org current or onequery org list --page-size 25
onequery source list --org <org> --page-size 25
onequery source show <source> --org <org>
onequery query validate --org <org> --source <source> --sql '<sql>' --max-rows 100 --max-bytes 1048576 --cell-max-chars 2000 --timeout-ms 60000
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, command substitution, or chained commands.
For long or quote-heavy SQL, write it to a temporary UTF-8 file and use --file <path> instead of forcing brittle shell escaping.
If onequery is unavailable, ask the operator to install it or expose it on PATH.
If exec runs under restrictive approval or allowlist policy, ask the operator to allow the resolved onequery binary or enable skill-bin auto-allow.
In your final answer, report the org, source, and any request id returned by the CLI.

Recovery:

Auth issues: rerun onequery auth whoami, then ask the user to refresh the OneQuery CLI session if needed.
Org ambiguity: onequery org list --page-size 25
Source ambiguity: onequery source list --org <org> --page-size 25, then onequery source show <source> --org <org>
SQL shape issues: onequery query validate ...