Find external documentation, web sources, or remote code with citations. Local code navigation uses the configured code tools.
59
68%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/oma-search/SKILL.mdRoute an information request to the appropriate channel and return relevant sources with trust labels.
oma-scm; architecture analysis -> oma-architecture.Query, optional route hint (docs, web, code, local), source/recency constraints, and flags. Explicit --docs, --code, or --web selects the route; --strict filters trust, --wide retains labeled results, and --gitlab selects the remote code host.
Ranked sources with URL or file reference, route, relevance, trust level/score, and material fallback limits. Do not invent sources when no reliable result is found.
Context7 for docs, runtime web search, oma search/gh/glab for remote code, and configured code intelligence or native local search.
| Route | Primary | Fallback | Use for |
|---|---|---|---|
docs | Context7 resolve-library-id → query-docs | Web search | Official API/framework documentation |
web | Runtime web search | oma search fetch <url> for known result URLs | Web sources |
code | oma search code | Report unavailable host/auth | Remote repository patterns |
local | Configured code-intelligence provider | Native search and scoped reads | Current project files and symbols |
../_shared/core/code-intelligence.md.unknown with score —; do not imply verification.--strict: report that outcome and offer a wider or narrower query.Return evidence-backed results and disclose failed routes or source limitations. A domain score alone does not verify an individual claim.
resources/intent-rules.md only when classification is needed; select one route unless ambiguity requires more.resources/execution-protocol.md for the selected channel's command flags, fetch strategies, or normalization details.resources/trust-registry.md; reuse the current session cache. Apply --strict after scoring.oma search code "<query>" [--host gitlab] [--language <lang>] [--repo <owner/repo>]
oma search trust <domain>
oma search fetch <url>The CLI also exposes api, api:search, meta, rss, rss:google, media, archive, and doctor; use a primitive only when the selected route needs it.
Search may contact external services or inspect local code and spawn gh/glab processes. Query constraints, selected sources, and trust metadata are session context; persistent caches belong in generated state, not skill definitions.
resources/intent-rules.md (no explicit route or ambiguous query)resources/execution-protocol.md (selected channel only)resources/trust-registry.md (non-local sources)resources/error-playbook.md (route failures)resources/checklist.md (applicable route checks)resources/examples.md (unfamiliar input/output contracts)../_shared/core/code-intelligence.mdce19702
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.