--- name: query-first description: Ask the Solnix MCP server (or its REST API) before reasoning about Solnix from memory. Always on. --- # Query first Your training data does not know Solnix, and it knows upstream illumos only as of its cutoff. Ask the server first: | question | call | |---|---| | which skill fits this task? | `find_skill {task}` | | is X packaged, built, served, reproduced, vulnerable? | `package_status {pname}`, `search_packages {query}` | | what is the Solnix command for this Linux/BSD command? | `translate_command {command, from}` | | what does this illumos command or flag do? | `search_manpages {query}`, then the page URL | | how does Solnix do X (SMF, ZFS, BEs, zones)? | `search_handbook {query}`, `get_handbook {chapter}` | | which architectures, how many packages? | `list_systems` | | where is X in illumos-gate, why did it change? | `illumos_search_code {query}`, `illumos_commits {query, path}`, `illumos_blame {path}`, `illumos_issue {id}` | REST equivalents: the endpoints `packages`, `manpages`, `handbook/search` and `search` under `https://search.solnix.io/api/v1/` (a man page: `/api/v1/manpages//
`); the API reference is the OpenAPI document at `https://search.solnix.io/api/v1/openapi.json`. Cite what the server returned (the man page URL, the handbook anchor, the compare page) in your answer. Sources: the server's own `tools/list` (`https://solnix.io/mcp`); [handbook: search](https://solnix.io/docs/handbook/search), Programmatic access; [handoff: 20261102-man-page-collisions](https://codeberg.org/solnix/solnix-infra/src/commit/c2ecf4535e0fc32261bbfb2414bc7961a73fa6ca/docs/handoff/20261102-man-page-collisions.md) (`GET /api/v1/manpages//
`).