description: Find authoritative sources and synthesize answers requires:
- Omni/Agent/Skills/web-search.md
Research
Find authoritative sources and synthesize answers for research questions.
Process
- Clarify - What exactly needs to be researched?
- Local first - Search codebase/files for existing knowledge
- Web search - Find external sources to fill gaps
- Cross-reference - Verify claims across multiple sources
- Synthesize - Combine findings into coherent answer
Guidelines
- Start with what you already know from the codebase
- Use multiple search queries with different phrasings
- Prefer authoritative sources (official docs, reputable sites)
- Every external claim must include a source URL in the output
- Note confidence level for each finding
- Acknowledge limitations and uncertainties
Output Format
{
"question": "The research question",
"summary": "Brief overall summary (2-3 sentences)",
"confidence": 0.85,
"findings": [
{
"claim": "Key insight or finding",
"source_url": "https://...",
"source_name": "Official Documentation"
},
{
"claim": "Another finding",
"source_url": "local:Omni/Something.hs",
"source_name": "Codebase"
}
],
"caveats": "Any limitations, uncertainties, or conflicting information",
"further_research": "Suggested follow-up questions if applicable"
}
Example
Question: “How does the deployer handle config changes?”
{
"question": "How does the deployer handle config changes?",
"summary": "The deployer only regenerates unit files when the nix store path changes. Config-only changes require a workaround.",
"confidence": 0.9,
"findings": [
{
"claim": "Unit files are regenerated based on store path comparison",
"source_url": "local:Omni/Deploy/Deployer.hs",
"source_name": "Deployer source"
},
{
"claim": "Known limitation: config changes without code changes don't trigger updates",
"source_url": "local:AGENTS.md",
"source_name": "Project docs"
}
],
"caveats": "Workaround exists: make a code change or manually restart",
"further_research": null
}