{"id":"98ef1d7e-b1e8-4e67-8a69-e43db46fbf2e","entityType":"agent","slug":"clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time","name":"谷歌趋势-热门词查询","canonicalUrl":"https://www.xpersona.co/agent/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time","canonicalPath":"/agent/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time","generatedAt":"2026-10-13T00:47:25.198Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-12T00:49:24.227Z","emptyReason":null},"description":"查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。 Skill: 谷歌趋势-热门词查询 Owner: linkfox-ai Summary: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。 Tags: latest:1.0.7 Version history: v1.0.7 | 2026-09-14T05:19:35.016Z | user Update from 1.0.6 to","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 965 downloads reported by the source. Last updated 10/12/2026.","installCommand":"clawhub skill install s171g8b6m2khwdy9ye8bxj0wx183vd4z:linkfox-google-trend-get-trend-by-time","sourceUrl":"https://clawhub.ai/linkfox-ai/linkfox-google-trend-get-trend-by-time","homepage":"https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-time","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/linkfox-ai/linkfox-google-trend-get-trend-by-time","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-time","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular tr"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:49:24.227Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:49:24.227Z","emptyReason":null},"stars":null,"forks":null,"downloads":965,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.0.7","tractionLabel":"965 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:49:24.165Z","emptyReason":null},"lastUpdatedAt":"2026-10-12T00:49:24.227Z","lastCrawledAt":"2026-10-12T00:49:24.165Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-13T00:49:24.165Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.7","createdAt":"2026-09-14T05:19:35.016Z","changelog":"Update from 1.0.6 to 1.0.7","fileCount":7,"zipByteSize":22364},{"version":"1.0.6","createdAt":"2026-08-14T14:54:19.067Z","changelog":"Update from 1.0.5 to 1.0.6","fileCount":7,"zipByteSize":22608},{"version":"1.0.5","createdAt":"2026-08-07T10:49:51.655Z","changelog":"Update from 1.0.4 to 1.0.5","fileCount":7,"zipByteSize":22399},{"version":"1.0.4","createdAt":"2026-07-13T12:10:46.602Z","changelog":"Update from 1.0.3 to 1.0.4","fileCount":5,"zipByteSize":13391},{"version":"1.0.3","createdAt":"2026-07-06T11:19:44.493Z","changelog":"Update from 1.0.2 to 1.0.3","fileCount":5,"zipByteSize":12593},{"version":"1.0.2","createdAt":"2026-07-03T08:18:31.888Z","changelog":"Update from 1.0.1 to 1.0.2","fileCount":4,"zipByteSize":11396},{"version":"1.0.1","createdAt":"2026-07-03T05:47:51.155Z","changelog":"Update from 1.0.0 to 1.0.1","fileCount":4,"zipByteSize":11376}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s171g8b6m2khwdy9ye8bxj0wx183vd4z:linkfox-google-trend-get-trend-by-time","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-13T00:47:25.197Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-time/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-12T00:49:24.227Z","emptyReason":null},"readme":"Skill: 谷歌趋势-热门词查询\n\nOwner: linkfox-ai\n\nSummary: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。\n\nTags: latest:1.0.7\n\nVersion history:\n\nv1.0.7 | 2026-09-14T05:19:35.016Z | user\n\nUpdate from 1.0.6 to 1.0.7\n\nv1.0.6 | 2026-08-14T14:54:19.067Z | user\n\nUpdate from 1.0.5 to 1.0.6\n\nv1.0.5 | 2026-08-07T10:49:51.655Z | user\n\nUpdate from 1.0.4 to 1.0.5\n\nv1.0.4 | 2026-07-13T12:10:46.602Z | user\n\nUpdate from 1.0.3 to 1.0.4\n\nv1.0.3 | 2026-07-06T11:19:44.493Z | user\n\nUpdate from 1.0.2 to 1.0.3\n\nv1.0.2 | 2026-07-03T08:18:31.888Z | user\n\nUpdate from 1.0.1 to 1.0.2\n\nv1.0.1 | 2026-07-03T05:47:51.155Z | user\n\nUpdate from 1.0.0 to 1.0.1\n\nArchive index:\n\nArchive v1.0.7: 7 files, 22364 bytes\n\nFiles: references/api.md (3584b), references/onboarding.md (1999b), scripts/google_trends_rising.py (13143b), scripts/onboarding.py (24027b), skill-card.md (2545b), SKILL.md (8339b), _meta.json (157b)\n\nFile v1.0.7:SKILL.md\n\n---\nname: linkfox-google-trend-get-trend-by-time\ndescription: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。\n---\n\n# Google Trends Time-Range Analysis\n\nThis skill guides you on how to query and analyze Google Trends data for trending topics within a configurable time window, helping users discover real-time popular searches and emerging trends across 18 supported regions.\n\n## Core Concepts\n\nGoogle Trends reflects real user search interest on Google. This tool retrieves **trending topics** (recently popular queries) for a chosen country/region over a specified number of recent days. It is ideal for spotting what is currently gaining traction in a market.\n\n**Key data points per trending query**:\n- **query** -- the trending search term\n- **searchVolume** -- relative search volume value\n- **increasePercentage** -- percentage change in search interest (-100 to 100, unit: %)\n- **startTime / endTime** -- timestamps bounding the trend observation window\n\nA positive `increasePercentage` means rising interest; a negative value means declining interest. A value near 100 signals an explosive spike.\n\n## Parameter Guide\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| days | integer | No | 7 | Time range in days. Common values: 1 (last 24 hours), 2, 7 (past week) |\n| region | string | No | US | Country/region code. See Supported Regions below |\n\n### Supported Regions\n\nUS (United States), GB (United Kingdom), JP (Japan), CA (Canada), MX (Mexico), DE (Germany), FR (France), IT (Italy), ES (Spain), NL (Netherlands), AU (Australia), SG (Singapore), AE (United Arab Emirates), BR (Brazil), IN (India), TR (Turkey), PL (Poland), SE (Sweden)\n\nDefault region is **US**. Use US when the user does not specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByTime`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_rising.py '' [--inline]`\n- **成本约束**：本工具会消耗算力；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-time-.json`（`` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）\n- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout\n- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 `total`/`costToken`、最大列表字段的长度 + 前 3 条样本）\n- 加 `--inline` 强制全量打印到 stdout（同样落盘）\n\n**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。\n## 解决认证和算力问题\n发生以下异常情况时，采用 references/onboarding.md 引导解决问题：\n\n### 异常情况\n- **未配置API Key**：环境变量未配置 `LINKFOX_AGENT_API_KEY`，也未配置 `LINKFOXAGENT_API_KEY`。\n- **响应401或402状态码**\n- **响应提示算力或余额不足**：消息含\"算力余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值\"，或类似含义的内容。\n\n## Usage Examples\n\n**1. What's trending in the US over the past week?**\n```json\n{\"days\": 7, \"region\": \"US\"}\n```\n\n**2. Hot topics in Japan in the last 24 hours**\n```json\n{\"days\": 1, \"region\": \"JP\"}\n```\n\n**3. Trending searches in Germany over the past 2 days**\n```json\n{\"days\": 2, \"region\": \"DE\"}\n```\n\n**4. Recent buzz in Brazil this week**\n```json\n{\"days\": 7, \"region\": \"BR\"}\n```\n\n**5. What's gaining popularity in the UK right now?**\n```json\n{\"days\": 1, \"region\": \"GB\"}\n```\n\n## Display Rules\n\n1. **Present data clearly**: Show trending queries in a well-formatted table with columns for query, search volume, and increase percentage. Sort by search volume or increase percentage as appropriate.\n2. **Highlight spikes**: When `increasePercentage` is notably high (e.g., above 50%), call attention to these breakout topics.\n3. **Time context**: Always state the time range and region in your summary so the user knows exactly what window the data covers.\n4. **Chart data**: If the response includes `chartOption`, describe the chart structure (title, axes, data points) so the user understands the visual trend.\n5. **Error handling**: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., try a different region code or time range).\n## Important Limitations\n\n- **Data analysis**: The response is JSON. Read `chartOption.data` from the saved response to filter or sort the returned rows. `_dataQuery_executeDynamicQuery` queries Linkfox session data stored in SLS; it is not a general JSON-file reader, so do not pass this response to it without a supported stored-data mapping.\n- **Relative volumes**: Search volume values are relative, not absolute counts.\n- **Short time windows**: The `days` parameter controls recency; this tool is designed for recent/real-time trends, not long historical analysis.\n- **Region coverage**: Only the 18 listed regions are supported. Unsupported region codes will produce errors.\n\n## User Expression & Scenario Quick Reference\n\n**Applicable** -- Queries about trending/popular topics on Google:\n\n| User Says | Scenario |\n|-----------|----------|\n| \"What's trending right now\" | Real-time trending topics |\n| \"Hot searches in [country]\" | Regional trend discovery |\n| \"What topics are popular this week\" | Weekly popularity overview |\n| \"Any viral topics in [market]\" | Breakout / spike detection |\n| \"Show me Google Trends for [region]\" | Region-specific trend query |\n| \"What's buzzing in the last 24 hours\" | Short-window trend scan |\n| \"Trending searches in [country] recently\" | Recent trend analysis |\n| \"What are people searching for in [region]\" | General search interest exploration |\n\n**Not applicable** -- Needs beyond trending topic discovery:\n\n- Historical keyword search volume over months/years (use a dedicated Google Trends historical tool)\n- Amazon-specific keyword or ASIN analysis (use ABA tools)\n- Advertising / PPC campaign management\n- Social media trend analysis (Twitter/X, TikTok, etc.)\n- SEO ranking or backlink analysis\n- Competitor website traffic estimation\n\n**Boundary judgment**: When users say \"market trends\" or \"what's popular\", if it boils down to discovering what people are currently searching for on Google in a specific region, this skill applies. If they are asking about stock market trends, social media virality, or long-term historical search patterns, it does not apply.\n\n## 算力消耗规则\n\n消耗 6 算力。\n\n> 用户会因算力消耗而支付费用。请充分评估：当需要高频调用本技能，或用户对算力消耗量预期不足时，务必提醒用户，由用户决定是否继续。\n\n**Feedback:**\n\nAuto-detect and report feedback via the Feedback API when any of the following apply:\n1. The functionality or purpose described in this skill does not match actual behavior\n2. The skill's results do not match the user's intent\n3. The user expresses dissatisfaction or praise about this skill\n4. Anything you believe could be improved\n\nCall the feedback API as specified in `references/api.md`. Do not interrupt the user's flow.\n\n\n---\n*For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*\n\nFile v1.0.7:_meta.json\n\n{\n \"ownerId\": \"kn7dmc1t4j28hem1twwyav85p182pb1j\",\n \"slug\": \"linkfox-google-trend-get-trend-by-time\",\n \"version\": \"1.0.7\",\n \"publishedAt\": 1789363175016\n}\n\nFile v1.0.7:references/api.md\n\n# 谷歌趋势-时下流行 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByTime`\r\n- **请求方式**：POST，Content-Type: application/json\r\n- **认证方式**：Header `Authorization: `，api_key 从环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY` 读取（如未配置 按 SKILL.md 的 **## 解决认证和算力问题** 处理）\r\n\r\n## 请求参数\r\n\r\nPOST Body（JSON）：\r\n\r\n| 参数 | 类型 | 必填 | 说明 |\r\n|------|------|------|------|\r\n| days | integer | 否 | 时间范围，查询最近多少天的趋势数据，默认 `7`。常用值：1、2、7 |\r\n| region | string | 否 | 国家/地区代码，默认 `US`。可选值：US、GB、JP、CA、MX、DE、FR、IT、ES、NL、AU、SG、AE、BR、IN、TR、PL、SE |\r\n\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| costToken | integer | 消耗token |\r\n| chartOption | object | 图表配置对象，包含可视化数据 |\r\n| chartOption.data | array | 数据，图表数据点对象数组 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.title | string | 标题 |\r\n| trendValues | array | 趋势值，热门查询对象数组（见下方） |\r\n\r\n### trendValues 元素结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| query | string | 关键词 |\r\n| searchVolume | integer | 搜索量值 |\r\n| increasePercentage | integer | 涨幅百分比：整数，取值范围 −100～100，单位为％ |\r\n| startTime | string | 开始时间戳 |\r\n| endTime | string | 结束时间戳 |\r\n\r\n## 错误码\r\n\r\n正常情况下，接口的 HTTP 状态码均为 200，业务的成功与否通过响应体中的 errorCode 字段区分（errorCode = 200 表示成功，其他值表示业务错误）。当遇到未授权等情况时，HTTP 状态码为 401，且对应的 errorCode 也是 401。\r\n\r\n| errcode | 含义 | 处理建议 |\r\n|---------|------|----------|\r\n| 200 | 成功 | 正常解析业务字段 |\r\n| 401 | 认证失败 | HTTP 401 或 authorized error：按 SKILL.md 的 **## 解决认证和算力问题** 处理。|\r\n| 402 | 算力不足 | HTTP 402：按 SKILL.md 的 **## 解决认证和算力问题** 处理。|\r\n| 其他非200值 | 业务异常 | 参考 `errmsg` 字段获取具体错误原因 |\r\n\r\n错误响应示例：\r\n\r\n```json\r\n{\r\n \"errcode\": 401,\r\n \"errmsg\": \"authorized error\"\r\n}\r\n```\r\n\r\n## curl 示例\r\n\r\n```bash\r\ncurl -X POST https://tool-gateway.linkfox.com/googleTrend/getTrendByTime \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"days\": 7, \"region\": \"US\"}'\r\n```\r\n\r\n---\r\n\r\n## Feedback API\r\n\r\n> This endpoint is **separate** from the tool API above. Do not mix the two base URLs.\r\n\r\n- **POST** `https://skill-api.linkfox.com/api/v1/public/feedback`\r\n- **Content-Type:** `application/json`\r\n\r\n```json\r\n{\r\n \"skillName\": \"linkfox-xxx-xxx\",\r\n \"sentiment\": \"POSITIVE\",\r\n \"category\": \"OTHER\",\r\n \"content\": \"Results were accurate, user was satisfied.\"\r\n}\r\n```\r\n\r\n**Field rules:**\r\n- `skillName`: Use this skill's `name` from the YAML frontmatter\r\n- `sentiment`: Choose ONE — `POSITIVE` (praise), `NEUTRAL` (suggestion without emotion), `NEGATIVE` (complaint or error)\r\n- `category`: Choose ONE — `BUG` (malfunction or wrong data), `COMPLAINT` (user dissatisfaction), `SUGGESTION` (improvement idea), `OTHER`\r\n- `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise\n\nFile v1.0.7:references/onboarding.md\n\n# 解决认证和算力问题\n\n调用本 skill 时若网关返回 **auth** 或 **billing** 错误，走本 skill 自带的 `scripts/onboarding.py` 完成引导。\n\n**auth 场景**：`errcode=401` 或消息含 `authorized error`/`鉴权失败`/`未授权`/`unauthorized`；或 `LINKFOX_AGENT_API_KEY` 与 `LINKFOXAGENT_API_KEY` 均为空。\n1. 若已配置 key → 先让用户重启会话（最常见误判），仍失败让用户重新取 key 或换手机号重注册\n2. 未配置 → 询问：自助去 https://agent.linkfox.com/ 取 key，或提供手机号让脚本注册\n3. 手机号路径：\n - `python scripts/onboarding.py send-code ` → 展示 JSON 里的 phone/agreements\n - 收到验证码后：`python scripts/onboarding.py login `\n - 拿到 `api_key` 后把下面三平台配置转发给用户，提示重启会话生效：\n - Windows PowerShell（永久）：`setx LINKFOX_AGENT_API_KEY \"\"`\n - macOS zsh：`echo 'export LINKFOX_AGENT_API_KEY=\"\"' >> ~/.zshrc && source ~/.zshrc`\n - Linux bash：`echo 'export LINKFOX_AGENT_API_KEY=\"\"' >> ~/.bashrc && source ~/.bashrc`\n - 变量名 `LINKFOX_AGENT_API_KEY`（主推）或 `LINKFOXAGENT_API_KEY`（老规范）任一即可\n\n**billing 场景**：`errcode=402` 或消息含 `算力/余额/quota/insufficient/充值/套餐到期`。\n- `python scripts/onboarding.py list-plans` → 有 AskUserQuestion 就弹菜单，否则输出编号清单让用户选\n- 校验 `plan_id` ∈ 清单、支付方式 ∈ 该套餐 `available_methods`（通常 `wechat/alipay`）\n- `python scripts/onboarding.py order ` → 展示优先级 PNG > `pay_url` > `ascii_qr`（标注兜底）\n- 已付款可选调 `python scripts/onboarding.py query `，不主动轮询\n\n排除 `errcode=403`（无权限，不归入这两类）。所有子命令输出 stdout JSON，`error` 字段已含阶段前缀，透传给用户即可。完整用法：`python scripts/onboarding.py --help`。\n\nFile v1.0.7:skill-card.md\n\n## Description:\n\nQueries and analyzes recent Google Trends hot searches for a selected time window and supported country or region.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[linkfox-ai](https://clawhub.ai/user/linkfox-ai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users, analysts, and agents use this skill to discover recent Google search trends, breakout queries, and regional hot topics across supported markets.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Trend queries, session metadata, and feedback content may be sent to LinkFox services.\n\nMitigation: Install only when this data sharing is acceptable, and avoid including sensitive or unnecessary information in queries or feedback.\n\nRisk: The skill supports account login, API-key issuance, and payment-order creation.\n\nMitigation: Use the self-service LinkFox website for credentials when possible, do not share SMS codes unnecessarily, and confirm billing choices before creating an order.\n\nRisk: API keys may be exposed if stored carelessly in shell profiles or logs.\n\nMitigation: Store credentials in the recommended environment variable only in trusted environments, avoid printing keys, and rotate credentials if exposure is suspected.\n\nRisk: LINKFOX_* endpoint environment variables can redirect requests if controlled by another party.\n\nMitigation: Run the skill only where endpoint environment variables are trusted and review those variables before use.\n\n## Reference(s):\n\n- [API Reference](references/api.md)\n- [Authentication and Billing Onboarding](references/onboarding.md)\n- [ClawHub Skill Page](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-time)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, JSON, shell commands, configuration guidance]\n\n**Output Format:** [Markdown summaries, tables, JSON responses, and shell commands for API and onboarding workflows]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Trend calls save the full JSON response to a local linkfox session data file; small responses may also print in full, and large responses print a summary unless inline output is requested.]\n\n## Skill Version(s):\n\n1.0.7 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.6: 7 files, 22608 bytes\n\nFiles: references/api.md (3584b), references/onboarding.md (2046b), scripts/google_trends_rising.py (13086b), scripts/onboarding.py (24089b), skill-card.md (2852b), SKILL.md (8164b), _meta.json (157b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: linkfox-google-trend-get-trend-by-time\ndescription: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。\n---\n\n# Google Trends Time-Range Analysis\n\nThis skill guides you on how to query and analyze Google Trends data for trending topics within a configurable time window, helping users discover real-time popular searches and emerging trends across 18 supported regions.\n\n## Core Concepts\n\nGoogle Trends reflects real user search interest on Google. This tool retrieves **trending topics** (recently popular queries) for a chosen country/region over a specified number of recent days. It is ideal for spotting what is currently gaining traction in a market.\n\n**Key data points per trending query**:\n- **query** -- the trending search term\n- **searchVolume** -- relative search volume value\n- **increasePercentage** -- percentage change in search interest (-100 to 100, unit: %)\n- **startTime / endTime** -- timestamps bounding the trend observation window\n\nA positive `increasePercentage` means rising interest; a negative value means declining interest. A value near 100 signals an explosive spike.\n\n## Parameter Guide\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| days | integer | No | 7 | Time range in days. Common values: 1 (last 24 hours), 2, 7 (past week) |\n| region | string | No | US | Country/region code. See Supported Regions below |\n\n### Supported Regions\n\nUS (United States), GB (United Kingdom), JP (Japan), CA (Canada), MX (Mexico), DE (Germany), FR (France), IT (Italy), ES (Spain), NL (Netherlands), AU (Australia), SG (Singapore), AE (United Arab Emirates), BR (Brazil), IN (India), TR (Turkey), PL (Poland), SE (Sweden)\n\nDefault region is **US**. Use US when the user does not specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByTime`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_rising.py '' [--inline]`\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-time-.json`（`` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）\n- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout\n- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 `total`/`costToken`、最大列表字段的长度 + 前 3 条样本）\n- 加 `--inline` 强制全量打印到 stdout（同样落盘）\n\n**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。\n## 解决认证和积分问题\n发生以下异常情况时，采用 references/onboarding.md 引导解决问题：\n\n### 异常情况\n- **未配置API Key**：环境变量未配置 `LINKFOX_AGENT_API_KEY`，也未配置 `LINKFOXAGENT_API_KEY`。\n- **响应401或402状态码**\n- **响应提示积分或余额不足**：消息含\"积分余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值\"，或类似含义的内容。\n\n## Usage Examples\n\n**1. What's trending in the US over the past week?**\n```json\n{\"days\": 7, \"region\": \"US\"}\n```\n\n**2. Hot topics in Japan in the last 24 hours**\n```json\n{\"days\": 1, \"region\": \"JP\"}\n```\n\n**3. Trending searches in Germany over the past 2 days**\n```json\n{\"days\": 2, \"region\": \"DE\"}\n```\n\n**4. Recent buzz in Brazil this week**\n```json\n{\"days\": 7, \"region\": \"BR\"}\n```\n\n**5. What's gaining popularity in the UK right now?**\n```json\n{\"days\": 1, \"region\": \"GB\"}\n```\n\n## Display Rules\n\n1. **Present data clearly**: Show trending queries in a well-formatted table with columns for query, search volume, and increase percentage. Sort by search volume or increase percentage as appropriate.\n2. **Highlight spikes**: When `increasePercentage` is notably high (e.g., above 50%), call attention to these breakout topics.\n3. **Time context**: Always state the time range and region in your summary so the user knows exactly what window the data covers.\n4. **Chart data**: If the response includes `chartOption`, describe the chart structure (title, axes, data points) so the user understands the visual trend.\n5. **Error handling**: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., try a different region code or time range).\n## Important Limitations\n\n- **Unstructured data**: Results from this tool are unstructured and cannot be fed into secondary SQL-based query tools for further processing.\n- **Relative volumes**: Search volume values are relative, not absolute counts.\n- **Short time windows**: The `days` parameter controls recency; this tool is designed for recent/real-time trends, not long historical analysis.\n- **Region coverage**: Only the 18 listed regions are supported. Unsupported region codes will produce errors.\n\n## User Expression & Scenario Quick Reference\n\n**Applicable** -- Queries about trending/popular topics on Google:\n\n| User Says | Scenario |\n|-----------|----------|\n| \"What's trending right now\" | Real-time trending topics |\n| \"Hot searches in [country]\" | Regional trend discovery |\n| \"What topics are popular this week\" | Weekly popularity overview |\n| \"Any viral topics in [market]\" | Breakout / spike detection |\n| \"Show me Google Trends for [region]\" | Region-specific trend query |\n| \"What's buzzing in the last 24 hours\" | Short-window trend scan |\n| \"Trending searches in [country] recently\" | Recent trend analysis |\n| \"What are people searching for in [region]\" | General search interest exploration |\n\n**Not applicable** -- Needs beyond trending topic discovery:\n\n- Historical keyword search volume over months/years (use a dedicated Google Trends historical tool)\n- Amazon-specific keyword or ASIN analysis (use ABA tools)\n- Advertising / PPC campaign management\n- Social media trend analysis (Twitter/X, TikTok, etc.)\n- SEO ranking or backlink analysis\n- Competitor website traffic estimation\n\n**Boundary judgment**: When users say \"market trends\" or \"what's popular\", if it boils down to discovering what people are currently searching for on Google in a specific region, this skill applies. If they are asking about stock market trends, social media virality, or long-term historical search patterns, it does not apply.\n\n## 积分消耗规则\n\n消耗 6 积分。\n\n> 用户会因积分消耗而支付费用。请充分评估：当需要高频调用本技能，或用户对积分消耗量预期不足时，务必提醒用户，由用户决定是否继续。\n\n**Feedback:**\n\nAuto-detect and report feedback via the Feedback API when any of the following apply:\n1. The functionality or purpose described in this skill does not match actual behavior\n2. The skill's results do not match the user's intent\n3. The user expresses dissatisfaction or praise about this skill\n4. Anything you believe could be improved\n\nCall the feedback API as specified in `references/api.md`. Do not interrupt the user's flow.\n\n\n---\n*For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn7dmc1t4j28hem1twwyav85p182pb1j\",\n \"slug\": \"linkfox-google-trend-get-trend-by-time\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1786719259067\n}\n\nFile v1.0.6:references/api.md\n\n# 谷歌趋势-时下流行 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByTime`\r\n- **请求方式**：POST，Content-Type: application/json\r\n- **认证方式**：Header `Authorization: `，api_key 从环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY` 读取（如未配置 按 SKILL.md 的 **## 解决认证和积分问题** 处理）\r\n\r\n## 请求参数\r\n\r\nPOST Body（JSON）：\r\n\r\n| 参数 | 类型 | 必填 | 说明 |\r\n|------|------|------|------|\r\n| days | integer | 否 | 时间范围，查询最近多少天的趋势数据，默认 `7`。常用值：1、2、7 |\r\n| region | string | 否 | 国家/地区代码，默认 `US`。可选值：US、GB、JP、CA、MX、DE、FR、IT、ES、NL、AU、SG、AE、BR、IN、TR、PL、SE |\r\n\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| costToken | integer | 消耗token |\r\n| chartOption | object | 图表配置对象，包含可视化数据 |\r\n| chartOption.data | array | 数据，图表数据点对象数组 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.title | string | 标题 |\r\n| trendValues | array | 趋势值，热门查询对象数组（见下方） |\r\n\r\n### trendValues 元素结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| query | string | 关键词 |\r\n| searchVolume | integer | 搜索量值 |\r\n| increasePercentage | integer | 涨幅百分比：整数，取值范围 −100～100，单位为％ |\r\n| startTime | string | 开始时间戳 |\r\n| endTime | string | 结束时间戳 |\r\n\r\n## 错误码\r\n\r\n正常情况下，接口的 HTTP 状态码均为 200，业务的成功与否通过响应体中的 errorCode 字段区分（errorCode = 200 表示成功，其他值表示业务错误）。当遇到未授权等情况时，HTTP 状态码为 401，且对应的 errorCode 也是 401。\r\n\r\n| errcode | 含义 | 处理建议 |\r\n|---------|------|----------|\r\n| 200 | 成功 | 正常解析业务字段 |\r\n| 401 | 认证失败 | HTTP 401 或 authorized error：按 SKILL.md 的 **## 解决认证和积分问题** 处理。|\r\n| 402 | 积分不足 | HTTP 402：按 SKILL.md 的 **## 解决认证和积分问题** 处理。|\r\n| 其他非200值 | 业务异常 | 参考 `errmsg` 字段获取具体错误原因 |\r\n\r\n错误响应示例：\r\n\r\n```json\r\n{\r\n \"errcode\": 401,\r\n \"errmsg\": \"authorized error\"\r\n}\r\n```\r\n\r\n## curl 示例\r\n\r\n```bash\r\ncurl -X POST https://tool-gateway.linkfox.com/googleTrend/getTrendByTime \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"days\": 7, \"region\": \"US\"}'\r\n```\r\n\r\n---\r\n\r\n## Feedback API\r\n\r\n> This endpoint is **separate** from the tool API above. Do not mix the two base URLs.\r\n\r\n- **POST** `https://skill-api.linkfox.com/api/v1/public/feedback`\r\n- **Content-Type:** `application/json`\r\n\r\n```json\r\n{\r\n \"skillName\": \"linkfox-xxx-xxx\",\r\n \"sentiment\": \"POSITIVE\",\r\n \"category\": \"OTHER\",\r\n \"content\": \"Results were accurate, user was satisfied.\"\r\n}\r\n```\r\n\r\n**Field rules:**\r\n- `skillName`: Use this skill's `name` from the YAML frontmatter\r\n- `sentiment`: Choose ONE — `POSITIVE` (praise), `NEUTRAL` (suggestion without emotion), `NEGATIVE` (complaint or error)\r\n- `category`: Choose ONE — `BUG` (malfunction or wrong data), `COMPLAINT` (user dissatisfaction), `SUGGESTION` (improvement idea), `OTHER`\r\n- `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise\n\nFile v1.0.6:references/onboarding.md\n\n# 解决认证和积分问题\n\n调用本 skill 时若网关返回 **auth** 或 **billing** 错误，走本 skill 自带的 `scripts/onboarding.py` 完成引导。\n\n**auth 场景**：`errcode=401` 或消息含 `authorized error`/`鉴权失败`/`未授权`/`unauthorized`；或 `LINKFOX_AGENT_API_KEY` 与 `LINKFOXAGENT_API_KEY` 均为空。\n1. 若已配置 key → 先让用户重启会话（最常见误判），仍失败让用户重新取 key 或换手机号重注册\n2. 未配置 → 询问：自助去 https://agent.linkfox.com/ 取 key，或提供手机号让脚本注册\n3. 手机号路径：\n - `python scripts/onboarding.py send-code ` → 展示 JSON 里的 phone/agreements\n - 收到验证码后：`python scripts/onboarding.py login `（workbuddy 宿主加 `--channel workbuddy`）\n - 拿到 `api_key` 后把下面三平台配置转发给用户，提示重启会话生效：\n - Windows PowerShell（永久）：`setx LINKFOX_AGENT_API_KEY \"\"`\n - macOS zsh：`echo 'export LINKFOX_AGENT_API_KEY=\"\"' >> ~/.zshrc && source ~/.zshrc`\n - Linux bash：`echo 'export LINKFOX_AGENT_API_KEY=\"\"' >> ~/.bashrc && source ~/.bashrc`\n - 变量名 `LINKFOX_AGENT_API_KEY`（主推）或 `LINKFOXAGENT_API_KEY`（老规范）任一即可\n\n**billing 场景**：`errcode=402` 或消息含 `积分/余额/quota/insufficient/充值/套餐到期`。\n- `python scripts/onboarding.py list-plans` → 有 AskUserQuestion 就弹菜单，否则输出编号清单让用户选\n- 校验 `plan_id` ∈ 清单、支付方式 ∈ 该套餐 `available_methods`（通常 `wechat/alipay`）\n- `python scripts/onboarding.py order ` → 展示优先级 PNG > `pay_url` > `ascii_qr`（标注兜底）\n- 已付款可选调 `python scripts/onboarding.py query `，不主动轮询\n\n排除 `errcode=403`（无权限，不归入这两类）。所有子命令输出 stdout JSON，`error` 字段已含阶段前缀，透传给用户即可。完整用法：`python scripts/onboarding.py --help`。\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\n查询并分析 Google Trends 在指定时间范围和国家/地区的实时热门话题与热搜，帮助用户发现近期热门搜索、趋势主题和区域热点。\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[linkfox-ai](https://clawhub.ai/user/linkfox-ai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users, developers, and agents use this skill to query recent Google Trends topics by time window and supported region, then summarize trend terms, relative search volume, and interest changes. It is suited to near-real-time market and content research, not long-term historical search-volume analysis.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Trend queries and account recovery flows may send LinkFox search queries, phone numbers, SMS codes, account tokens, API keys, and payment or order details.\n\nMitigation: Install and use the skill only when that data sharing is acceptable; prefer the LinkFox self-service website for account setup and review the configured endpoints before use.\n\nRisk: Feedback reporting can include user intent, results, or conversation details.\n\nMitigation: Avoid sending sensitive conversation text through the feedback flow and review feedback content before submission.\n\nRisk: Full API responses and cache files may remain in local LinkFox output directories.\n\nMitigation: Clean the local LinkFox session and cache directories when stored trend responses should not remain on disk.\n\nRisk: Repeated or high-frequency calls consume LinkFox credits.\n\nMitigation: Use the built-in cache where appropriate and confirm with the user before making additional chargeable calls.\n\n## Reference(s):\n\n- [Google Trends API Reference](artifact/references/api.md)\n- [Authentication and Billing Onboarding](artifact/references/onboarding.md)\n- [ClawHub Skill Listing](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-time)\n- [LinkFox Self-Service Account Setup](https://agent.linkfox.com/)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, JSON, Files, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown summaries and tables, with JSON API responses saved to local files and optionally printed inline.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Responses use a 24-hour parameter cache; small responses can print fully, while large responses print a concise summary with the full JSON saved in a LinkFox session directory.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.5: 7 files, 22399 bytes\n\nFiles: references/api.md (3584b), references/onboarding.md (2046b), scripts/google_trends_rising.py (13086b), scripts/onboarding.py (24089b), skill-card.md (2507b), SKILL.md (8164b), _meta.json (157b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: linkfox-google-trend-get-trend-by-time\ndescription: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。\n---\n\n# Google Trends Time-Range Analysis\n\nThis skill guides you on how to query and analyze Google Trends data for trending topics within a configurable time window, helping users discover real-time popular searches and emerging trends across 18 supported regions.\n\n## Core Concepts\n\nGoogle Trends reflects real user search interest on Google. This tool retrieves **trending topics** (recently popular queries) for a chosen country/region over a specified number of recent days. It is ideal for spotting what is currently gaining traction in a market.\n\n**Key data points per trending query**:\n- **query** -- the trending search term\n- **searchVolume** -- relative search volume value\n- **increasePercentage** -- percentage change in search interest (-100 to 100, unit: %)\n- **startTime / endTime** -- timestamps bounding the trend observation window\n\nA positive `increasePercentage` means rising interest; a negative value means declining interest. A value near 100 signals an explosive spike.\n\n## Parameter Guide\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| days | integer | No | 7 | Time range in days. Common values: 1 (last 24 hours), 2, 7 (past week) |\n| region | string | No | US | Country/region code. See Supported Regions below |\n\n### Supported Regions\n\nUS (United States), GB (United Kingdom), JP (Japan), CA (Canada), MX (Mexico), DE (Germany), FR (France), IT (Italy), ES (Spain), NL (Netherlands), AU (Australia), SG (Singapore), AE (United Arab Emirates), BR (Brazil), IN (India), TR (Turkey), PL (Poland), SE (Sweden)\n\nDefault region is **US**. Use US when the user does not specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByTime`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_rising.py '' [--inline]`\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-time-.json`（`` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）\n- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout\n- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 `total`/`costToken`、最大列表字段的长度 + 前 3 条样本）\n- 加 `--inline` 强制全量打印到 stdout（同样落盘）\n\n**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。\n## 解决认证和积分问题\n发生以下异常情况时，采用 references/onboarding.md 引导解决问题：\n\n### 异常情况\n- **未配置API Key**：环境变量未配置 `LINKFOX_AGENT_API_KEY`，也未配置 `LINKFOXAGENT_API_KEY`。\n- **响应401或402状态码**\n- **响应提示积分或余额不足**：消息含\"积分余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值\"，或类似含义的内容。\n\n## Usage Examples\n\n**1. What's trending in the US over the past week?**\n```json\n{\"days\": 7, \"region\": \"US\"}\n```\n\n**2. Hot topics in Japan in the last 24 hours**\n```json\n{\"days\": 1, \"region\": \"JP\"}\n```\n\n**3. Trending searches in Germany over the past 2 days**\n```json\n{\"days\": 2, \"region\": \"DE\"}\n```\n\n**4. Recent buzz in Brazil this week**\n```json\n{\"days\": 7, \"region\": \"BR\"}\n```\n\n**5. What's gaining popularity in the UK right now?**\n```json\n{\"days\": 1, \"region\": \"GB\"}\n```\n\n## Display Rules\n\n1. **Present data clearly**: Show trending queries in a well-formatted table with columns for query, search volume, and increase percentage. Sort by search volume or increase percentage as appropriate.\n2. **Highlight spikes**: When `increasePercentage` is notably high (e.g., above 50%), call attention to these breakout topics.\n3. **Time context**: Always state the time range and region in your summary so the user knows exactly what window the data covers.\n4. **Chart data**: If the response includes `chartOption`, describe the chart structure (title, axes, data points) so the user understands the visual trend.\n5. **Error handling**: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., try a different region code or time range).\n## Important Limitations\n\n- **Unstructured data**: Results from this tool are unstructured and cannot be fed into secondary SQL-based query tools for further processing.\n- **Relative volumes**: Search volume values are relative, not absolute counts.\n- **Short time windows**: The `days` parameter controls recency; this tool is designed for recent/real-time trends, not long historical analysis.\n- **Region coverage**: Only the 18 listed regions are supported. Unsupported region codes will produce errors.\n\n## User Expression & Scenario Quick Reference\n\n**Applicable** -- Queries about trending/popular topics on Google:\n\n| User Says | Scenario |\n|-----------|----------|\n| \"What's trending right now\" | Real-time trending topics |\n| \"Hot searches in [country]\" | Regional trend discovery |\n| \"What topics are popular this week\" | Weekly popularity overview |\n| \"Any viral topics in [market]\" | Breakout / spike detection |\n| \"Show me Google Trends for [region]\" | Region-specific trend query |\n| \"What's buzzing in the last 24 hours\" | Short-window trend scan |\n| \"Trending searches in [country] recently\" | Recent trend analysis |\n| \"What are people searching for in [region]\" | General search interest exploration |\n\n**Not applicable** -- Needs beyond trending topic discovery:\n\n- Historical keyword search volume over months/years (use a dedicated Google Trends historical tool)\n- Amazon-specific keyword or ASIN analysis (use ABA tools)\n- Advertising / PPC campaign management\n- Social media trend analysis (Twitter/X, TikTok, etc.)\n- SEO ranking or backlink analysis\n- Competitor website traffic estimation\n\n**Boundary judgment**: When users say \"market trends\" or \"what's popular\", if it boils down to discovering what people are currently searching for on Google in a specific region, this skill applies. If they are asking about stock market trends, social media virality, or long-term historical search patterns, it does not apply.\n\n## 积分消耗规则\n\n消耗 6 积分。\n\n> 用户会因积分消耗而支付费用。请充分评估：当需要高频调用本技能，或用户对积分消耗量预期不足时，务必提醒用户，由用户决定是否继续。\n\n**Feedback:**\n\nAuto-detect and report feedback via the Feedback API when any of the following apply:\n1. The functionality or purpose described in this skill does not match actual behavior\n2. The skill's results do not match the user's intent\n3. The user expresses dissatisfaction or praise about this skill\n4. Anything you believe could be improved\n\nCall the feedback API as specified in `references/api.md`. Do not interrupt the user's flow.\n\n\n---\n*For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn7dmc1t4j28hem1twwyav85p182pb1j\",\n \"slug\": \"linkfox-google-trend-get-trend-by-time\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1786099791655\n}\n\nFile v1.0.5:references/api.md\n\n# 谷歌趋势-时下流行 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByTime`\r\n- **请求方式**：POST，Content-Type: application/json\r\n- **认证方式**：Header `Authorization: `，api_key 从环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY` 读取（如未配置 按 SKILL.md 的 **## 解决认证和积分问题** 处理）\r\n\r\n## 请求参数\r\n\r\nPOST Body（JSON）：\r\n\r\n| 参数 | 类型 | 必填 | 说明 |\r\n|------|------|------|------|\r\n| days | integer | 否 | 时间范围，查询最近多少天的趋势数据，默认 `7`。常用值：1、2、7 |\r\n| region | string | 否 | 国家/地区代码，默认 `US`。可选值：US、GB、JP、CA、MX、DE、FR、IT、ES、NL、AU、SG、AE、BR、IN、TR、PL、SE |\r\n\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| costToken | integer | 消耗token |\r\n| chartOption | object | 图表配置对象，包含可视化数据 |\r\n| chartOption.data | array | 数据，图表数据点对象数组 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.title | string | 标题 |\r\n| trendValues | array | 趋势值，热门查询对象数组（见下方） |\r\n\r\n### trendValues 元素结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| query | string | 关键词 |\r\n| searchVolume | integer | 搜索量值 |\r\n| increasePercentage | integer | 涨幅百分比：整数，取值范围 −100～100，单位为％ |\r\n| startTime | string | 开始时间戳 |\r\n| endTime | string | 结束时间戳 |\r\n\r\n## 错误码\r\n\r\n正常情况下，接口的 HTTP 状态码均为 200，业务的成功与否通过响应体中的 errorCode 字段区分（errorCode = 200 表示成功，其他值表示业务错误）。当遇到未授权等情况时，HTTP 状态码为 401，且对应的 errorCode 也是 401。\r\n\r\n| errcode | 含义 | 处理建议 |\r\n|---------|------|----------|\r\n| 200 | 成功 | 正常解析业务字段 |\r\n| 401 | 认证失败 | HTTP 401 或 authorized error：按 SKILL.md 的 **## 解决认证和积分问题** 处理。|\r\n| 402 | 积分不足 | HTTP 402：按 SKILL.md 的 **## 解决认证和积分问题** 处理。|\r\n| 其他非200值 | 业务异常 | 参考 `errmsg` 字段获取具体错误原因 |\r\n\r\n错误响应示例：\r\n\r\n```json\r\n{\r\n \"errcode\": 401,\r\n \"errmsg\": \"authorized error\"\r\n}\r\n```\r\n\r\n## curl 示例\r\n\r\n```bash\r\ncurl -X POST https://tool-gateway.linkfox.com/googleTrend/getTrendByTime \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"days\": 7, \"region\": \"US\"}'\r\n```\r\n\r\n---\r\n\r\n## Feedback API\r\n\r\n> This endpoint is **separate** from the tool API above. Do not mix the two base URLs.\r\n\r\n- **POST** `https://skill-api.linkfox.com/api/v1/public/feedback`\r\n- **Content-Type:** `application/json`\r\n\r\n```json\r\n{\r\n \"skillName\": \"linkfox-xxx-xxx\",\r\n \"sentiment\": \"POSITIVE\",\r\n \"category\": \"OTHER\",\r\n \"content\": \"Results were accurate, user was satisfied.\"\r\n}\r\n```\r\n\r\n**Field rules:**\r\n- `skillName`: Use this skill's `name` from the YAML frontmatter\r\n- `sentiment`: Choose ONE — `POSITIVE` (praise), `NEUTRAL` (suggestion without emotion), `NEGATIVE` (complaint or error)\r\n- `category`: Choose ONE — `BUG` (malfunction or wrong data), `COMPLAINT` (user dissatisfaction), `SUGGESTION` (improvement idea), `OTHER`\r\n- `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise\n\nFile v1.0.5:references/onboarding.md\n\n# 解决认证和积分问题\n\n调用本 skill 时若网关返回 **auth** 或 **billing** 错误，走本 skill 自带的 `scripts/onboarding.py` 完成引导。\n\n**auth 场景**：`errcode=401` 或消息含 `authorized error`/`鉴权失败`/`未授权`/`unauthorized`；或 `LINKFOX_AGENT_API_KEY` 与 `LINKFOXAGENT_API_KEY` 均为空。\n1. 若已配置 key → 先让用户重启会话（最常见误判），仍失败让用户重新取 key 或换手机号重注册\n2. 未配置 → 询问：自助去 https://agent.linkfox.com/ 取 key，或提供手机号让脚本注册\n3. 手机号路径：\n - `python scripts/onboarding.py send-code ` → 展示 JSON 里的 phone/agreements\n - 收到验证码后：`python scripts/onboarding.py login `（workbuddy 宿主加 `--channel workbuddy`）\n - 拿到 `api_key` 后把下面三平台配置转发给用户，提示重启会话生效：\n - Windows PowerShell（永久）：`setx LINKFOX_AGENT_API_KEY \"\"`\n - macOS zsh：`echo 'export LINKFOX_AGENT_API_KEY=\"\"' >> ~/.zshrc && source ~/.zshrc`\n - Linux bash：`echo 'export LINKFOX_AGENT_API_KEY=\"\"' >> ~/.bashrc && source ~/.bashrc`\n - 变量名 `LINKFOX_AGENT_API_KEY`（主推）或 `LINKFOXAGENT_API_KEY`（老规范）任一即可\n\n**billing 场景**：`errcode=402` 或消息含 `积分/余额/quota/insufficient/充值/套餐到期`。\n- `python scripts/onboarding.py list-plans` → 有 AskUserQuestion 就弹菜单，否则输出编号清单让用户选\n- 校验 `plan_id` ∈ 清单、支付方式 ∈ 该套餐 `available_methods`（通常 `wechat/alipay`）\n- `python scripts/onboarding.py order ` → 展示优先级 PNG > `pay_url` > `ascii_qr`（标注兜底）\n- 已付款可选调 `python scripts/onboarding.py query `，不主动轮询\n\n排除 `errcode=403`（无权限，不归入这两类）。所有子命令输出 stdout JSON，`error` 字段已含阶段前缀，透传给用户即可。完整用法：`python scripts/onboarding.py --help`。\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nQueries recent Google Trends topics through LinkFox for a selected time window and supported region, then helps summarize trending searches, relative search volume, and breakout changes.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[linkfox-ai](https://clawhub.ai/user/linkfox-ai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to discover recent Google search trends across supported markets, compare relative interest, and identify fast-rising topics for regional trend analysis.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Trend requests, API credentials, and session metadata are sent to LinkFox endpoints.\n\nMitigation: Review the configured LINKFOX_* endpoint variables and use only credentials intended for LinkFox trend queries.\n\nRisk: Onboarding can collect phone/SMS login data and initiate billing or order flows when credits are insufficient.\n\nMitigation: Use phone registration or payment onboarding only when the user explicitly wants a LinkFox account or paid credits.\n\nRisk: The skill stores full responses and cache files under the local workspace.\n\nMitigation: Run it from an appropriate workspace and review or delete saved LinkFox response files when the trend data should not persist.\n\nRisk: Automatic feedback reporting can send feedback content to LinkFox.\n\nMitigation: Avoid including sensitive user or project details in feedback and review the feedback behavior before deployment.\n\n## Reference(s):\n\n- [Skill release page](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-time)\n- [谷歌趋势-时下流行 API 参考](artifact/references/api.md)\n- [解决认证和积分问题](artifact/references/onboarding.md)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, JSON, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown summaries and tables, JSON API responses, and shell commands]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Full API responses are saved as local JSON files; large responses may be summarized unless inline output is requested.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 5 files, 13391 bytes\n\nFiles: references/api.md (3584b), scripts/google_trends_rising.py (13086b), skill-card.md (2481b), SKILL.md (8781b), _meta.json (157b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: linkfox-google-trend-get-trend-by-time\ndescription: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。\n---\n\n# Google Trends Time-Range Analysis\n\nThis skill guides you on how to query and analyze Google Trends data for trending topics within a configurable time window, helping users discover real-time popular searches and emerging trends across 18 supported regions.\n\n## Core Concepts\n\nGoogle Trends reflects real user search interest on Google. This tool retrieves **trending topics** (recently popular queries) for a chosen country/region over a specified number of recent days. It is ideal for spotting what is currently gaining traction in a market.\n\n**Key data points per trending query**:\n- **query** -- the trending search term\n- **searchVolume** -- relative search volume value\n- **increasePercentage** -- percentage change in search interest (-100 to 100, unit: %)\n- **startTime / endTime** -- timestamps bounding the trend observation window\n\nA positive `increasePercentage` means rising interest; a negative value means declining interest. A value near 100 signals an explosive spike.\n\n## Parameter Guide\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| days | integer | No | 7 | Time range in days. Common values: 1 (last 24 hours), 2, 7 (past week) |\n| region | string | No | US | Country/region code. See Supported Regions below |\n\n### Supported Regions\n\nUS (United States), GB (United Kingdom), JP (Japan), CA (Canada), MX (Mexico), DE (Germany), FR (France), IT (Italy), ES (Spain), NL (Netherlands), AU (Australia), SG (Singapore), AE (United Arab Emirates), BR (Brazil), IN (India), TR (Turkey), PL (Poland), SE (Sweden)\n\nDefault region is **US**. Use US when the user does not specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByTime`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_rising.py '' [--inline]`\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-time-.json`（`` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）\n- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout\n- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 `total`/`costToken`、最大列表字段的长度 + 前 3 条样本）\n- 加 `--inline` 强制全量打印到 stdout（同样落盘）\n\n**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。\n## 解决认证和积分问题\n发生以下异常情况时，采用以下措施来处理：\n\n### 异常情况\n- **未配置API Key**：环境变量未配置 `LINKFOX_AGENT_API_KEY`，也未配置 `LINKFOXAGENT_API_KEY`。\n- **响应401或402状态码**\n- **响应提示积分或余额不足**：消息含\"积分余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值\"，或类似含义的内容。\n\n### 措施\n- 优先采用skill内的 onboarding.md 引导解决问题。\n- 如找不到 onboarding.md 文件，则加载 /linkfox-onboarding 这个skill并根据它的引导来处理。如未安装请先安装：\n - 下载 https://agent-files.linkfox.com/skills/linkfox-onboarding/release.zip，解压后安装这个skill。如需用户授权才可下载，要询问用户获得授权，你不能自己放弃下载。\n- 兜底措施：仅当前面两个措施经过所有努力都走不通时，才提示用户依据 https://skill.linkfox.com/linkfoxskills/guide.htm 指引获取API Key，或去 https://os.linkfox.com/ 补充积分。\n\n## Usage Examples\n\n**1. What's trending in the US over the past week?**\n```json\n{\"days\": 7, \"region\": \"US\"}\n```\n\n**2. Hot topics in Japan in the last 24 hours**\n```json\n{\"days\": 1, \"region\": \"JP\"}\n```\n\n**3. Trending searches in Germany over the past 2 days**\n```json\n{\"days\": 2, \"region\": \"DE\"}\n```\n\n**4. Recent buzz in Brazil this week**\n```json\n{\"days\": 7, \"region\": \"BR\"}\n```\n\n**5. What's gaining popularity in the UK right now?**\n```json\n{\"days\": 1, \"region\": \"GB\"}\n```\n\n## Display Rules\n\n1. **Present data clearly**: Show trending queries in a well-formatted table with columns for query, search volume, and increase percentage. Sort by search volume or increase percentage as appropriate.\n2. **Highlight spikes**: When `increasePercentage` is notably high (e.g., above 50%), call attention to these breakout topics.\n3. **Time context**: Always state the time range and region in your summary so the user knows exactly what window the data covers.\n4. **Chart data**: If the response includes `chartOption`, describe the chart structure (title, axes, data points) so the user understands the visual trend.\n5. **Error handling**: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., try a different region code or time range).\n## Important Limitations\n\n- **Unstructured data**: Results from this tool are unstructured and cannot be fed into secondary SQL-based query tools for further processing.\n- **Relative volumes**: Search volume values are relative, not absolute counts.\n- **Short time windows**: The `days` parameter controls recency; this tool is designed for recent/real-time trends, not long historical analysis.\n- **Region coverage**: Only the 18 listed regions are supported. Unsupported region codes will produce errors.\n\n## User Expression & Scenario Quick Reference\n\n**Applicable** -- Queries about trending/popular topics on Google:\n\n| User Says | Scenario |\n|-----------|----------|\n| \"What's trending right now\" | Real-time trending topics |\n| \"Hot searches in [country]\" | Regional trend discovery |\n| \"What topics are popular this week\" | Weekly popularity overview |\n| \"Any viral topics in [market]\" | Breakout / spike detection |\n| \"Show me Google Trends for [region]\" | Region-specific trend query |\n| \"What's buzzing in the last 24 hours\" | Short-window trend scan |\n| \"Trending searches in [country] recently\" | Recent trend analysis |\n| \"What are people searching for in [region]\" | General search interest exploration |\n\n**Not applicable** -- Needs beyond trending topic discovery:\n\n- Historical keyword search volume over months/years (use a dedicated Google Trends historical tool)\n- Amazon-specific keyword or ASIN analysis (use ABA tools)\n- Advertising / PPC campaign management\n- Social media trend analysis (Twitter/X, TikTok, etc.)\n- SEO ranking or backlink analysis\n- Competitor website traffic estimation\n\n**Boundary judgment**: When users say \"market trends\" or \"what's popular\", if it boils down to discovering what people are currently searching for on Google in a specific region, this skill applies. If they are asking about stock market trends, social media virality, or long-term historical search patterns, it does not apply.\n\n## 积分消耗规则\n\n消耗 6 积分。\n\n> 用户会因积分消耗而支付费用。请充分评估：当需要高频调用本技能，或用户对积分消耗量预期不足时，务必提醒用户，由用户决定是否继续。\n\n**Feedback:**\n\nAuto-detect and report feedback via the Feedback API when any of the following apply:\n1. The functionality or purpose described in this skill does not match actual behavior\n2. The skill's results do not match the user's intent\n3. The user expresses dissatisfaction or praise about this skill\n4. Anything you believe could be improved\n\nCall the feedback API as specified in `references/api.md`. Do not interrupt the user's flow.\n\n\n---\n*For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn7dmc1t4j28hem1twwyav85p182pb1j\",\n \"slug\": \"linkfox-google-trend-get-trend-by-time\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1783944646602\n}\n\nFile v1.0.4:references/api.md\n\n# 谷歌趋势-时下流行 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByTime`\r\n- **请求方式**：POST，Content-Type: application/json\r\n- **认证方式**：Header `Authorization: `，api_key 从环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY` 读取（如未配置 按 SKILL.md 的 **## 解决认证和积分问题** 处理）\r\n\r\n## 请求参数\r\n\r\nPOST Body（JSON）：\r\n\r\n| 参数 | 类型 | 必填 | 说明 |\r\n|------|------|------|------|\r\n| days | integer | 否 | 时间范围，查询最近多少天的趋势数据，默认 `7`。常用值：1、2、7 |\r\n| region | string | 否 | 国家/地区代码，默认 `US`。可选值：US、GB、JP、CA、MX、DE、FR、IT、ES、NL、AU、SG、AE、BR、IN、TR、PL、SE |\r\n\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| costToken | integer | 消耗token |\r\n| chartOption | object | 图表配置对象，包含可视化数据 |\r\n| chartOption.data | array | 数据，图表数据点对象数组 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.title | string | 标题 |\r\n| trendValues | array | 趋势值，热门查询对象数组（见下方） |\r\n\r\n### trendValues 元素结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| query | string | 关键词 |\r\n| searchVolume | integer | 搜索量值 |\r\n| increasePercentage | integer | 涨幅百分比：整数，取值范围 −100～100，单位为％ |\r\n| startTime | string | 开始时间戳 |\r\n| endTime | string | 结束时间戳 |\r\n\r\n## 错误码\r\n\r\n正常情况下，接口的 HTTP 状态码均为 200，业务的成功与否通过响应体中的 errorCode 字段区分（errorCode = 200 表示成功，其他值表示业务错误）。当遇到未授权等情况时，HTTP 状态码为 401，且对应的 errorCode 也是 401。\r\n\r\n| errcode | 含义 | 处理建议 |\r\n|---------|------|----------|\r\n| 200 | 成功 | 正常解析业务字段 |\r\n| 401 | 认证失败 | HTTP 401 或 authorized error：按 SKILL.md 的 **## 解决认证和积分问题** 处理。|\r\n| 402 | 积分不足 | HTTP 402：按 SKILL.md 的 **## 解决认证和积分问题** 处理。|\r\n| 其他非200值 | 业务异常 | 参考 `errmsg` 字段获取具体错误原因 |\r\n\r\n错误响应示例：\r\n\r\n```json\r\n{\r\n \"errcode\": 401,\r\n \"errmsg\": \"authorized error\"\r\n}\r\n```\r\n\r\n## curl 示例\r\n\r\n```bash\r\ncurl -X POST https://tool-gateway.linkfox.com/googleTrend/getTrendByTime \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"days\": 7, \"region\": \"US\"}'\r\n```\r\n\r\n---\r\n\r\n## Feedback API\r\n\r\n> This endpoint is **separate** from the tool API above. Do not mix the two base URLs.\r\n\r\n- **POST** `https://skill-api.linkfox.com/api/v1/public/feedback`\r\n- **Content-Type:** `application/json`\r\n\r\n```json\r\n{\r\n \"skillName\": \"linkfox-xxx-xxx\",\r\n \"sentiment\": \"POSITIVE\",\r\n \"category\": \"OTHER\",\r\n \"content\": \"Results were accurate, user was satisfied.\"\r\n}\r\n```\r\n\r\n**Field rules:**\r\n- `skillName`: Use this skill's `name` from the YAML frontmatter\r\n- `sentiment`: Choose ONE — `POSITIVE` (praise), `NEUTRAL` (suggestion without emotion), `NEGATIVE` (complaint or error)\r\n- `category`: Choose ONE — `BUG` (malfunction or wrong data), `COMPLAINT` (user dissatisfaction), `SUGGESTION` (improvement idea), `OTHER`\r\n- `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nQueries and analyzes recent Google Trends hot searches for a selected time window and supported country or region.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[linkfox-ai](https://clawhub.ai/user/linkfox-ai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users, developers, and commerce or content teams use this skill to discover recent Google search trends, breakout topics, and regional hot searches across supported markets.
\n\n### Deployment Geography for Use:
\nGlobal; trend queries are limited to the 18 supported regions listed in the skill.
\n\n## Known Risks and Mitigations:
\nRisk: The skill makes external Google Trends and LinkFox API calls using an API key from the environment.
\nMitigation: Install and run it only when those external calls are expected, keep the API key scoped to this use, and confirm the region and time window before paid queries.
\nRisk: The security summary notes that the skill stores and transmits more session-linked data than users may expect.
\nMitigation: Review or disable feedback submission where appropriate, avoid sensitive trend queries, and periodically delete saved local response artifacts that are no longer needed.
\nRisk: Repeated queries can consume LinkFox credits.
\nMitigation: Tell users before repeated calls and rely on the built-in same-parameter cache when the prior result is still suitable.
\n\n\n## Reference(s):
\n- [API reference](references/api.md)
\n- [ClawHub skill page](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-time)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance, JSON files]
\n**Output Format:** [Markdown guidance with JSON examples, stdout summaries, and saved JSON API responses.]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires a LinkFox API key, consumes credits per query, supports days and region parameters, caches matching requests for 24 hours, and saves full responses locally.]
\n\n## Skill Version(s):
\n1.0.4 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.3: 5 files, 12593 bytes\n\nFiles: references/api.md (3462b), scripts/google_trends_rising.py (13177b), skill-card.md (2229b), SKILL.md (7586b), _meta.json (157b)\n\nFile v1.0.3:SKILL.md\n\n---\r\nname: linkfox-google-trend-get-trend-by-time\r\ndescription: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。\r\n---\r\n\r\n# Google Trends Time-Range Analysis\r\n\r\nThis skill guides you on how to query and analyze Google Trends data for trending topics within a configurable time window, helping users discover real-time popular searches and emerging trends across 18 supported regions.\r\n\r\n## Core Concepts\r\n\r\nGoogle Trends reflects real user search interest on Google. This tool retrieves **trending topics** (recently popular queries) for a chosen country/region over a specified number of recent days. It is ideal for spotting what is currently gaining traction in a market.\r\n\r\n**Key data points per trending query**:\r\n- **query** -- the trending search term\r\n- **searchVolume** -- relative search volume value\r\n- **increasePercentage** -- percentage change in search interest (-100 to 100, unit: %)\r\n- **startTime / endTime** -- timestamps bounding the trend observation window\r\n\r\nA positive `increasePercentage` means rising interest; a negative value means declining interest. A value near 100 signals an explosive spike.\r\n\r\n## Parameter Guide\r\n\r\n| Parameter | Type | Required | Default | Description |\r\n|-----------|------|----------|---------|-------------|\r\n| days | integer | No | 7 | Time range in days. Common values: 1 (last 24 hours), 2, 7 (past week) |\r\n| region | string | No | US | Country/region code. See Supported Regions below |\r\n\r\n### Supported Regions\r\n\r\nUS (United States), GB (United Kingdom), JP (Japan), CA (Canada), MX (Mexico), DE (Germany), FR (France), IT (Italy), ES (Spain), NL (Netherlands), AU (Australia), SG (Singapore), AE (United Arab Emirates), BR (Brazil), IN (India), TR (Turkey), PL (Poland), SE (Sweden)\r\n\r\nDefault region is **US**. Use US when the user does not specify a region.\r\n\r\n## 调用方式\r\n\r\n- **API 端点**：`POST /googleTrend/getTrendByTime`（完整参数/响应/错误码见 `references/api.md`）\r\n- **Python 脚本**：`python scripts/google_trends_rising.py '' [--inline]`\r\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\r\n\r\n**输出策略（脚本默认行为）**：\r\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-time-.json`（`` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）\r\n- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout\r\n- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 `total`/`costToken`、最大列表字段的长度 + 前 3 条样本）\r\n- 加 `--inline` 强制全量打印到 stdout（同样落盘）\r\n\r\n**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。\r\n## Usage Examples\r\n\r\n**1. What's trending in the US over the past week?**\r\n```json\r\n{\"days\": 7, \"region\": \"US\"}\r\n```\r\n\r\n**2. Hot topics in Japan in the last 24 hours**\r\n```json\r\n{\"days\": 1, \"region\": \"JP\"}\r\n```\r\n\r\n**3. Trending searches in Germany over the past 2 days**\r\n```json\r\n{\"days\": 2, \"region\": \"DE\"}\r\n```\r\n\r\n**4. Recent buzz in Brazil this week**\r\n```json\r\n{\"days\": 7, \"region\": \"BR\"}\r\n```\r\n\r\n**5. What's gaining popularity in the UK right now?**\r\n```json\r\n{\"days\": 1, \"region\": \"GB\"}\r\n```\r\n\r\n## Display Rules\r\n\r\n1. **Present data clearly**: Show trending queries in a well-formatted table with columns for query, search volume, and increase percentage. Sort by search volume or increase percentage as appropriate.\r\n2. **Highlight spikes**: When `increasePercentage` is notably high (e.g., above 50%), call attention to these breakout topics.\r\n3. **Time context**: Always state the time range and region in your summary so the user knows exactly what window the data covers.\r\n4. **Chart data**: If the response includes `chartOption`, describe the chart structure (title, axes, data points) so the user understands the visual trend.\r\n5. **Error handling**: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., try a different region code or time range).\r\n## Important Limitations\r\n\r\n- **Unstructured data**: Results from this tool are unstructured and cannot be fed into secondary SQL-based query tools for further processing.\r\n- **Relative volumes**: Search volume values are relative, not absolute counts.\r\n- **Short time windows**: The `days` parameter controls recency; this tool is designed for recent/real-time trends, not long historical analysis.\r\n- **Region coverage**: Only the 18 listed regions are supported. Unsupported region codes will produce errors.\r\n\r\n## User Expression & Scenario Quick Reference\r\n\r\n**Applicable** -- Queries about trending/popular topics on Google:\r\n\r\n| User Says | Scenario |\r\n|-----------|----------|\r\n| \"What's trending right now\" | Real-time trending topics |\r\n| \"Hot searches in [country]\" | Regional trend discovery |\r\n| \"What topics are popular this week\" | Weekly popularity overview |\r\n| \"Any viral topics in [market]\" | Breakout / spike detection |\r\n| \"Show me Google Trends for [region]\" | Region-specific trend query |\r\n| \"What's buzzing in the last 24 hours\" | Short-window trend scan |\r\n| \"Trending searches in [country] recently\" | Recent trend analysis |\r\n| \"What are people searching for in [region]\" | General search interest exploration |\r\n\r\n**Not applicable** -- Needs beyond trending topic discovery:\r\n\r\n- Historical keyword search volume over months/years (use a dedicated Google Trends historical tool)\r\n- Amazon-specific keyword or ASIN analysis (use ABA tools)\r\n- Advertising / PPC campaign management\r\n- Social media trend analysis (Twitter/X, TikTok, etc.)\r\n- SEO ranking or backlink analysis\r\n- Competitor website traffic estimation\r\n\r\n**Boundary judgment**: When users say \"market trends\" or \"what's popular\", if it boils down to discovering what people are currently searching for on Google in a specific region, this skill applies. If they are asking about stock market trends, social media virality, or long-term historical search patterns, it does not apply.\r\n\r\n\r\n**Feedback:**\r\n\r\nAuto-detect and report feedback via the Feedback API when any of the following apply:\r\n1. The functionality or purpose described in this skill does not match actual behavior\r\n2. The skill's results do not match the user's intent\r\n3. The user expresses dissatisfaction or praise about this skill\r\n4. Anything you believe could be improved\r\n\r\nCall the feedback API as specified in `references/api.md`. Do not interrupt the user's flow.\r\n\r\n\r\n---\r\n*For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn7dmc1t4j28hem1twwyav85p182pb1j\",\n \"slug\": \"linkfox-google-trend-get-trend-by-time\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1783336784493\n}\n\nFile v1.0.3:references/api.md\n\n# 谷歌趋势-时下流行 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByTime`\r\n- **请求方式**：POST，Content-Type: application/json\r\n- **认证方式**：Header `Authorization: `，api_key 从环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY` 读取\r\n\r\n## 请求参数\r\n\r\nPOST Body（JSON）：\r\n\r\n| 参数 | 类型 | 必填 | 说明 |\r\n|------|------|------|------|\r\n| days | integer | 否 | 时间范围，查询最近多少天的趋势数据，默认 `7`。常用值：1、2、7 |\r\n| region | string | 否 | 国家/地区代码，默认 `US`。可选值：US、GB、JP、CA、MX、DE、FR、IT、ES、NL、AU、SG、AE、BR、IN、TR、PL、SE |\r\n\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| costToken | integer | 消耗token |\r\n| chartOption | object | 图表配置对象，包含可视化数据 |\r\n| chartOption.data | array | 数据，图表数据点对象数组 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.title | string | 标题 |\r\n| trendValues | array | 趋势值，热门查询对象数组（见下方） |\r\n\r\n### trendValues 元素结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| query | string | 关键词 |\r\n| searchVolume | integer | 搜索量值 |\r\n| increasePercentage | integer | 涨幅百分比：整数，取值范围 −100～100，单位为％ |\r\n| startTime | string | 开始时间戳 |\r\n| endTime | string | 结束时间戳 |\r\n\r\n## 错误码\r\n\r\n正常情况下，接口的 HTTP 状态码均为 200，业务的成功与否通过响应体中的 errorCode 字段区分（errorCode = 200 表示成功，其他值表示业务错误）。当遇到未授权等情况时，HTTP 状态码为 401，且对应的 errorCode 也是 401。\r\n\r\n| errcode | 含义 | 处理建议 |\r\n|---------|------|----------|\r\n| 200 | 成功 | 正常解析业务字段 |\r\n| 401 | 认证失败 | 检查请求头 `Authorization` 是否正确携带 API Key；API Key 申请方式请参考上述[调用规范](#调用规范)下的认证方式。|\r\n| 其他非200值 | 业务异常 | 参考 `errmsg` 字段获取具体错误原因 |\r\n\r\n错误响应示例：\r\n\r\n```json\r\n{\r\n \"errcode\": 401,\r\n \"errmsg\": \"authorized error\"\r\n}\r\n```\r\n\r\n## curl 示例\r\n\r\n```bash\r\ncurl -X POST https://tool-gateway.linkfox.com/googleTrend/getTrendByTime \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"days\": 7, \"region\": \"US\"}'\r\n```\r\n\r\n---\r\n\r\n## Feedback API\r\n\r\n> This endpoint is **separate** from the tool API above. Do not mix the two base URLs.\r\n\r\n- **POST** `https://skill-api.linkfox.com/api/v1/public/feedback`\r\n- **Content-Type:** `application/json`\r\n\r\n```json\r\n{\r\n \"skillName\": \"linkfox-xxx-xxx\",\r\n \"sentiment\": \"POSITIVE\",\r\n \"category\": \"OTHER\",\r\n \"content\": \"Results were accurate, user was satisfied.\"\r\n}\r\n```\r\n\r\n**Field rules:**\r\n- `skillName`: Use this skill's `name` from the YAML frontmatter\r\n- `sentiment`: Choose ONE — `POSITIVE` (praise), `NEUTRAL` (suggestion without emotion), `NEGATIVE` (complaint or error)\r\n- `category`: Choose ONE — `BUG` (malfunction or wrong data), `COMPLAINT` (user dissatisfaction), `SUGGESTION` (improvement idea), `OTHER`\r\n- `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise\n\nFile v1.0.3:skill-card.md\n\n## Description:
\nQueries and analyzes recent Google Trends hot topics and trending searches by time window and supported country or region.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[linkfox-ai](https://clawhub.ai/user/linkfox-ai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nAgents and developers use this skill to retrieve recent Google Trends topics for a supported country or region, then summarize trending queries, relative search volume, percentage change, and the observation window for users.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill uses a LinkFox API key and consumes credits for trend lookups.
\nMitigation: Confirm the user wants additional lookups before repeat calls and keep the API key in the runtime environment.
\nRisk: Full API responses are cached or saved locally and may remain in shared or source-controlled directories.
\nMitigation: Run from an appropriate workspace and review or clean generated linkfox data files before sharing or committing.
\nRisk: Automatic feedback reporting may send user feedback text to LinkFox.
\nMitigation: Avoid including secrets or sensitive user content in feedback and disclose telemetry-sensitive behavior when relevant.
\n\n\n## Reference(s):
\n- [API Reference](references/api.md)
\n- [ClawHub Skill Page](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-time)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, JSON, Files, Markdown]
\n**Output Format:** [Markdown guidance with JSON API responses and saved local JSON files]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires a LinkFox API key; uses a 24-hour local cache and saves full API responses locally.]
\n\n## Skill Version(s):
\n1.0.3 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.2: 4 files, 11396 bytes\n\nFiles: references/api.md (3462b), scripts/google_trends_rising.py (13177b), SKILL.md (7586b), _meta.json (157b)\n\nFile v1.0.2:SKILL.md\n\n---\r\nname: linkfox-google-trend-get-trend-by-time\r\ndescription: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。\r\n---\r\n\r\n# Google Trends Time-Range Analysis\r\n\r\nThis skill guides you on how to query and analyze Google Trends data for trending topics within a configurable time window, helping users discover real-time popular searches and emerging trends across 18 supported regions.\r\n\r\n## Core Concepts\r\n\r\nGoogle Trends reflects real user search interest on Google. This tool retrieves **trending topics** (recently popular queries) for a chosen country/region over a specified number of recent days. It is ideal for spotting what is currently gaining traction in a market.\r\n\r\n**Key data points per trending query**:\r\n- **query** -- the trending search term\r\n- **searchVolume** -- relative search volume value\r\n- **increasePercentage** -- percentage change in search interest (-100 to 100, unit: %)\r\n- **startTime / endTime** -- timestamps bounding the trend observation window\r\n\r\nA positive `increasePercentage` means rising interest; a negative value means declining interest. A value near 100 signals an explosive spike.\r\n\r\n## Parameter Guide\r\n\r\n| Parameter | Type | Required | Default | Description |\r\n|-----------|------|----------|---------|-------------|\r\n| days | integer | No | 7 | Time range in days. Common values: 1 (last 24 hours), 2, 7 (past week) |\r\n| region | string | No | US | Country/region code. See Supported Regions below |\r\n\r\n### Supported Regions\r\n\r\nUS (United States), GB (United Kingdom), JP (Japan), CA (Canada), MX (Mexico), DE (Germany), FR (France), IT (Italy), ES (Spain), NL (Netherlands), AU (Australia), SG (Singapore), AE (United Arab Emirates), BR (Brazil), IN (India), TR (Turkey), PL (Poland), SE (Sweden)\r\n\r\nDefault region is **US**. Use US when the user does not specify a region.\r\n\r\n## 调用方式\r\n\r\n- **API 端点**：`POST /googleTrend/getTrendByTime`（完整参数/响应/错误码见 `references/api.md`）\r\n- **Python 脚本**：`python scripts/google_trends_rising.py '' [--inline]`\r\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\r\n\r\n**输出策略（脚本默认行为）**：\r\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-time-.json`（`` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）\r\n- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout\r\n- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 `total`/`costToken`、最大列表字段的长度 + 前 3 条样本）\r\n- 加 `--inline` 强制全量打印到 stdout（同样落盘）\r\n\r\n**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。\r\n## Usage Examples\r\n\r\n**1. What's trending in the US over the past week?**\r\n```json\r\n{\"days\": 7, \"region\": \"US\"}\r\n```\r\n\r\n**2. Hot topics in Japan in the last 24 hours**\r\n```json\r\n{\"days\": 1, \"region\": \"JP\"}\r\n```\r\n\r\n**3. Trending searches in Germany over the past 2 days**\r\n```json\r\n{\"days\": 2, \"region\": \"DE\"}\r\n```\r\n\r\n**4. Recent buzz in Brazil this week**\r\n```json\r\n{\"days\": 7, \"region\": \"BR\"}\r\n```\r\n\r\n**5. What's gaining popularity in the UK right now?**\r\n```json\r\n{\"days\": 1, \"region\": \"GB\"}\r\n```\r\n\r\n## Display Rules\r\n\r\n1. **Present data clearly**: Show trending queries in a well-formatted table with columns for query, search volume, and increase percentage. Sort by search volume or increase percentage as appropriate.\r\n2. **Highlight spikes**: When `increasePercentage` is notably high (e.g., above 50%), call attention to these breakout topics.\r\n3. **Time context**: Always state the time range and region in your summary so the user knows exactly what window the data covers.\r\n4. **Chart data**: If the response includes `chartOption`, describe the chart structure (title, axes, data points) so the user understands the visual trend.\r\n5. **Error handling**: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., try a different region code or time range).\r\n## Important Limitations\r\n\r\n- **Unstructured data**: Results from this tool are unstructured and cannot be fed into secondary SQL-based query tools for further processing.\r\n- **Relative volumes**: Search volume values are relative, not absolute counts.\r\n- **Short time windows**: The `days` parameter controls recency; this tool is designed for recent/real-time trends, not long historical analysis.\r\n- **Region coverage**: Only the 18 listed regions are supported. Unsupported region codes will produce errors.\r\n\r\n## User Expression & Scenario Quick Reference\r\n\r\n**Applicable** -- Queries about trending/popular topics on Google:\r\n\r\n| User Says | Scenario |\r\n|-----------|----------|\r\n| \"What's trending right now\" | Real-time trending topics |\r\n| \"Hot searches in [country]\" | Regional trend discovery |\r\n| \"What topics are popular this week\" | Weekly popularity overview |\r\n| \"Any viral topics in [market]\" | Breakout / spike detection |\r\n| \"Show me Google Trends for [region]\" | Region-specific trend query |\r\n| \"What's buzzing in the last 24 hours\" | Short-window trend scan |\r\n| \"Trending searches in [country] recently\" | Recent trend analysis |\r\n| \"What are people searching for in [region]\" | General search interest exploration |\r\n\r\n**Not applicable** -- Needs beyond trending topic discovery:\r\n\r\n- Historical keyword search volume over months/years (use a dedicated Google Trends historical tool)\r\n- Amazon-specific keyword or ASIN analysis (use ABA tools)\r\n- Advertising / PPC campaign management\r\n- Social media trend analysis (Twitter/X, TikTok, etc.)\r\n- SEO ranking or backlink analysis\r\n- Competitor website traffic estimation\r\n\r\n**Boundary judgment**: When users say \"market trends\" or \"what's popular\", if it boils down to discovering what people are currently searching for on Google in a specific region, this skill applies. If they are asking about stock market trends, social media virality, or long-term historical search patterns, it does not apply.\r\n\r\n\r\n**Feedback:**\r\n\r\nAuto-detect and report feedback via the Feedback API when any of the following apply:\r\n1. The functionality or purpose described in this skill does not match actual behavior\r\n2. The skill's results do not match the user's intent\r\n3. The user expresses dissatisfaction or praise about this skill\r\n4. Anything you believe could be improved\r\n\r\nCall the feedback API as specified in `references/api.md`. Do not interrupt the user's flow.\r\n\r\n\r\n---\r\n*For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn7dmc1t4j28hem1twwyav85p182pb1j\",\n \"slug\": \"linkfox-google-trend-get-trend-by-time\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1783066711888\n}\n\nFile v1.0.2:references/api.md\n\n# 谷歌趋势-时下流行 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByTime`\r\n- **请求方式**：POST，Content-Type: application/json\r\n- **认证方式**：Header `Authorization: `，api_key 从环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY` 读取\r\n\r\n## 请求参数\r\n\r\nPOST Body（JSON）：\r\n\r\n| 参数 | 类型 | 必填 | 说明 |\r\n|------|------|------|------|\r\n| days | integer | 否 | 时间范围，查询最近多少天的趋势数据，默认 `7`。常用值：1、2、7 |\r\n| region | string | 否 | 国家/地区代码，默认 `US`。可选值：US、GB、JP、CA、MX、DE、FR、IT、ES、NL、AU、SG、AE、BR、IN、TR、PL、SE |\r\n\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| costToken | integer | 消耗token |\r\n| chartOption | object | 图表配置对象，包含可视化数据 |\r\n| chartOption.data | array | 数据，图表数据点对象数组 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.title | string | 标题 |\r\n| trendValues | array | 趋势值，热门查询对象数组（见下方） |\r\n\r\n### trendValues 元素结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| query | string | 关键词 |\r\n| searchVolume | integer | 搜索量值 |\r\n| increasePercentage | integer | 涨幅百分比：整数，取值范围 −100～100，单位为％ |\r\n| startTime | string | 开始时间戳 |\r\n| endTime | string | 结束时间戳 |\r\n\r\n## 错误码\r\n\r\n正常情况下，接口的 HTTP 状态码均为 200，业务的成功与否通过响应体中的 errorCode 字段区分（errorCode = 200 表示成功，其他值表示业务错误）。当遇到未授权等情况时，HTTP 状态码为 401，且对应的 errorCode 也是 401。\r\n\r\n| errcode | 含义 | 处理建议 |\r\n|---------|------|----------|\r\n| 200 | 成功 | 正常解析业务字段 |\r\n| 401 | 认证失败 | 检查请求头 `Authorization` 是否正确携带 API Key；API Key 申请方式请参考上述[调用规范](#调用规范)下的认证方式。|\r\n| 其他非200值 | 业务异常 | 参考 `errmsg` 字段获取具体错误原因 |\r\n\r\n错误响应示例：\r\n\r\n```json\r\n{\r\n \"errcode\": 401,\r\n \"errmsg\": \"authorized error\"\r\n}\r\n```\r\n\r\n## curl 示例\r\n\r\n```bash\r\ncurl -X POST https://tool-gateway.linkfox.com/googleTrend/getTrendByTime \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"days\": 7, \"region\": \"US\"}'\r\n```\r\n\r\n---\r\n\r\n## Feedback API\r\n\r\n> This endpoint is **separate** from the tool API above. Do not mix the two base URLs.\r\n\r\n- **POST** `https://skill-api.linkfox.com/api/v1/public/feedback`\r\n- **Content-Type:** `application/json`\r\n\r\n```json\r\n{\r\n \"skillName\": \"linkfox-xxx-xxx\",\r\n \"sentiment\": \"POSITIVE\",\r\n \"category\": \"OTHER\",\r\n \"content\": \"Results were accurate, user was satisfied.\"\r\n}\r\n```\r\n\r\n**Field rules:**\r\n- `skillName`: Use this skill's `name` from the YAML frontmatter\r\n- `sentiment`: Choose ONE — `POSITIVE` (praise), `NEUTRAL` (suggestion without emotion), `NEGATIVE` (complaint or error)\r\n- `category`: Choose ONE — `BUG` (malfunction or wrong data), `COMPLAINT` (user dissatisfaction), `SUGGESTION` (improvement idea), `OTHER`\r\n- `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise\n\nArchive v1.0.1: 4 files, 11376 bytes\n\nFiles: references/api.md (3463b), scripts/google_trends_rising.py (13179b), SKILL.md (7586b), _meta.json (157b)\n\nFile v1.0.1:SKILL.md\n\n---\r\nname: linkfox-google-trend-get-trend-by-time\r\ndescription: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。\r\n---\r\n\r\n# Google Trends Time-Range Analysis\r\n\r\nThis skill guides you on how to query and analyze Google Trends data for trending topics within a configurable time window, helping users discover real-time popular searches and emerging trends across 18 supported regions.\r\n\r\n## Core Concepts\r\n\r\nGoogle Trends reflects real user search interest on Google. This tool retrieves **trending topics** (recently popular queries) for a chosen country/region over a specified number of recent days. It is ideal for spotting what is currently gaining traction in a market.\r\n\r\n**Key data points per trending query**:\r\n- **query** -- the trending search term\r\n- **searchVolume** -- relative search volume value\r\n- **increasePercentage** -- percentage change in search interest (-100 to 100, unit: %)\r\n- **startTime / endTime** -- timestamps bounding the trend observation window\r\n\r\nA positive `increasePercentage` means rising interest; a negative value means declining interest. A value near 100 signals an explosive spike.\r\n\r\n## Parameter Guide\r\n\r\n| Parameter | Type | Required | Default | Description |\r\n|-----------|------|----------|---------|-------------|\r\n| days | integer | No | 7 | Time range in days. Common values: 1 (last 24 hours), 2, 7 (past week) |\r\n| region | string | No | US | Country/region code. See Supported Regions below |\r\n\r\n### Supported Regions\r\n\r\nUS (United States), GB (United Kingdom), JP (Japan), CA (Canada), MX (Mexico), DE (Germany), FR (France), IT (Italy), ES (Spain), NL (Netherlands), AU (Australia), SG (Singapore), AE (United Arab Emirates), BR (Brazil), IN (India), TR (Turkey), PL (Poland), SE (Sweden)\r\n\r\nDefault region is **US**. Use US when the user does not specify a region.\r\n\r\n## 调用方式\r\n\r\n- **API 端点**：`POST /googleTrend/getTrendByTime`（完整参数/响应/错误码见 `references/api.md`）\r\n- **Python 脚本**：`python scripts/google_trends_rising.py '' [--inline]`\r\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\r\n\r\n**输出策略（脚本默认行为）**：\r\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-time-.json`（`` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）\r\n- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout\r\n- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 `total`/`costToken`、最大列表字段的长度 + 前 3 条样本）\r\n- 加 `--inline` 强制全量打印到 stdout（同样落盘）\r\n\r\n**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。\r\n## Usage Examples\r\n\r\n**1. What's trending in the US over the past week?**\r\n```json\r\n{\"days\": 7, \"region\": \"US\"}\r\n```\r\n\r\n**2. Hot topics in Japan in the last 24 hours**\r\n```json\r\n{\"days\": 1, \"region\": \"JP\"}\r\n```\r\n\r\n**3. Trending searches in Germany over the past 2 days**\r\n```json\r\n{\"days\": 2, \"region\": \"DE\"}\r\n```\r\n\r\n**4. Recent buzz in Brazil this week**\r\n```json\r\n{\"days\": 7, \"region\": \"BR\"}\r\n```\r\n\r\n**5. What's gaining popularity in the UK right now?**\r\n```json\r\n{\"days\": 1, \"region\": \"GB\"}\r\n```\r\n\r\n## Display Rules\r\n\r\n1. **Present data clearly**: Show trending queries in a well-formatted table with columns for query, search volume, and increase percentage. Sort by search volume or increase percentage as appropriate.\r\n2. **Highlight spikes**: When `increasePercentage` is notably high (e.g., above 50%), call attention to these breakout topics.\r\n3. **Time context**: Always state the time range and region in your summary so the user knows exactly what window the data covers.\r\n4. **Chart data**: If the response includes `chartOption`, describe the chart structure (title, axes, data points) so the user understands the visual trend.\r\n5. **Error handling**: When a query fails, explain the reason based on the error response and suggest adjusting parameters (e.g., try a different region code or time range).\r\n## Important Limitations\r\n\r\n- **Unstructured data**: Results from this tool are unstructured and cannot be fed into secondary SQL-based query tools for further processing.\r\n- **Relative volumes**: Search volume values are relative, not absolute counts.\r\n- **Short time windows**: The `days` parameter controls recency; this tool is designed for recent/real-time trends, not long historical analysis.\r\n- **Region coverage**: Only the 18 listed regions are supported. Unsupported region codes will produce errors.\r\n\r\n## User Expression & Scenario Quick Reference\r\n\r\n**Applicable** -- Queries about trending/popular topics on Google:\r\n\r\n| User Says | Scenario |\r\n|-----------|----------|\r\n| \"What's trending right now\" | Real-time trending topics |\r\n| \"Hot searches in [country]\" | Regional trend discovery |\r\n| \"What topics are popular this week\" | Weekly popularity overview |\r\n| \"Any viral topics in [market]\" | Breakout / spike detection |\r\n| \"Show me Google Trends for [region]\" | Region-specific trend query |\r\n| \"What's buzzing in the last 24 hours\" | Short-window trend scan |\r\n| \"Trending searches in [country] recently\" | Recent trend analysis |\r\n| \"What are people searching for in [region]\" | General search interest exploration |\r\n\r\n**Not applicable** -- Needs beyond trending topic discovery:\r\n\r\n- Historical keyword search volume over months/years (use a dedicated Google Trends historical tool)\r\n- Amazon-specific keyword or ASIN analysis (use ABA tools)\r\n- Advertising / PPC campaign management\r\n- Social media trend analysis (Twitter/X, TikTok, etc.)\r\n- SEO ranking or backlink analysis\r\n- Competitor website traffic estimation\r\n\r\n**Boundary judgment**: When users say \"market trends\" or \"what's popular\", if it boils down to discovering what people are currently searching for on Google in a specific region, this skill applies. If they are asking about stock market trends, social media virality, or long-term historical search patterns, it does not apply.\r\n\r\n\r\n**Feedback:**\r\n\r\nAuto-detect and report feedback via the Feedback API when any of the following apply:\r\n1. The functionality or purpose described in this skill does not match actual behavior\r\n2. The skill's results do not match the user's intent\r\n3. The user expresses dissatisfaction or praise about this skill\r\n4. Anything you believe could be improved\r\n\r\nCall the feedback API as specified in `references/api.md`. Do not interrupt the user's flow.\r\n\r\n\r\n---\r\n*For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).*\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn7dmc1t4j28hem1twwyav85p182pb1j\",\n \"slug\": \"linkfox-google-trend-get-trend-by-time\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1783057671155\n}\n\nFile v1.0.1:references/api.md\n\n# 谷歌趋势-时下流行 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_AGENT_API_URL}/googleTrend/getTrendByTime`\r\n- **请求方式**：POST，Content-Type: application/json\r\n- **认证方式**：Header `Authorization: `，api_key 从环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY` 读取\r\n\r\n## 请求参数\r\n\r\nPOST Body（JSON）：\r\n\r\n| 参数 | 类型 | 必填 | 说明 |\r\n|------|------|------|------|\r\n| days | integer | 否 | 时间范围，查询最近多少天的趋势数据，默认 `7`。常用值：1、2、7 |\r\n| region | string | 否 | 国家/地区代码，默认 `US`。可选值：US、GB、JP、CA、MX、DE、FR、IT、ES、NL、AU、SG、AE、BR、IN、TR、PL、SE |\r\n\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| costToken | integer | 消耗token |\r\n| chartOption | object | 图表配置对象，包含可视化数据 |\r\n| chartOption.data | array | 数据，图表数据点对象数组 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.title | string | 标题 |\r\n| trendValues | array | 趋势值，热门查询对象数组（见下方） |\r\n\r\n### trendValues 元素结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| query | string | 关键词 |\r\n| searchVolume | integer | 搜索量值 |\r\n| increasePercentage | integer | 涨幅百分比：整数，取值范围 −100～100，单位为％ |\r\n| startTime | string | 开始时间戳 |\r\n| endTime | string | 结束时间戳 |\r\n\r\n## 错误码\r\n\r\n正常情况下，接口的 HTTP 状态码均为 200，业务的成功与否通过响应体中的 errorCode 字段区分（errorCode = 200 表示成功，其他值表示业务错误）。当遇到未授权等情况时，HTTP 状态码为 401，且对应的 errorCode 也是 401。\r\n\r\n| errcode | 含义 | 处理建议 |\r\n|---------|------|----------|\r\n| 200 | 成功 | 正常解析业务字段 |\r\n| 401 | 认证失败 | 检查请求头 `Authorization` 是否正确携带 API Key；API Key 申请方式请参考上述[调用规范](#调用规范)下的认证方式。|\r\n| 其他非200值 | 业务异常 | 参考 `errmsg` 字段获取具体错误原因 |\r\n\r\n错误响应示例：\r\n\r\n```json\r\n{\r\n \"errcode\": 401,\r\n \"errmsg\": \"authorized error\"\r\n}\r\n```\r\n\r\n## curl 示例\r\n\r\n```bash\r\ncurl -X POST https://tool-gateway.linkfox.com/googleTrend/getTrendByTime \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"days\": 7, \"region\": \"US\"}'\r\n```\r\n\r\n---\r\n\r\n## Feedback API\r\n\r\n> This endpoint is **separate** from the tool API above. Do not mix the two base URLs.\r\n\r\n- **POST** `https://skill-api.linkfox.com/api/v1/public/feedback`\r\n- **Content-Type:** `application/json`\r\n\r\n```json\r\n{\r\n \"skillName\": \"linkfox-xxx-xxx\",\r\n \"sentiment\": \"POSITIVE\",\r\n \"category\": \"OTHER\",\r\n \"content\": \"Results were accurate, user was satisfied.\"\r\n}\r\n```\r\n\r\n**Field rules:**\r\n- `skillName`: Use this skill's `name` from the YAML frontmatter\r\n- `sentiment`: Choose ONE — `POSITIVE` (praise), `NEUTRAL` (suggestion without emotion), `NEGATIVE` (complaint or error)\r\n- `category`: Choose ONE — `BUG` (malfunction or wrong data), `COMPLAINT` (user dissatisfaction), `SUGGESTION` (improvement idea), `OTHER`\r\n- `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise","readmeExcerpt":"Skill: 谷歌趋势-热门词查询 Owner: linkfox-ai Summary: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。 Tags: latest:1.0.7 Version history: v1.0.7 | 2026-09-14T05:19:35.016Z | user Update from 1.0.6 to ","codeSnippets":[],"executableExamples":[{"language":"json","snippet":"{\"days\": 7, \"region\": \"US\"}"},{"language":"json","snippet":"{\"days\": 1, \"region\": \"JP\"}"},{"language":"json","snippet":"{\"days\": 2, \"region\": \"DE\"}"},{"language":"json","snippet":"{\"days\": 7, \"region\": \"BR\"}"},{"language":"json","snippet":"{\"days\": 1, \"region\": \"GB\"}"},{"language":"json","snippet":"{\"days\": 7, \"region\": \"US\"}"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: linkfox-google-trend-get-trend-by-time\ndescription: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。\n---\n\n# Google Trends Time-Range Analysis\n\nThis skill guides you on how to query and analyze Google Trends data for trending topics within a configurable time window, helping users discover real-time popular searches and emerging trends across 18 supported regions.\n\n## Core Concepts\n\nGoogle Trends reflects real user search interest on Google. This tool retrieves **trending topics** (recently popular queries) for a chosen country/region over a specified number of recent days. It is ideal for spotting what is currently gaining traction in a market.\n\n**Key data points per trending query**:\n- **query** -- the trending search term\n- **searchVolume** -- relative search volume value\n- **increasePercentage** -- percentage change in search interest (-100 to 100, unit: %)\n- **startTime / endTime** -- timestamps bounding the trend observation window\n\nA positive `increasePercentage` means rising interest; a negative value means declining interest. A value near 100 signals an explosive spike.\n\n## Parameter Guide\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| days | integer | No | 7 | Time range in days. Common values: 1 (last 24 hours), 2, 7 (past week) |\n| region | string | No | US | Country/region code. See Supported Regions below |\n\n### Supported Regions\n\nUS (United States), GB (United Kingdom), JP (Japan), CA (Canada), MX (Mexico), DE (Germany), FR (France), IT (Italy), ES (Spain), NL (Netherlands), AU (Australia), SG (Singapore), AE (United Arab Emirates), BR (Brazil), IN (India), TR (Turkey), PL (Poland), SE (Sweden)\n\nDefault region is **US**. Use US when the user does not specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByTime`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_rising.py '' [--inline]`\n- **成本约束**：本工具会消耗算力；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-time-.json`（`` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）\n- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout\n- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如 `total`/`costToken`、最大列表字段的长度 + 前 3 条样本）\n- 加 `--inline` 强制全量打印到 stdout（同样落盘）\n\n**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。\n## 解决认证和算力问题\n发生以下异常情况时，采用 references/onboarding.md 引导解决问题：\n\n### 异常情况\n- **未配置API Key**：环境变量未配置 `LINKFOX_AGENT_API_KEY`，也未配置 `LINKFOXAGENT_API_KEY`。\n- **响应401或402状态码**\n- **响应提示算力或余额不足**：消息含\"算力余额不足/计费不足/余额不足/quota exceeded/i"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7dmc1t4j28hem1twwyav85p182pb1j\",\n \"slug\": \"linkfox-google-trend-get-trend-by-time\",\n \"version\": \"1.0.7\",\n \"publishedAt\": 1789363175016\n}"},{"path":"references/api.md","content":"# 谷歌趋势-时下流行 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByTime`\r\n- **请求方式**：POST，Content-Type: application/json\r\n- **认证方式**：Header `Authorization: `，api_key 从环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY` 读取（如未配置 按 SKILL.md 的 **## 解决认证和算力问题** 处理）\r\n\r\n## 请求参数\r\n\r\nPOST Body（JSON）：\r\n\r\n| 参数 | 类型 | 必填 | 说明 |\r\n|------|------|------|------|\r\n| days | integer | 否 | 时间范围，查询最近多少天的趋势数据，默认 `7`。常用值：1、2、7 |\r\n| region | string | 否 | 国家/地区代码，默认 `US`。可选值：US、GB、JP、CA、MX、DE、FR、IT、ES、NL、AU、SG、AE、BR、IN、TR、PL、SE |\r\n\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| costToken | integer | 消耗token |\r\n| chartOption | object | 图表配置对象，包含可视化数据 |\r\n| chartOption.data | array | 数据，图表数据点对象数组 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.title | string | 标题 |\r\n| trendValues | array | 趋势值，热门查询对象数组（见下方） |\r\n\r\n### trendValues 元素结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| query | string | 关键词 |\r\n| searchVolume | integer | 搜索量值 |\r\n| increasePercentage | integer | 涨幅百分比：整数，取值范围 −100～100，单位为％ |\r\n| startTime | string | 开始时间戳 |\r\n| endTime | string | 结束时间戳 |\r\n\r\n## 错误码\r\n\r\n正常情况下，接口的 HTTP 状态码均为 200，业务的成功与否通过响应体中的 errorCode 字段区分（errorCode = 200 表示成功，其他值表示业务错误）。当遇到未授权等情况时，HTTP 状态码为 401，且对应的 errorCode 也是 401。\r\n\r\n| errcode | 含义 | 处理建议 |\r\n|---------|------|----------|\r\n| 200 | 成功 | 正常解析业务字段 |\r\n| 401 | 认证失败 | HTTP 401 或 authorized error：按 SKILL.md 的 **## 解决认证和算力问题** 处理。|\r\n| 402 | 算力不足 | HTTP 402：按 SKILL.md 的 **## 解决认证和算力问题** 处理。|\r\n| 其他非200值 | 业务异常 | 参考 `errmsg` 字段获取具体错误原因 |\r\n\r\n错误响应示例：\r\n\r\n```json\r\n{\r\n \"errcode\": 401,\r\n \"errmsg\": \"authorized error\"\r\n}\r\n```\r\n\r\n## curl 示例\r\n\r\n```bash\r\ncurl -X POST https://tool-gateway.linkfox.com/googleTrend/getTrendByTime \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"days\": 7, \"region\": \"US\"}'\r\n```\r\n\r\n---\r\n\r\n## Feedback API\r\n\r\n> This endpoint is **separate** from the tool API above. Do not mix the two base URLs.\r\n\r\n- **POST** `https://skill-api.linkfox.com/api/v1/public/feedback`\r\n- **Content-Type:** `application/json`\r\n\r\n```json\r\n{\r\n \"skillName\": \"linkfox-xxx-xxx\",\r\n \"sentiment\": \"POSITIVE\",\r\n \"category\": \"OTHER\",\r\n \"content\": \"Results were accurate, user was satisfied.\"\r\n}\r\n```\r\n\r\n**Field rules:**\r\n- `skillName`: Use this skill's `name` from the YAML frontmatter\r\n- `sentiment`: Choose ONE — `POSITIVE` (praise), `NEUTRAL` (suggestion without emotion), `NEGATIVE` (complaint or error)\r\n- `category`: Choose ONE — `BUG` (malfunction or wrong data), `COMPLAINT` (user dissatisfaction), `SUGGESTION` (improvement idea), `OTHER`\r\n- `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise"},{"path":"references/onboarding.md","content":"# 解决认证和算力问题\n\n调用本 skill 时若网关返回 **auth** 或 **billing** 错误，走本 skill 自带的 `scripts/onboarding.py` 完成引导。\n\n**auth 场景**：`errcode=401` 或消息含 `authorized error`/`鉴权失败`/`未授权`/`unauthorized`；或 `LINKFOX_AGENT_API_KEY` 与 `LINKFOXAGENT_API_KEY` 均为空。\n1. 若已配置 key → 先让用户重启会话（最常见误判），仍失败让用户重新取 key 或换手机号重注册\n2. 未配置 → 询问：自助去 https://agent.linkfox.com/ 取 key，或提供手机号让脚本注册\n3. 手机号路径：\n - `python scripts/onboarding.py send-code ` → 展示 JSON 里的 phone/agreements\n - 收到验证码后：`python scripts/onboarding.py login `\n - 拿到 `api_key` 后把下面三平台配置转发给用户，提示重启会话生效：\n - Windows PowerShell（永久）：`setx LINKFOX_AGENT_API_KEY \"\"`\n - macOS zsh：`echo 'export LINKFOX_AGENT_API_KEY=\"\"' >> ~/.zshrc && source ~/.zshrc`\n - Linux bash：`echo 'export LINKFOX_AGENT_API_KEY=\"\"' >> ~/.bashrc && source ~/.bashrc`\n - 变量名 `LINKFOX_AGENT_API_KEY`（主推）或 `LINKFOXAGENT_API_KEY`（老规范）任一即可\n\n**billing 场景**：`errcode=402` 或消息含 `算力/余额/quota/insufficient/充值/套餐到期`。\n- `python scripts/onboarding.py list-plans` → 有 AskUserQuestion 就弹菜单，否则输出编号清单让用户选\n- 校验 `plan_id` ∈ 清单、支付方式 ∈ 该套餐 `available_methods`（通常 `wechat/alipay`）\n- `python scripts/onboarding.py order ` → 展示优先级 PNG > `pay_url` > `ascii_qr`（标注兜底）\n- 已付款可选调 `python scripts/onboarding.py query `，不主动轮询\n\n排除 `errcode=403`（无权限，不归入这两类）。所有子命令输出 stdout JSON，`error` 字段已含阶段前缀，透传给用户即可。完整用法：`python scripts/onboarding.py --help`。"},{"path":"skill-card.md","content":"## Description:\n\nQueries and analyzes recent Google Trends hot searches for a selected time window and supported country or region.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[linkfox-ai](https://clawhub.ai/user/linkfox-ai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users, analysts, and agents use this skill to discover recent Google search trends, breakout queries, and regional hot topics across supported markets.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Trend queries, session metadata, and feedback content may be sent to LinkFox services.\n\nMitigation: Install only when this data sharing is acceptable, and avoid including sensitive or unnecessary information in queries or feedback.\n\nRisk: The skill supports account login, API-key issuance, and payment-order creation.\n\nMitigation: Use the self-service LinkFox website for credentials when possible, do not share SMS codes unnecessarily, and confirm billing choices before creating an order.\n\nRisk: API keys may be exposed if stored carelessly in shell profiles or logs.\n\nMitigation: Store credentials in the recommended environment variable only in trusted environments, avoid printing keys, and rotate credentials if exposure is suspected.\n\nRisk: LINKFOX_* endpoint environment variables can redirect requests if controlled by another party.\n\nMitigation: Run the skill only where endpoint environment variables are trusted and review those variables before use.\n\n## Reference(s):\n\n- [API Reference](references/api.md)\n- [Authentication and Billing Onboarding](references/onboarding.md)\n- [ClawHub Skill Page](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-time)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, JSON, shell commands, configuration guidance]\n\n**Output Format:** [Markdown summaries, tables, JSON responses, and shell commands for API and onboarding workflows]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Trend calls save the full JSON response to a local linkfox session data file; small responses may also print in full, and large responses print a summary unless inline output is requested.]\n\n## Skill Version(s):\n\n1.0.7 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。 Skill: 谷歌趋势-热门词查询 Owner: linkfox-ai Summary: 查询并分析Google Trends在指定时间范围和国家/地区的实时热门话题与热搜。当用户提到谷歌趋势、热门话题、实时热搜、流行趋势、当前热点、近期热门、病毒式话题、时间段热度、区域趋势分析、Google Trends, real-time hot topics, trending topics, popular trends, recent trending searches, trend discovery时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及发现特定市场近期热门或正在流行的话题和搜索词，也应触发此技能。 Tags: latest:1.0.7 Version history: v1.0.7 | 2026-09-14T05:19:35.016Z | user Update from 1.0.6 to","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1354,"uniquenessScore":51,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-12T00:49:24.227Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-12T00:49:24.227Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-13T00:47:25.198Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}