oma-search

# 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, Ser...