Intent-based search router with trust scoring. Routes queries to optimal channels (Context7 docs, native web search, gh/glab code search, Serena local) and attaches domain trust labels. Use for search, find, lookup, reference, docs, code search, and web research.
インストール
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Intent-based search router with trust scoring. Routes queries to optimal channels (Context7 docs, native web search, gh/glab code search, Serena local) and attaches domain trust labels. Use for search, find, lookup, reference, docs, code search, and web research.
Search Agent - Intent-Based Search Router
Scheduling
Goal
Classify information-seeking requests, route them to the best search channel, attach trust labels, and return source-grounded results.
Intent signature
User asks to search, find, look up, reference docs, inspect official documentation, search GitHub/GitLab code, or gather web research.
Another skill needs reusable search infrastructure with trust scoring.
When to use
Finding official library/framework documentation
Web research for tutorials, examples, comparisons, and solutions
Searching GitHub/GitLab code for implementation patterns
Any query where the search channel is unclear (auto-routing)
Other skills needing search infrastructure (shared invocation)
When NOT to use
Local codebase exploration only -> use Serena MCP directly
Git history or blame analysis -> use SCM Agent
Full architecture research -> use Architecture Agent (may invoke this skill internally)
Expected inputs
Query string, intent hint, or explicit flags such as --docs, --code, --web, --strict, --wide, --gitlab
Optional required source type, recency, domain, or trust constraints
Expected outputs
Ranked search results with route, source, trust label, and concise relevance summary
Fallback explanation when primary route fails
Source links or references suitable for the calling skill
Dependencies
Context7 MCP for docs, runtime-native web search, gh/glab for code, Serena for local search
resources/intent-rules.md, resources/trust-registry.md, execution protocol, examples, and checklist
Control-flow features
Branches by classified intent, user flags, route success/failure, and trust constraints
May call web/docs/code/local tools
Scores domains at domain level only
Structural Flow
Entry
Parse the query and flags.
Classify the search intent.
Select one best route unless ambiguity or flags justify more.
Scenes
PREPARE: Parse query and classify route.
ACT: Dispatch to docs, web, code, or local search.
ACQUIRE: Collect search results and source metadata.
VERIFY: Apply trust scoring and route-specific quality checks.
FINALIZE: Present ranked results or fallback status.
Transitions
If --docs, --code, --web, --strict, --wide, or --gitlab is provided, flags override classifier.
If docs route fails, fall back to web.
If web search needs fetch escalation, use oma search fetch strategies.
If query is purely local, use Serena MCP instead of web.
Failure and recovery
If primary route fails, fall forward to the next appropriate route.
If trust score is weak, label it instead of hiding uncertainty.
If no reliable results exist, report that and suggest a narrower query.
Exit
Success: results are routed, trust-scored, and source-grounded.
Partial success: route failures or trust limitations are explicit.
Logical Operations
Actions
Action
SSL primitive
Evidence
Parse query and flags
READ
User request
Classify intent
SELECT
Intent rules
Dispatch search route
CALL_TOOL
Docs, web, code, local tools
Collect results
READ
Search outputs
Score trust
VALIDATE
Trust registry
Rank and format
INFER
Relevance and trust
Report results
NOTIFY
Final answer
Tools and instruments
Context7 docs tools
Runtime-native web search
gh search code or glab api
Serena MCP for local project search
Canonical command path
gh search code "<query>"
glab api "/search?scope=blobs&search=<query>"
For docs and web routes, use the runtime's available official-docs or web-search tools after classifying intent; do not duplicate routes unless the intent is ambiguous.
Other skills reference oma-search by specifying intent and query:
State intent: docs | web | code | local
Pass query string
Use Trust Score in results to weigh source reliability
References
Follow resources/execution-protocol.md step by step.
See resources/examples.md for input/output examples.
Use resources/intent-rules.md for intent classification reference.
Use resources/trust-registry.md for domain trust scoring reference.
Before submitting, run resources/checklist.md.
Vendor-specific execution protocols are injected automatically by oma agent:spawn.
Source files live under ../_shared/runtime/execution-protocols/{vendor}.md.
