Imported from wordbricks/onequery (AGENTS.md). Install upstream with npx skills add wordbricks/onequery. Copyright stays with the author.

If you encounter something surprising or confusing in this project, flag it as a comment.

Runtime: Node.js mostly, (Rust for apps/cli).
Contract: Connect RPC (Protobuf contracts locates at proto/)
Testing: Vitest
Linter/formatter: oxlint, oxfmt
For linting, use bun lint --format json. For type-aware lint, append --type-aware flag (takes more time then normal lint).
For checking lint/format for whole monorepo, use bunx turbo check --json, to fix, bunx turbo check:fix
For type checking, use bunx turbo typecheck --json.
For testing, use bunx turbo test --json, not bun test.
For tools, use mise exec.

Auto-generated files and how to generate them:

NOTE: Don't edit them manually.

packages/proto-cli/src/** - Generated by Buf from onequery/cli/v1
packages/proto-runtime/src/** - Generated by Buf from onequery/runtime/v1
packages/proto-workflow/src/** - Generated by Buf from onequery/workflow/v1
- packages/cli-server/src/connect/** contains handwritten Connect handlers/adapters that import generated service descriptors from packages/proto-*.
apps/dashboard/src/routeTree.gen.ts - Generated by TanStack Router
**/worker-configuration.d.ts - Generated by Wrangler
packages/ui/src/components/ui/** - Generated by shadcn/ui CLI
packages/db/src/migrations/** - Generated by Drizzle CLI

Install onequery and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

onequery

About

Auto-generated files and how to generate them:

Use it

Install onequery and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews