Web Search Pro 2.1 Core Profile
This ClawHub package publishes the core retrieval profile of web-search-pro.
It is a code-backed Node runtime package, not an instruction-only bundle.
Use This Skill When
- - the caller needs live web search or news search
- the caller needs docs lookup or code lookup
- the caller may continue from search into extract, crawl, map, or research
- the agent needs explainable routing and visible federated-search gains
- the first run needs a real no-key baseline
Quick Start
The shortest successful path is:
- - Option A: No-key baseline
- Option B: Add one premium provider
- Then try docs, news, and research
Option A: No-key baseline
No API key is required for the first successful run.
CODEBLOCK0
Option B: Add one premium provider
If you only add one premium provider, start with TAVILY_API_KEY.
CODEBLOCK1
First successful searches
CODEBLOCK2
Then try docs, news, and research
CODEBLOCK3
Install Model
ClawHub installs this bundle directly as a code-backed Node skill pack.
- - hard runtime requirement: INLINECODE2
- no remote installer, curl-to-shell bootstrap, or Python helper transport in the baseline path
- optional runtime config file: INLINECODE3
- local state directory: INLINECODE4
Why Federated Search Matters
Federation is not just "more providers". It exposes compact gain metrics:
- - INLINECODE5
- INLINECODE6
- INLINECODE7
- INLINECODE8
- INLINECODE9
Runtime Contract
The planner's primary route.
Compact route explanation with confidence and federation summary.
Full route diagnostics exposed by
--explain-routing or
--plan.
The providers that actually returned results when fanout is active.
Compact federation gain summary for added providers, recovered results, corroboration, and
duplicate savings.
Cache hit plus TTL telemetry for agents.
- -
topicType, topicSignals, INLINECODE21
Structured planning summaries for the model-facing research pack.
Commands By Task
Included commands:
- - INLINECODE22
- INLINECODE23
- INLINECODE24
- INLINECODE25
- INLINECODE26
- INLINECODE27
- INLINECODE28
- INLINECODE29
- INLINECODE30
- INLINECODE31
- INLINECODE32
Runtime notes:
- - Node is the only hard runtime requirement.
- No API key is required for the baseline.
- Optional provider credentials or endpoints widen coverage.
- Baseline outbound requests use
curl when available and fall back to built-in fetch.
Baseline:
- - No API key is required for the baseline.
- INLINECODE35 is best-effort no-key search.
- INLINECODE36 is the no-key extract / crawl / map fallback.
Optional provider credentials or endpoints unlock stronger coverage:
CODEBLOCK4
Review and diagnostics:
CODEBLOCK5
Search keywords:
INLINECODE37 , news search, latest updates, current events, docs search,
API docs, code search, company research, competitor analysis, site crawl,
site map, multilingual search, Baidu search, answer-first search,
cited answers, explainable routing, INLINECODE53
Web Search Pro 2.1 核心配置文件
本 ClawHub 包发布了 web-search-pro 的核心检索配置文件。
它是一个基于代码的 Node 运行时包,而非纯指令包。
何时使用此技能
- - 调用者需要实时网页搜索或新闻搜索
- 调用者需要文档查找或代码查找
- 调用者可能从搜索进入提取、爬取、映射或研究
- 代理需要可解释的路由和可见的联邦搜索收益
- 首次运行需要真正的无密钥基线
快速开始
最短的成功路径是:
- - 选项 A:无密钥基线
- 选项 B:添加一个高级提供商
- 然后尝试文档、新闻和研究
选项 A:无密钥基线
首次成功运行无需 API 密钥。
bash
node {baseDir}/scripts/doctor.mjs --json
node {baseDir}/scripts/bootstrap.mjs --json
node {baseDir}/scripts/search.mjs OpenAI Responses API 文档 --json
选项 B:添加一个高级提供商
如果只添加一个高级提供商,请从 TAVILYAPIKEY 开始。
bash
export TAVILYAPIKEY=tvly-xxxxx
node {baseDir}/scripts/doctor.mjs --json
node {baseDir}/scripts/search.mjs 最新 OpenAI 新闻 --type news --json
首次成功搜索
bash
node {baseDir}/scripts/search.mjs OpenClaw 网页搜索 --json
node {baseDir}/scripts/search.mjs OpenAI Responses API 文档 --preset docs --plan --json
node {baseDir}/scripts/extract.mjs https://platform.openai.com/docs --json
然后尝试文档、新闻和研究
bash
node {baseDir}/scripts/search.mjs OpenAI Responses API 文档 --preset docs --json
node {baseDir}/scripts/search.mjs 最新 OpenAI 新闻 --type news --json
node {baseDir}/scripts/research.mjs OpenClaw 搜索技能全景 --plan --json
安装模型
ClawHub 将此包直接安装为基于代码的 Node 技能包。
- - 硬运行时要求:node
- 基线路径中无远程安装程序、curl-to-shell 引导程序或 Python 辅助传输
- 可选运行时配置文件:config.json
- 本地状态目录:.cache/web-search-pro
联邦搜索为何重要
联邦不仅仅是更多提供商。它暴露了紧凑的收益指标:
- - federated.value.additionalProvidersUsed
- federated.value.resultsRecoveredByFanout
- federated.value.resultsCorroboratedByFanout
- federated.value.duplicateSavings
- routingSummary.federation.value
运行时契约
规划器的主要路由。
包含置信度和联邦摘要的紧凑路由说明。
由 --explain-routing 或 --plan 暴露的完整路由诊断。
- - federated.providersUsed
当扇出激活时实际返回结果的提供商。
关于新增提供商、恢复结果、相互印证和重复节省的紧凑联邦收益摘要。
缓存命中及代理的 TTL 遥测。
- - topicType、topicSignals、researchAxes
面向模型研究包的规划摘要结构。
按任务划分的命令
包含的命令:
- - search.mjs
- extract.mjs
- crawl.mjs
- map.mjs
- research.mjs
- doctor.mjs
- bootstrap.mjs
- capabilities.mjs
- review.mjs
- cache.mjs
- health.mjs
运行时说明:
- - Node 是唯一的硬运行时要求。
- 基线无需 API 密钥。
- 可选的提供商凭证或端点可扩大覆盖范围。
- 基线出站请求在可用时使用 curl,否则回退到内置的 fetch。
基线:
- - 基线无需 API 密钥。
- ddg 是尽力而为的无密钥搜索。
- fetch 是无密钥提取/爬取/映射的回退方案。
可选的提供商凭证或端点可解锁更强的覆盖范围:
bash
TAVILYAPIKEY=tvly-xxxxx
EXAAPIKEY=exa-xxxxx
QUERITAPIKEY=xxxxx
SERPERAPIKEY=xxxxx
BRAVEAPIKEY=xxxxx
SERPAPIAPIKEY=xxxxx
YOUAPIKEY=xxxxx
SEARXNGINSTANCEURL=https://searx.example.com
Perplexity / Sonar:选择一种传输路径
PERPLEXITY
APIKEY=xxxxx
OPENROUTER
APIKEY=xxxxx
OPENROUTER
BASEURL=https://openrouter.ai/api/v1 # 可选覆盖
KILOCODE
APIKEY=xxxxx
或使用自定义的 OpenAI 兼容网关
PERPLEXITY
GATEWAYAPI_KEY=xxxxx
PERPLEXITY
BASEURL=https://gateway.example.com/v1
PERPLEXITY_MODEL=perplexity/sonar-pro # 接受 sonar
或 perplexity/sonar
审查和诊断:
bash
node {baseDir}/scripts/capabilities.mjs --json
node {baseDir}/scripts/doctor.mjs --json
node {baseDir}/scripts/bootstrap.mjs --json
node {baseDir}/scripts/review.mjs --json
搜索关键词:
网页搜索、新闻搜索、最新更新、当前事件、文档搜索、
API 文档、代码搜索、公司研究、竞争对手分析、网站爬取、
网站地图、多语言搜索、百度搜索、答案优先搜索、
引用答案、可解释路由、无密钥基线