oliverv/caro / .agents/skills/oma-search
oma-search
VerifiedFind external documentation, web sources, or remote code with citations. Local code navigation uses the configured code tools.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.8 KB |
| resources/checklist.md | markdown | 1.7 KB |
| resources/error-playbook.md | markdown | 5.1 KB |
| resources/examples.md | markdown | 4.2 KB |
| resources/execution-protocol.md | markdown | 3.0 KB |
| resources/intent-rules.md | markdown | 2.7 KB |
| resources/trust-registry.md | markdown | 5.0 KB |
resources/examples.md
View on GitHub# Search Agent - Input/Output Examples
## Example 1: docs route (auto-detected)
**Input:**
```
/oma-search "React useEffect official docs"
```
**Intent Classification:**
- Keyword "official docs" detected -> `docs` mode
**Output:**
```
Query: "React useEffect official docs"
Mode: docs (auto)
DOCS #1 useEffect — react.dev [verified,lang-docs 0.95]
DOCS #2 Synchronizing with Effects — react.dev [verified,lang-docs 0.95]
DOCS #3 useEffect API Reference — react.dev [verified,lang-docs 0.95]
```
## Example 2: web route (auto-detected)
**Input:**
```
/oma-search "Redis pub/sub use cases"
```
**Intent Classification:**
- Keyword "use cases" detected -> `web` mode
**Output:**
```
Query: "Redis pub/sub use cases"
Mode: web (auto)
WEB #1 Redis Pub/Sub Guide — redis.io/docs [verified,official-site 0.90]
WEB #2 Real-time Chat with Redis — dev.to [external,blog 0.40]
WEB #3 Redis Pub/Sub Patterns — stackoverflow [community,qna 0.70]
WEB #4 Redis Event-Driven Architecture — medium [external,blog 0.35]
```
## Example 3: code route (flag override)
**Input:**
```
/oma-search --code "OAuth PKCE implementation TypeScript"
```
**Intent Classification:**
- `--code` flag -> skip classification, forced `code` mode
**Output:**
```
Query: "OAuth PKCE implementation TypeScript"
Mode: code (flag)
CODE #1 src/auth/pkce.ts — panva/oauth4webapi [github]
CODE #2 lib/pkce.ts — auth0/nextjs-auth0 [github]
CODE #3 packages/oauth/src/pkce.ts — lucia-auth/lucia [github]
```
## Example 4: Ambiguous query (fallback parallel)
**Input:**
```
/oma-search "Next.js middleware"
```
**Intent Classification:**
- No clear keyword signal -> fallback `web` + `docs` parallel
**Output:**
```
Query: "Next.js middleware"
Mode: docs + web (auto)
DOCS #1 Middleware — nextjs.org/docs [verified,lang-docs 0.95]
DOCS #2 next.config.js — nextjs.org/docs [verified,lang-docs 0.95]
WEB #3 Middleware Deep Dive — vercel.com/blog [verified,vendor 0.90]
WEB #4 Next.js Middleware Guide — freecodecamp [external,tutorial 0.45]
```
## Example 5: --strict mode
**Input:**
```
/oma-search --strict "JWT refresh token rotation"
```
**Intent Classification:**
- `--strict` modifier -> filter to verified+ (>= 0.85)
- No route flag -> fallback `web` + `docs`
**Output:**
```
Query: "JWT refresh token rotation"
Mode: docs + web (auto, strict)
DOCS #1 JWT Best Practices — datatracker.ietf.org [verified,standards 0.95]
WEB #2 Token Rotation — auth0.com/docs [verified,official-site 0.90]
WEB #3 Refresh Token Rotation — auth0.com/docs [verified,official-site 0.90]
Filtered: 4 results below trust threshold (0.85). Use --wide to see all.
```
## Example 6: GitLab code search
**Input:**
```
/oma-search --code --gitlab "CI pipeline caching strategy"
```
**Output:**
```
Query: "CI pipeline caching strategy"
Mode: code (flag, gitlab)
CODE #1 .gitlab-ci.yml — gitlab-org/gitlab [gitlab]
CODE #2 ci/cache.yml — gitlab-org/omnibus-gitlab [gitlab]
CODE #3 .gitlab-ci.yml — getsentry/sentry [gitlab]
```
## Example 7: Shared infrastructure call (from oma-debug)
**Context:** oma-debug encounters an unfamiliar error message
**Internal call:**
```
Intent: web
Query: "TypeError: Cannot read properties of undefined (reading 'map') React"
```
**Output returned to oma-debug:**
```
Query: "TypeError: Cannot read properties of undefined (reading 'map') React"
Mode: web (explicit)
WEB #1 Common React Error Fix — stackoverflow [community,qna 0.70]
WEB #2 Handling Undefined in React — react.dev [verified,lang-docs 0.95]
WEB #3 TypeError Debugging — dev.to [external,blog 0.40]
```
## Example 8: docs fallback to web
**Input:**
```
/oma-search --docs "htmx form validation"
```
**Context7 fails to resolve "htmx" library.**
**Output:**
```
Query: "htmx form validation"
Mode: docs -> web (fallback)
Could not find official docs via Context7. Showing web results.
WEB #1 Form Validation — htmx.org [verified,official-site 0.90]
WEB #2 htmx Validation Guide — dev.to [external,blog 0.40]
WEB #3 htmx Form Patterns — reddit.com/r/htmx [community,forum 0.55]
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |