Use when you need information from web or codebase and want a structured summary. Handles API docs, library usage, best practices, error solutions, codebase conventions, or general knowledge questions.
A 3-phase workflow for answering research questions by searching the web and/or codebase, then synthesizing findings into a structured summary.
Before searching anything, understand what is being asked.
Execute searches iteratively. Maximum 3 rounds — then report what you have.
Search strategies:
After each round, check: did this answer part of the question? Re-anchor to the original question to prevent drift. Identify remaining gaps to target in the next round. Track all sources (URLs, file paths with line numbers).
Stop gathering when:
Produce the Research Summary in exactly this format:
## Research Summary: [Topic]
**Question:** [Original question restated from Phase 1]
### Key Findings
- [Finding 1 — concise, actionable]
- [Finding 2]
- ...
### Sources
- [URL or file:line_number 1]
- [URL or file:line_number 2]
### Confidence
[HIGH / MEDIUM / LOW] — [one sentence justification]
### Open Questions
- [Anything unresolved or worth further investigation]
Confidence levels:
| Phase | Input | Output | Key Rule | |-------|-------|--------|----------| | 1. Clarify | Research question | Restated question + sub-queries | State interpretation if ambiguous | | 2. Gather | Sub-queries | Raw findings with sources | Max 3 rounds, re-anchor each round | | 3. Synthesize | Findings | Research Summary | Always include sources + confidence |
| Mistake | Fix | |---|---| | Returning raw search results | Synthesize into Key Findings with your own words | | Searching endlessly without synthesizing | Stop after 3 rounds. Partial answer > no answer. | | Drifting to related but unasked topics | Re-read the original question after each round | | Using only one source for important claims | Triangulate against 2+ sources | | Broad search terms returning noise | Start narrow: specific function names, error strings, exact phrases | | Reading entire files when a section suffices | Glob-then-Read: find first, read only what matters |
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer