linkfox-ai-mode-google-search
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseGoogle AI Search
Google AI搜索
This skill calls Google Search in AI Mode to get the AI Overview answer for a single keyword. Only one question per call is supported — there is no multi-turn follow-up within a single request. The response is unstructured Markdown — summarize it directly, do not route it to a data-analysis sandbox.
本技能调用Google搜索的AI Mode,获取单个关键词对应的AI概览回答。每次调用仅支持一个问题——单次请求内不支持多轮跟进。返回结果为非结构化Markdown格式,请直接进行总结,无需路由至数据分析沙箱。
Core Concepts
核心概念
The tool drives Google's AI Mode (the panel that appears at the top of Google search results and synthesizes an answer with citations):
- The required is sent to Google as the query and the AI Overview for it is captured.
keyword - Single-round only: each call handles exactly one question. There is no parameter for follow-ups.
prompts - For follow-up questions: the agent must summarize the previous AI Overview answer (key points, citations, relevant context) and concatenate it with the new question into a new , then make a fresh API call.
keyword - All answers are returned as a single Markdown document under , with citations linked to the source pages.
stdout
resultsNum0本工具调用Google的AI Mode(即Google搜索结果顶部出现的、整合来源信息生成回答的面板):
- 将必填的作为查询词发送至Google,并抓取对应的AI概览内容。
keyword - 仅支持单轮对话:每次调用仅处理一个问题,无用于跟进的参数。
prompts - 跟进问题处理方式:Agent必须总结之前的AI概览回答(核心要点、引用来源、相关上下文),并将其与新问题拼接成新的,然后发起新的API调用。
keyword - 所有回答以单个Markdown文档形式返回至字段,同时包含指向来源页面的引用链接。
stdout
resultsNum0Parameters
参数说明
| Parameter | Type | Required | Description |
|---|---|---|---|
| keyword | string | Yes | Google search keyword. Sent as the |
| 参数 | 类型 | 是否必填 | 描述 |
|---|---|---|---|
| keyword | string | 是 | Google搜索关键词。作为 |
Response Fields
响应字段
| Field | Type | Description |
|---|---|---|
| stdout | string | Markdown document with the AI Overview for the keyword, plus inline citation links |
| sourceUrl | string | The Google AI Mode search URL that was actually requested |
| resultsNum | integer | Number of AI Overview blocks rendered (0 = keyword did not trigger AI Overview) |
| code / errcode | string / integer | |
| msg / errmsg | string | |
| costTime | integer | API latency in milliseconds |
| costToken | integer | Tokens consumed (only billed on success) |
| taskId | string | Upstream task identifier for tracing |
| type | string | Render hint, fixed value |
| 字段 | 类型 | 描述 |
|---|---|---|
| stdout | string | 包含关键词AI概览内容及内嵌引用链接的Markdown文档 |
| sourceUrl | string | 实际请求的Google AI Mode搜索URL |
| resultsNum | integer | 渲染的AI概览模块数量(0表示关键词未触发AI概览) |
| code / errcode | string / integer | 成功时为 |
| msg / errmsg | string | 成功时为 |
| costTime | integer | API响应延迟(毫秒) |
| costToken | integer | 消耗的Token数量(仅成功调用时计费) |
| taskId | string | 用于追踪的上游任务标识 |
| type | string | 渲染提示,固定值为 |
调用方式
调用方式
- API 端点:(完整参数/响应/错误码见
POST /aiMode/googleSearch)references/api.md - Python 脚本:
python scripts/google_ai_search.py '<JSON 参数>' [--inline] - 成本约束:本工具会消耗积分;同一会话同一参数组合默认只调用一次,脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探;需要继续检索时先向用户说明会产生额外消耗。
输出策略(脚本默认行为):
- 始终将完整响应写入 (
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-ai-mode-google-search-<timestamp>.json为脚本执行时的工作目录,在 Claude Code 里即当前项目目录;<cwd>取自环境变量<session>,按用户任务自动聚合;禁止写入 /tmp,当前目录不可写则报错)SESSION_ID - 响应体 ≤ 8 KB:落盘后把完整 JSON 打印到 stdout
- 响应体 > 8 KB:落盘后 stdout 只输出摘要(顶层字段、常见计数如 /
total、最大列表字段的长度 + 前 3 条样本)costToken - 加 强制全量打印到 stdout(同样落盘)
--inline
读数据建议:先看摘要判断是否足够;需要具体字段时优先用 或 从保存的 json 文件按需抽取,避免整份 JSON 进入上下文。
jqConvertFrom-Json- API 端点:(完整参数/响应/错误码详见
POST /aiMode/googleSearch)references/api.md - Python 脚本:
python scripts/google_ai_search.py '<JSON 参数>' [--inline] - 成本约束:本工具会消耗积分;同一会话中同一参数组合默认仅调用一次,脚本自带24小时本地缓存。失败/空结果时不得自动更换关键词、翻页或修改邮编连续尝试;如需继续检索,需先向用户说明会产生额外消耗。
输出策略(脚本默认行为):
- 始终将完整响应写入 (
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-ai-mode-google-search-<timestamp>.json为脚本执行时的工作目录,在Claude Code中即当前项目目录;<cwd>取自环境变量<session>,按用户任务自动聚合;禁止写入/tmp目录,若当前目录不可写则报错)SESSION_ID - 响应体 ≤ 8 KB:落盘后将完整JSON打印至stdout
- 响应体 > 8 KB:落盘后仅在stdout输出摘要(顶层字段、/
total等常见计数、最长列表字段的长度+前3条样本)costToken - 添加参数可强制将全量内容打印至stdout(同样会落盘)
--inline
读数据建议:先查看摘要判断是否满足需求;如需提取具体字段,优先使用或从保存的JSON文件中按需抽取,避免整份JSON进入上下文。
jqConvertFrom-Json解决认证和积分问题
解决认证和积分问题
发生以下异常情况时,采用 references/onboarding.md 引导解决问题:
出现以下异常情况时,参考引导用户解决:
references/onboarding.md异常情况
异常情况
- 未配置API Key:环境变量未配置 ,也未配置
LINKFOX_AGENT_API_KEY。LINKFOXAGENT_API_KEY - 响应401或402状态码
- 响应提示积分或余额不足:消息含"积分余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值",或类似含义的内容。
- 未配置API Key:环境变量未配置或
LINKFOX_AGENT_API_KEY。LINKFOXAGENT_API_KEY - 响应401或402状态码
- 响应提示积分或余额不足:消息包含“积分余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值”或类似含义的内容。
How to Build Queries
查询构建指南
Each call takes a single . For follow-up questions, the agent must summarize the previous result and build a new query.
keyword每次调用仅接收单个参数。对于跟进问题,Agent必须总结之前的结果并构建新的查询词。
keywordTips
技巧提示
- Front-load context in : include market/region cues when relevant (
keyword) — the AI Overview is sensitive to phrasing."open-ear bone-conduction headphones US 2026" - Match the language to the target market: ask in English for US/UK/AU markets, Japanese for JP, German for DE, etc. — the AI Overview is biased toward the locale's language.
- Use natural-language questions: phrasing like "compare against" / "what are the unsolved pain points" elicits richer AI Overview output than single keywords.
- For follow-ups, summarize and re-ask: when the user wants to dig deeper, the agent should summarize key points from the previous AI Overview response and concatenate with the new question into a new for a fresh call. Example:
keyword"Based on the AI overview that top bone-conduction headphones are Shokz OpenRun Pro and AfterShokz Aeropex, what are the unsolved technical pain points compared to in-ear earbuds?"
- 在前置上下文:相关时加入市场/地区线索(如
keyword)——AI概览对表述方式较为敏感。"open-ear bone-conduction headphones US 2026" - 匹配目标市场语言:针对美/英/澳市场用英文提问,日本市场用日文,德国市场用德文等——AI概览会偏向对应地区的语言。
- 使用自然语言提问:类似“compare against”/“what are the unsolved pain points”的表述比单个关键词能触发更丰富的AI概览输出。
- 跟进问题需总结并重提:当用户需要深入挖掘时,Agent应总结之前AI概览响应的核心要点,并与新问题拼接成新的发起新调用。示例:
keyword"Based on the AI overview that top bone-conduction headphones are Shokz OpenRun Pro and AfterShokz Aeropex, what are the unsolved technical pain points compared to in-ear earbuds?"
Usage Examples
使用示例
1. Single-shot AI Overview
json
{
"keyword": "GaN charger vs traditional charger comparison"
}2. Cross-border product research
json
{
"keyword": "best open-ear bone conduction headphones 2026 US"
}3. Follow-up question (agent summarizes prior result and re-asks in a new call)
First call:
json
{
"keyword": "best open-ear bone conduction headphones 2026 US"
}Second call (agent builds context summary + new question):
json
{
"keyword": "The AI overview mentioned OpenRun Pro and AfterShokz Aeropex as top picks for bone conduction headphones. What unsolved technical pain points still exist compared to in-ear earbuds?"
}4. Consumer preference snapshot
json
{
"keyword": "robot vacuum buying preferences 2026 reddit"
}5. Long-tail keyword exploration for selection
json
{
"keyword": "smart pet feeder for cats with camera"
}1. 单次AI概览查询
json
{
"keyword": "GaN charger vs traditional charger comparison"
}2. 跨境产品调研
json
{
"keyword": "best open-ear bone conduction headphones 2026 US"
}3. 跟进问题(Agent总结之前结果并重提)
首次调用:
json
{
"keyword": "best open-ear bone conduction headphones 2026 US"
}二次调用(Agent构建上下文总结+新问题):
json
{
"keyword": "The AI overview mentioned OpenRun Pro and AfterShokz Aeropex as top picks for bone conduction headphones. What unsolved technical pain points still exist compared to in-ear earbuds?"
}4. 消费者偏好快照
json
{
"keyword": "robot vacuum buying preferences 2026 reddit"
}5. 长尾选品探索
json
{
"keyword": "smart pet feeder for cats with camera"
}Display Rules
展示规则
- Render the Markdown directly: is already structured Markdown with headings, bullets, and citation links — preserve that structure when answering the user.
stdout - Cite sources: keep the inline reference links from so the user can verify each claim.
stdout - Flag empty AI Overview: if is
resultsNum, tell the user Google AI Overview did not trigger for that keyword and suggest rephrasing or trying a different region.0 - Don't reroute to a data-analysis sandbox: the output is unstructured text and not suitable for SQL-like processing.
- Indicate freshness: results reflect Google AI Mode at call time; mention this when the user asks about recency.
- Handle business errors: if /
codeis noterrcode, surface the200/msgto the user and suggest retrying or refining the input.errmsg
- 直接渲染Markdown:已为包含标题、项目符号和引用链接的结构化Markdown——回复用户时请保留该格式。
stdout - 保留来源引用:保留中的内嵌引用链接,方便用户验证每个结论。
stdout - 标记空AI概览:若为
resultsNum,需告知用户该关键词未触发Google AI概览,并建议重新表述或尝试其他地区。0 - 请勿路由至数据分析沙箱:输出为非结构化文本,不适合类SQL处理。
- 标注时效性:结果反映调用时Google AI Mode的状态,当用户询问时效性时需提及此点。
- 处理业务错误:若/
code不为errcode,需将200/msg告知用户,并建议重试或优化输入。errmsg
Important Limitations
重要限制
- Unstructured output: Markdown text only — no structured tables, no second-pass data query.
- AI Overview not guaranteed: some keywords (especially niche, ambiguous, or sensitive ones) do not trigger AI Overview at all ().
resultsNum = 0 - Single-round only: no multi-turn follow-up within one call. For follow-ups, the agent must summarize previous context and make a new call.
- Locale follows Google's defaults: the tool uses Google's standard AI Mode endpoint without an explicit region switch; bias the language and wording of to match the market you care about.
keyword - Real-time fetch: results are pulled live, so output for the same keyword can vary across calls.
- 非结构化输出:仅为Markdown文本——无结构化表格,不支持二次数据查询。
- AI概览不保证触发:部分关键词(尤其是小众、模糊或敏感关键词)完全不会触发AI概览()。
resultsNum = 0 - 仅支持单轮对话:单次调用内不支持多轮跟进。如需跟进,Agent必须总结之前的上下文并发起新调用。
- 地区遵循Google默认设置:本工具使用Google标准AI Mode端点,无明确地区切换功能;需通过调整的语言和表述来匹配目标市场。
keyword - 实时抓取:结果为实时获取,同一关键词的输出可能因调用时间不同而变化。
User Expression & Scenario Quick Reference
用户表述与场景速查
Applicable — when the user wants AI-summarized live web information:
| User Says | Scenario |
|---|---|
| "用 Google AI 帮我搜...", "Google AI Overview 看下..." | Direct AI Overview lookup |
| "海外消费者对 XX 怎么看", "美国市场对 XX 的偏好" | Cross-border consumer preference |
| "XX 的最新趋势 / 痛点 / 使用场景" | Deep research |
| "顺便问一下 / 然后再追问 ..." | Follow-up needed (agent summarizes prior result and re-asks in new call) |
| "网页上对 XX 的总结", "搜索引擎里大家怎么说 XX" | Web-wide summarization |
| "长尾选品调研 / 蓝海选品方向" | Long-tail product exploration |
Not applicable — better routed elsewhere:
- Querying internal structured datasets (use the appropriate data query tool).
- Amazon ABA search-term analytics (use the ABA data explorer).
- Pulling structured product listings, prices, reviews from a specific platform (use the matching platform skill).
- Plain web search where the user only needs raw page content with no AI synthesis (use the standard web search skill).
- Image generation, image recognition, or file analysis.
Boundary judgment: when the user wants "AI 帮我汇总网上的说法" or "用谷歌搜一下", this skill applies. If the user wants to ask follow-up questions, the agent should summarize the previous answer and make a new call. If they explicitly want raw search results, structured data, or already have a specialized data source, do not use this skill.
适用场景——当用户需要AI汇总的实时网页信息时:
| 用户表述 | 场景 |
|---|---|
| "用 Google AI 帮我搜...", "Google AI Overview 看下..." | 直接查询AI概览 |
| "海外消费者对 XX 怎么看", "美国市场对 XX 的偏好" | 跨境消费者偏好分析 |
| "XX 的最新趋势 / 痛点 / 使用场景" | 深度调研 |
| "顺便问一下 / 然后再追问 ..." | 需要跟进(Agent总结之前结果并重提) |
| "网页上对 XX 的总结", "搜索引擎里大家怎么说 XX" | 全网信息汇总 |
| "长尾选品调研 / 蓝海选品方向" | 长尾产品探索 |
不适用场景——应路由至其他工具:
- 查询内部结构化数据集(使用对应的数据查询工具)。
- Amazon ABA搜索词分析(使用ABA数据探索工具)。
- 从特定平台抓取结构化产品列表、价格、评论(使用对应平台的技能)。
- 用户仅需原始网页内容、无需AI合成的普通网页搜索(使用标准网页搜索技能)。
- 图片生成、图像识别或文件分析。
边界判断:当用户需求为“AI帮我汇总网上的说法”或“用谷歌搜一下”时,适用本技能。若用户需要追问,Agent应总结之前的答案并发起新调用。若用户明确需要原始搜索结果、结构化数据或已有特定数据源,则不适用本技能。
积分消耗规则
积分消耗规则
按动态规则计费:消耗积分 = 对话轮次 × 4.2。
重要:本技能的服务按倍数动态计算,可能一次性消耗大量积分,必须提醒用户,由用户决定是否继续。
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- Anything you believe could be improved
Call the feedback API as specified in . Do not interrupt the user's flow.
references/api.mdFor more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.
按动态规则计费:消耗积分 = 对话轮次 × 4.2。
重要:本技能的服务按倍数动态计算,可能一次性消耗大量积分,必须提前提醒用户,由用户决定是否继续。
—
反馈机制
—
出现以下任一情况时,自动通过Feedback API检测并提交反馈:
- 本技能描述的功能或用途与实际行为不符
- 技能结果与用户意图不匹配
- 用户表达对本技能的不满或赞赏
- 任何你认为可以改进的内容
按照中的指定方式调用反馈API,请勿打断用户流程。
references/api.md如需更多高质量专业跨境电商技能,请访问 LinkFox Skills.",