| name | search-analyst-pair |
| description | Turn any research request into a structured, reviewable brief — fact collection, risk analysis, and recommendation in three deterministic steps. |
| version | 1.0.0 |
| metadata | {"openclaw":{"requires":{"env":"[Truncated]","bins":"[Truncated]"},"primaryEnv":"OPENCLAW_TOKEN","emoji":"🔍","homepage":"https://github.com/baobaodawang-creater/neo-agent-lab"}} |
Search Analyst Pair
This skill packages a deterministic /hunt workflow for OpenClaw.
When a user message starts with /hunt, the workflow follows a strict 3-hop chain:
- Search (DeepSeek): gather facts and sources only.
- Analyst (Gemini): analyze Search output and identify key points and risks.
- Main (Kimi): synthesize Search + Analyst into final guidance.
Why this skill
- Prevents ad-hoc routing for critical tasks.
- Separates fact collection, analysis, and decision output.
- Supports both native OpenClaw orchestration and a FastAPI fallback runner.
Best-fit scenarios
- Time-sensitive research tasks that require reliable structure.
- Decision support where source traceability matters.
- Team workflows that need stable, reviewable output sections.
Requirements
- OpenClaw gateway running and reachable.
- Agent IDs available:
main, search, analyst.
tools.agentToAgent.enabled=true in OpenClaw config.subagents.allowAgents configured:
main allows search, analystsearch allows analyst
Behavior contract
- Trigger prefix:
/hunt
- Fixed order:
Search -> Analyst -> Main
- Fallback policy: if agent-to-agent spawn fails, the workflow must explicitly mark fallback output.
Usage examples
/hunt Review today's agent framework updates and give a practical migration plan.
/hunt Collect top legal AI workflow changes this week and assess implementation risk.
Output shape (recommended)
Search findingsAnalyst assessmentMain conclusion
