This skill is responsible for choosing external information sources, not for local files or current repository retrieval:
- Code and technical documentation questions: prefer the
find-docsskill, querying via the Context7 CLI. - Other open web questions: prefer Exa WebSearch MCP for searching.
- When a specific URL is already available and you need to open, read, or verify the page content: use the OpenAI official Web Search provided by the current environment.
Tasks such as GitHub repositories, issues, PRs, commits, releases, workflows, and source code verification are handled by the dedicated GitHub skill.
Retrieval routing
用户问题
|
v
本地文件、当前仓库代码、日志或配置检索?
|-- 是 --> 不使用本 skill,按本地任务处理
|
v
GitHub 仓库、issue、PR、commit、release、workflow 或源码核对?
|-- 是 --> 使用 GitHub skill,停止本 skill
|
v
用户提供了具体 URL,或需要打开某个 URL 查看正文?
|-- 是 --> 使用 OpenAI 官方 Web Search 打开并读取页面
|
v
代码、库、框架、SDK、CLI、云服务、API 或其他技术文档问题?
|-- 是 --> 使用 find-docs skill;不可用时静默切换到 OpenAI 官方 Web Search
|
v
其他官网、博客、新闻、产品信息、价格规格或对比资料?
|-- 是 --> 使用 Exa WebSearch MCP;不可用时静默切换到 OpenAI 官方 Web Search
|
v
无法判断来源 --> 能合理默认时说明默认后继续,否则再澄清
Basic rules
- Code-related external material questions should preferentially go through
find-docs; non-code open web retrieval should preferentially go through Exa. - Exa is mainly used to discover web pages. After obtaining a specific URL, if you need to view or verify the content, use OpenAI official Web Search to open that URL.
- Prefer official sources and primary sources; when comparison or cross-verification is needed, then supplement with highly trusted third-party sources.
- You must open the pages that can support the conclusion, not rely only on search snippets.
- Keep traceable links in the answer, and distinguish retrieved facts, claims from web pages, and your own judgment.
- All retrieval is completed in the current context; do not delegate retrieval tasks to a subagent or Agent.
- If you cannot find it, state that it was not found; do not write guesses as facts.
Code and technical documentation questions
- Locate the
find-docsskill available in the current environment, and fully read itsSKILL.md。 - Follow the
find-docsprocess to use the Context7 CLI to query interfaces, parameters, configuration, examples, migration, and version behavior of libraries, frameworks, SDKs, CLIs, cloud services, or APIs. find-docsis only used as the source of truth for Context7 CLI commands and the query process; retrieval source selection, failover, and error presentation are governed by this skill.- When Context7 CLI does not cover the question, has insufficient quota, is unavailable, or the call fails, immediately switch to OpenAI official Web Search, and preferentially search the official documentation for that technology.
Do not use Exa instead of Context7 to query API or configuration details. Do not use Context7 to query news, blogs, product promotion pages, community discussions, or repository internal implementation.
Other open web questions
- Use Exa WebSearch MCP to search official websites, blogs, news, product information, prices, specifications, horizontal comparisons, or other public materials.
- First look for official sources and primary sources; when comparison is needed, then search highly trusted third-party sources.
- When you need to read the page content of a search result, hand the URL to OpenAI official Web Search to open and verify it.
- When Exa is unavailable, has insufficient quota, or the call fails, immediately switch to OpenAI official Web Search to complete the search and page reading.
Silent switching
- When Context7 CLI, Exa, or another preferred retrieval tool has insufficient quota, is rate-limited, missing, or unavailable, do not output intermediate prompts to the user such as "quota reached," "quota exhausted," login, recharge, or waiting for quota recovery.
- Do not repeatedly retry the same tool that has already been confirmed to have insufficient quota; directly use the above alternative sources to continue completing the task.
- In the final answer, only state the source actually used. Only when all available sources cannot support the conclusion should you state that verification could not be completed, and do not elaborate on the internal tool failure process.