Search Router

Scheduling

Goal

Select the search or retrieval channel needed by the request and return sources with supporting evidence and retrieval limits.

Intent signature

• Find external documentation, web information, or remote implementation examples.
• Read a known external URL or supply external sources to another skill.

When to use

Library documentation, web research, remote code search, known-URL reading, and requests whose external source channel needs selection.

When NOT to use

• Pure local code exploration -> use configured code intelligence directly under ../_shared/core/code-intelligence.md; do not dispatch this skill.
• Git history/blame -> oma-scm; architecture analysis -> oma-architecture.

Expected inputs

Query or known URL; optional route hint (docs, web, code, fetch); version, recency, host, repository and source constraints; optional web-provider override. Explicit --docs, --code or --web selects the search route. --gitlab selects the remote code host. --strict requires suitable primary or official sources with inspected supporting content; --wide includes broader results with their limitations. These modifiers preserve the request's source constraints.

Expected outputs

An answer or relevant source list with source URL/file reference, route, actual provider, source type, content-read status, supporting evidence and material limitations. Include publication, retrieval and version details when observed. Do not invent results, dates, sources or certainty.

Dependencies

Context7 for documentation; the configured providers.web (native, brave or exa) for web discovery; oma search code/gh/glab for remote code; runtime retrieval tools or oma search fetch for known URLs. oma search providers reports registration, selection and credential metadata; oma doctor checks credential presence without verifying validity or API reachability.

Structural Flow