search-web

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Search-Web 技能

Search-Web Skill

概述

Overview

用最小搜索链路整合

Context7

、

Exa

、网页正文读取和

DeepWiki

。先确认必需 MCP 已可用，再拿官方文档、网页资料和仓库信息，避免首次使用时直接撞上工具缺失。

Integrate

Context7

Exa

, web content extraction and

DeepWiki

with the minimal search workflow. First confirm that the required MCPs are available, then obtain official documents, web resources and repository information to avoid running into missing tool issues directly on first use.

何时使用

When to Use

查询库、框架、SDK 或语言的官方文档
查找代码示例、教程、博客文章或最新网页资料
读取指定网页正文
查看 GitHub 仓库结构、文档或源码入口
不适用于纯本地代码检索或无需联网的普通问答

Query official documents of libraries, frameworks, SDKs or programming languages
Find code examples, tutorials, blog posts or latest web resources
Extract content from specified web pages
View GitHub repository structure, documents or source code entry
Not applicable for pure local code retrieval or common Q&A that does not require internet access

核心流程

Core Process

使用时的第一个步骤，固定先检查 setup 状态文件；如果状态缺失、未完成、与真实环境不一致，或者任一必需 MCP 不可用，立即转
```
references/setup.md
```
。
setup 状态通过后，再判断问题是否属于精确配置项、阈值、开关、
```
flag
```
、
```
option
```
、
```
parameter
```
、
```
env
```
一类问题。
命中配置项类问题时，先读
```
references/strategies/config-index-shortcut.md
```
，优先定位官方配置索引入口。
技术文档问题先走
```
Context7
```
，固定顺序是先
```
resolve-library-id
```
再
```
query-docs
```
；详细模板和错误示例看
```
examples/usage.md
```
。
只要属于联网搜索，固定使用
```
Exa
```
；不得改用任何其他搜索型 MCP。
```
Exa
```
不可用时只能回到
```
references/setup.md
```
修复。
```
Context7
```
之后继续走
```
Exa
```
，补网页资料、最新信息或官方入口。
```
Exa
```
结果命中 GitHub 仓库时走
```
DeepWiki
```
。
只有在用户已给出明确 URL，或
```
Exa
```
已经定位到目标网页后，才允许进入网页正文读取。正文读取不是搜索步骤，不能替代
```
Exa
```
。
最终按
```
references/rules/output-format.md
```
组织回答，优先给官方文档，再给网页资料、正文读取结果和仓库信息。

As the first step when using, always check the setup status file first; if the status is missing, incomplete, inconsistent with the real environment, or any required MCP is unavailable, immediately redirect to
```
references/setup.md
```
.
After the setup status is verified, judge whether the question belongs to types such as precise configuration items, thresholds, switches,
```
flag
```
,
```
option
```
,
```
parameter
```
,
```
env
```
.
When the question is a configuration item type, read
```
references/strategies/config-index-shortcut.md
```
first, and prioritize locating the official configuration index entry.
For technical document questions, use
```
Context7
```
first, the fixed order is
```
resolve-library-id
```
first then
```
query-docs
```
; see
```
examples/usage.md
```
for detailed templates and error examples.
As long as it is an internet search, always use
```
Exa
```
; do not switch to any other search-type MCP. When
```
Exa
```
is unavailable, you can only go back to
```
references/setup.md
```
for repair.
After
```
Context7
```
, proceed to
```
Exa
```
to supplement web resources, latest information or official entries.
When the
```
Exa
```
results hit a GitHub repository, use
```
DeepWiki
```
.
Only when the user has provided a clear URL, or
```
Exa
```
has located the target web page, is web content extraction allowed. Content extraction is not a search step and cannot replace
```
Exa
```
.
Finally organize the answer according to
```
references/rules/output-format.md
```
, give official documents first, then web resources, content extraction results and repository information.

MCP 使用边界

MCP Usage Boundaries

技术文档：只允许
```
Context7
```
联网搜索：只允许
```
Exa
```
GitHub 仓库：只允许
```
mcp-deepwiki
```
网页正文：只允许在“已知 URL 的非搜索读取”场景使用宿主已提供的正文读取工具
禁止把
```
open-websearch
```
、通用浏览器搜索或其他搜索型 MCP 当成
```
Exa
```
的替代品

Technical documents: only
```
Context7
```
is allowed
Internet search: only
```
Exa
```
is allowed
GitHub repository: only
```
mcp-deepwiki
```
is allowed
Web content: only allowed to use the host-provided content extraction tool in the scenario of "non-search reading with known URL"
It is forbidden to use
```
open-websearch
```
, general browser search or other search-type MCPs as substitutes for
```
Exa
```

按需继续加载

Load Additional Documents As Needed

只有在以下场景再读

examples/usage.md

：

需要
```
Context7
```
、
```
Exa
```
、网页正文读取或
```
DeepWiki
```
的参数示例
需要
```
Context7
```
的错误示范、调用顺序示例或多源整合案例
需要网页读取降级案例
需要常见失败场景或排障示例

如果示例文档与正文流程冲突，以本文件为准。

首次使用，或者遇到状态文件缺失、状态与真实环境不一致、

Context7

Exa

DeepWiki

未注册或连接失败时，读

references/setup.md

。

需要标准输出模板、来源标注规则或 Markdown 结构约束时，读

references/rules/output-format.md

。

遇到精确配置项名、阈值、开关、

flag

、

option

、

parameter

、

env

一类问题时，读

references/strategies/config-index-shortcut.md

。

Read

examples/usage.md

only in the following scenarios:

Need parameter examples for
```
Context7
```
,
```
Exa
```
, web content extraction or
```
DeepWiki
```
Need error examples, call sequence examples or multi-source integration cases for
```
Context7
```
Need web page reading downgrade cases
Need common failure scenarios or troubleshooting examples

If the example document conflicts with the process in this file, this file shall prevail.

For first use, or when encountering missing status files, inconsistent status with the real environment,

Context7

Exa

DeepWiki

not registered or connection failed, read

references/setup.md

When you need standard output templates, source annotation rules or Markdown structure constraints, read

references/rules/output-format.md

When encountering questions about precise configuration item names, thresholds, switches,

flag

option

parameter

env

, etc, read

references/strategies/config-index-shortcut.md

输出要求

Output Requirements

最终回答前，必须按
```
references/rules/output-format.md
```
格式化
明确标注来源类型：
```
Context7
```
、
```
Exa
```
、网页读取、
```
DeepWiki
```
保留原始链接、文档入口或仓库标识
如果
```
Exa
```
缺失、不可用或环境异常，不允许切换到其他搜索型 MCP，必须直接说明并回到 setup/repair
如果发生降级、读取失败或信息不足，要直接说明
不编造未读取到的内容

Before final answer, it must be formatted according to
```
references/rules/output-format.md
```
Clearly mark the source type:
```
Context7
```
,
```
Exa
```
, web page extraction,
```
DeepWiki
```
Retain original links, document entries or repository identifiers
If
```
Exa
```
is missing, unavailable or the environment is abnormal, it is not allowed to switch to other search-type MCPs, you must explain directly and return to setup/repair
If downgrade, reading failure or insufficient information occurs, explain directly
Do not make up content that has not been retrieved