wordbricks

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

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).

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.

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.

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.

Breaking changes

Test authoring guidance

Diagnose GitHub bug reports in wordbricks/onequery. Use when given a GitHub issue URL from wordbricks/onequery and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.

Use when the user wants to inspect company or customer data that lives behind Velen, run ad hoc read-only SQL or source API operations advertised by a Velen-connected source, explicitly inspect a past Velen insight by public ID or catalog request, manage org-scoped Knowledge Graph or persona memory through Velen, or update the Velen CLI/agent skill. Do not use for local databases, direct credentials, or SQL/API work that bypasses Velen access controls.

Use when the user wants to inspect company or customer data that lives behind Velen, configure Velen CLI org selection or local profiles, run ad hoc read-only SQL or source API operations advertised by a Velen-connected source, explicitly inspect a past Velen insight by public ID or catalog request, manage org-scoped Knowledge Graph or persona memory through Velen, or update the Velen CLI/agent skill. Do not use for local databases, direct credentials, or SQL/API work that bypasses Velen access controls.

Load when a user request can only be completed by connecting to a company data source through OneQuery-managed access — including internal metrics, analytics, customer or company data lookups, trend checks, dashboard validation, or read-only SQL investigation — even if the user does not mention OneQuery explicitly.

Use when the user wants to inspect company or customer data that lives behind OneQuery, resolve org or source context, validate or run ad hoc read-only SQL against a OneQuery-connected source, or discover available OneQuery CLI commands. Do not use for local databases, direct credentials, or write operations that bypass OneQuery access controls.