Oh-my-agent oma-search
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.
install
source · Clone the upstream repo
git clone https://github.com/first-fluke/oh-my-agent
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/first-fluke/oh-my-agent "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.agents/skills/oma-search" ~/.claude/skills/first-fluke-oh-my-agent-oma-search && rm -rf "$T"
manifest:
.agents/skills/oma-search/SKILL.mdsource content
Search Agent - Intent-Based Search Router
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)
Core Rules
- Classify intent before searching: every query goes through IntentClassifier first
- One query, one best route: avoid redundant multi-route unless intent is ambiguous
- Trust score every result: all non-local results get domain trust labels from the registry
- Flags override classifier: user-provided flags (
,--docs
,--code
,--web
,--strict
,--wide
) always take precedence--gitlab - Fail forward: if primary route fails, fall back gracefully (docs->web, web->
strategies)oma search fetch - No additional MCP required: Context7 for docs, runtime native for web, CLI for code, Serena for local
- Vendor-agnostic web search: use whatever the current runtime provides (WebSearch, Google, Bing)
- Domain-level trust only: do not attempt sub-path or page-level scoring
Routes
| Route | Primary Tool | Fallback | Trigger |
|---|---|---|---|
| Context7 MCP ( → ) | route | Official docs, API reference |
| Runtime native search | (api/probe/impersonate/browser) | Tutorials, examples, solutions |
| / | — | Implementation patterns, repos |
| Serena MCP (delegate) | — | Current project files, symbols |
Default Workflow
- Parse — Extract query, detect flags, classify intent
- Route — Dispatch to the appropriate search channel(s)
- Collect — Gather results from dispatched routes
- Score — Attach trust labels to each result domain
- Present — Format and rank results for the user
Invocation
Standalone
/oma-search "React Server Components streaming" /oma-search --docs "Next.js middleware" /oma-search --code "PKCE implementation" /oma-search --strict "JWT refresh token rotation"
Shared Infrastructure (from other skills)
Other skills reference oma-search by specifying intent and query:
- State intent:
|docs
|web
|codelocal - Pass query string
- Use Trust Score in results to weigh source reliability
How to Execute
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.
Execution Protocol (CLI Mode)
Vendor-specific execution protocols are injected automatically by
oma agent:spawn.
Source files live under ../_shared/runtime/execution-protocols/{vendor}.md.
References
- Execution steps:
resources/execution-protocol.md - Intent classification:
resources/intent-rules.md - Trust registry:
resources/trust-registry.md - Examples:
resources/examples.md - Checklist:
resources/checklist.md - Error recovery:
resources/error-playbook.md - Context loading:
../_shared/core/context-loading.md - Context budget:
../_shared/core/context-budget.md - Lessons learned:
../_shared/core/lessons-learned.md