{"id":"0ddf5b02-cd6e-48dd-bc4c-bace0f69c9fd","entityType":"agent","slug":"clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys","name":"谷歌趋势-关键词趋势","canonicalUrl":"https://www.xpersona.co/agent/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys","canonicalPath":"/agent/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys","generatedAt":"2026-10-12T11:27:31.974Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-12T00:40:38.625Z","emptyReason":null},"description":"Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。 Skill: 谷歌趋势-关键词趋势 Owner: linkfox-ai Summary: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。 Tags: latest:1.0.7 Version history: v1.0.7 | 2026-09-14T05:19:29.114Z","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 966 downloads reported by the source. Last updated 10/12/2026.","installCommand":"clawhub skill install s171g8b6m2khwdy9ye8bxj0wx183vd4z:linkfox-google-trend-get-trend-by-keys","sourceUrl":"https://clawhub.ai/linkfox-ai/linkfox-google-trend-get-trend-by-keys","homepage":"https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-keys","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/linkfox-ai/linkfox-google-trend-get-trend-by-keys","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-keys","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity compari"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:40:38.625Z","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:40:38.625Z","emptyReason":null},"stars":null,"forks":null,"downloads":966,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.0.7","tractionLabel":"966 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-12T00:40:38.612Z","emptyReason":null},"lastUpdatedAt":"2026-10-12T00:40:38.625Z","lastCrawledAt":"2026-10-12T00:40:38.612Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-13T00:40:38.612Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.7","createdAt":"2026-09-14T05:19:29.114Z","changelog":"Update from 1.0.6 to 1.0.7","fileCount":7,"zipByteSize":22946},{"version":"1.0.6","createdAt":"2026-08-14T14:54:11.644Z","changelog":"Update from 1.0.5 to 1.0.6","fileCount":7,"zipByteSize":22915},{"version":"1.0.5","createdAt":"2026-08-07T10:49:44.113Z","changelog":"Update from 1.0.4 to 1.0.5","fileCount":7,"zipByteSize":22919},{"version":"1.0.4","createdAt":"2026-07-13T12:10:38.420Z","changelog":"Update from 1.0.3 to 1.0.4","fileCount":5,"zipByteSize":14095},{"version":"1.0.3","createdAt":"2026-07-06T11:19:35.985Z","changelog":"Update from 1.0.2 to 1.0.3","fileCount":5,"zipByteSize":13422},{"version":"1.0.2","createdAt":"2026-07-03T08:18:23.965Z","changelog":"Update from 1.0.1 to 1.0.2","fileCount":4,"zipByteSize":11962},{"version":"1.0.1","createdAt":"2026-07-03T05:47:37.865Z","changelog":"Update from 1.0.0 to 1.0.1","fileCount":4,"zipByteSize":11941}]},"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-keys","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-keys/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys/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-12T11:27:31.969Z"}},"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-keys/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-google-trend-get-trend-by-keys/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:40:38.625Z","emptyReason":null},"readme":"Skill: 谷歌趋势-关键词趋势\n\nOwner: linkfox-ai\n\nSummary: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。\n\nTags: latest:1.0.7\n\nVersion history:\n\nv1.0.7 | 2026-09-14T05:19:29.114Z | user\n\nUpdate from 1.0.6 to 1.0.7\n\nv1.0.6 | 2026-08-14T14:54:11.644Z | user\n\nUpdate from 1.0.5 to 1.0.6\n\nv1.0.5 | 2026-08-07T10:49:44.113Z | user\n\nUpdate from 1.0.4 to 1.0.5\n\nv1.0.4 | 2026-07-13T12:10:38.420Z | user\n\nUpdate from 1.0.3 to 1.0.4\n\nv1.0.3 | 2026-07-06T11:19:35.985Z | user\n\nUpdate from 1.0.2 to 1.0.3\n\nv1.0.2 | 2026-07-03T08:18:23.965Z | user\n\nUpdate from 1.0.1 to 1.0.2\n\nv1.0.1 | 2026-07-03T05:47:37.865Z | user\n\nUpdate from 1.0.0 to 1.0.1\n\nArchive index:\n\nArchive v1.0.7: 7 files, 22946 bytes\n\nFiles: references/api.md (4035b), references/onboarding.md (1999b), scripts/google_trends_keyword.py (13149b), scripts/onboarding.py (24027b), skill-card.md (2437b), SKILL.md (9842b), _meta.json (157b)\n\nFile v1.0.7:SKILL.md\n\n---\nname: linkfox-google-trend-get-trend-by-keys\ndescription: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。\n---\n\n# Google Trends Keyword Trend Analysis\n\nThis skill guides you on how to query and analyze Google Trends keyword search interest data, helping users understand how keyword popularity changes over time across different regions.\n\n## Core Concepts\n\nGoogle Trends provides normalized search interest data (0-100 scale) reflecting how popular a given search term is relative to its peak popularity in the selected region and time range. A value of 100 represents peak popularity, 50 means the term is half as popular as its peak, and 0 means insufficient data.\n\n**Important language rule**: Keywords must be in the language of the target country. For example, use English keywords for the US, German keywords for Germany, Japanese keywords for Japan. If the user provides keywords in the wrong language, translate them before querying.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| keyword | string | Yes | The search keyword to analyze (max 100 characters). Must be in the target country's language. |\n| region | string | No | Country/region code. Defaults to `US`. |\n| dayRangeStart | string | No | Start date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n| dayRangeEnd | string | No | End date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n\nWhen both `dayRangeStart` and `dayRangeEnd` are provided, the custom time range takes priority.\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 doesn't specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByKeys`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_keyword.py '' [--inline]`\n- **成本约束**：本工具会消耗算力；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-keys-.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## How to Build Queries\n\n### Principles for Effective Queries\n\n1. **Use the correct language**: Always ensure keywords match the target region's language. Translate first if needed.\n2. **Specify a region**: Default is US, but always confirm the user's intended market.\n3. **Use date ranges for focused analysis**: For seasonal trends or specific event analysis, provide `dayRangeStart` and `dayRangeEnd`.\n4. **Keep keywords concise**: Google Trends works best with short, focused search terms.\n\n### Usage Examples\n\n**1. Basic Keyword Trend (Default Region & Time)**\n```json\n{\"keyword\": \"wireless charger\"}\n```\nQuery the overall search interest trend for \"wireless charger\" in the US.\n\n**2. Keyword Trend in a Specific Region**\n```json\n{\"keyword\": \"Ladekabel\", \"region\": \"DE\"}\n```\nQuery the search interest for \"Ladekabel\" (charging cable) in Germany.\n\n**3. Custom Date Range Analysis**\n```json\n{\"keyword\": \"christmas gifts\", \"region\": \"US\", \"dayRangeStart\": \"2024-09-01\", \"dayRangeEnd\": \"2025-01-31\"}\n```\nAnalyze the seasonal trend of \"christmas gifts\" in the US from September 2024 through January 2025.\n\n**4. Year-over-Year Comparison**\n```json\n{\"keyword\": \"sunscreen\", \"region\": \"AU\", \"dayRangeStart\": \"2023-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\n```\nCompare multi-year seasonality of \"sunscreen\" in Australia.\n\n**5. Regional Market Research**\n```json\n{\"keyword\": \"yoga mat\", \"region\": \"GB\"}\n```\nCheck the popularity trend of \"yoga mat\" in the United Kingdom.\n\n**6. Emerging Trend Detection**\n```json\n{\"keyword\": \"AI glasses\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\n```\nTrack the rise of \"AI glasses\" search interest over the past two years in the US.\n\n## Display Rules\n\n1. **Present data clearly**: Show trend data in well-formatted tables or describe the trend curve. Include key data points such as peak values, troughs, and notable changes.\n2. **Explain the scale**: Remind users that Google Trends values are on a 0-100 normalized scale, where 100 = peak popularity in the selected scope.\n3. **Highlight patterns**: Point out seasonal patterns, sudden spikes, or sustained growth/decline when visible in the data.\n4. **Chart data availability**: When the response includes `chartOption`, mention that visualization data is available and describe the trend shape.\n5. **Error handling**: When a query fails, explain the reason and suggest adjustments (e.g., check keyword spelling, try a different date range, ensure the keyword is in the correct language).\n## Important Limitations\n\n- **Data analysis**: The response is JSON. Read `trendInfoForKeys[].trendValues[]` from the saved response; preserve `timeRange` and values such as `\"<1\"` without converting them to zero. `_dataQuery_executeDynamicQuery` queries Linkfox session data stored in SLS, not arbitrary JSON files; use it only when the required stored-data mapping exists.\n- **Normalized values**: Trend values are relative (0-100), not absolute search volumes.\n- **Data availability**: Data is available from 2004 onward, but very niche terms may have sparse data.\n- **Single keyword per call**: Each API call handles one keyword. For multi-keyword comparisons, make separate calls and compare results.\n- **Language requirement**: Keywords must match the target region's language for accurate results.\n\n## User Expression & Scenario Quick Reference\n\n**Applicable** -- Queries about keyword search popularity trends:\n\n| User Says | Scenario |\n|-----------|----------|\n| \"How popular is XX keyword on Google\" | Basic trend lookup |\n| \"Is XX trending up or down\" | Trend direction analysis |\n| \"When does XX peak in searches\" | Seasonal peak detection |\n| \"Compare popularity of XX across months\" | Seasonal pattern analysis |\n| \"Is XX gaining traction in Germany\" | Regional trend check |\n| \"What's the search trend for XX over the past year\" | Historical trend analysis |\n| \"Holiday search trends for XX\" | Seasonal / event-driven analysis |\n\n**Not applicable** -- Needs beyond Google Trends search interest data:\n\n- Google Ads keyword planner or bid/CPC data\n- Absolute search volume numbers (Google Trends provides relative, not absolute data)\n- Social media trending topics (Twitter/X, TikTok, etc.)\n- Amazon-specific search term data (use ABA Data Explorer instead)\n- Website traffic analytics (Google Analytics, SimilarWeb, etc.)\n- Keyword ranking on search engine result pages (SEO rank tracking)\n\n**Boundary judgment**: When users say \"keyword research\" or \"market trend analysis\", if it specifically relates to search interest popularity over time from Google's perspective, this skill applies. If they want absolute traffic numbers, advertising metrics, or e-commerce-platform-specific data, 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-keys\",\n \"version\": \"1.0.7\",\n \"publishedAt\": 1789363169114\n}\n\nFile v1.0.7:references/api.md\n\n# 谷歌趋势-关键词趋势信息 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByKeys`\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| keyword | string | 是 | 关键词（关键词必须是国家的语言！比如美国要用英语关键词，德国要用德语关键词。如果不是对应国家的语言，请先翻译。）最大长度100字符 |\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| dayRangeStart | string | 否 | 时间范围开始时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n| dayRangeEnd | string | 否 | 时间范围结束时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n\r\n- 当同时提供 `dayRangeStart` 和 `dayRangeEnd` 时，自定义时间范围优先\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| trendInfoForKeys | array | 关键词趋势信息数组 |\r\n| trendInfoForKeys[].keyword | string | 关键词 |\r\n| trendInfoForKeys[].trendValues | array | 趋势值数组 |\r\n| trendInfoForKeys[].trendValues[].timeRange | string | 时间，格式为 yyyy-MM-dd |\r\n| trendInfoForKeys[].trendValues[].value | string | 值（归一化搜索热度，0-100） |\r\n| chartOption | object | 图表渲染元数据 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.data | array | 数据 |\r\n| costToken | integer | 消耗token |\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/getTrendByKeys \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"keyword\": \"wireless charger\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-01-01\"}'\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\nAnalyzes Google Trends keyword search interest by keyword, region, and optional custom date range through LinkFox's Google Trends API.\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 query Google Trends-style search interest and compare keyword popularity over time or across supported regions. It helps identify seasonal patterns, spikes, declines, and relative search interest on a normalized 0-100 scale.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill sends search queries, account identifiers, login flow data, payment actions, and feedback data to LinkFox services.\n\nMitigation: Install and use the skill only when LinkFox is trusted for those data types, and avoid submitting confidential or regulated search terms.\n\nRisk: API keys and full response files may persist locally or in shell configuration.\n\nMitigation: Use scoped credentials where possible, avoid placing API keys in shell startup files, and review or delete saved linkfox response files after use.\n\nRisk: Endpoint override environment variables can redirect traffic away from the documented LinkFox services.\n\nMitigation: Keep default endpoints for normal use and inspect LinkFox-related environment variables before running the scripts.\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-keys)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, JSON files]\n\n**Output Format:** [Markdown guidance with JSON response summaries and saved JSON response files]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Responses may be saved under a local linkfox session directory; small responses may be printed inline, while larger responses are summarized.]\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, 22915 bytes\n\nFiles: references/api.md (4035b), references/onboarding.md (2046b), scripts/google_trends_keyword.py (13092b), scripts/onboarding.py (24089b), skill-card.md (2476b), SKILL.md (9635b), _meta.json (157b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: linkfox-google-trend-get-trend-by-keys\ndescription: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。\n---\n\n# Google Trends Keyword Trend Analysis\n\nThis skill guides you on how to query and analyze Google Trends keyword search interest data, helping users understand how keyword popularity changes over time across different regions.\n\n## Core Concepts\n\nGoogle Trends provides normalized search interest data (0-100 scale) reflecting how popular a given search term is relative to its peak popularity in the selected region and time range. A value of 100 represents peak popularity, 50 means the term is half as popular as its peak, and 0 means insufficient data.\n\n**Important language rule**: Keywords must be in the language of the target country. For example, use English keywords for the US, German keywords for Germany, Japanese keywords for Japan. If the user provides keywords in the wrong language, translate them before querying.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| keyword | string | Yes | The search keyword to analyze (max 100 characters). Must be in the target country's language. |\n| region | string | No | Country/region code. Defaults to `US`. |\n| dayRangeStart | string | No | Start date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n| dayRangeEnd | string | No | End date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n\nWhen both `dayRangeStart` and `dayRangeEnd` are provided, the custom time range takes priority.\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 doesn't specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByKeys`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_keyword.py '' [--inline]`\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-keys-.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## How to Build Queries\n\n### Principles for Effective Queries\n\n1. **Use the correct language**: Always ensure keywords match the target region's language. Translate first if needed.\n2. **Specify a region**: Default is US, but always confirm the user's intended market.\n3. **Use date ranges for focused analysis**: For seasonal trends or specific event analysis, provide `dayRangeStart` and `dayRangeEnd`.\n4. **Keep keywords concise**: Google Trends works best with short, focused search terms.\n\n### Usage Examples\n\n**1. Basic Keyword Trend (Default Region & Time)**\n```json\n{\"keyword\": \"wireless charger\"}\n```\nQuery the overall search interest trend for \"wireless charger\" in the US.\n\n**2. Keyword Trend in a Specific Region**\n```json\n{\"keyword\": \"Ladekabel\", \"region\": \"DE\"}\n```\nQuery the search interest for \"Ladekabel\" (charging cable) in Germany.\n\n**3. Custom Date Range Analysis**\n```json\n{\"keyword\": \"christmas gifts\", \"region\": \"US\", \"dayRangeStart\": \"2024-09-01\", \"dayRangeEnd\": \"2025-01-31\"}\n```\nAnalyze the seasonal trend of \"christmas gifts\" in the US from September 2024 through January 2025.\n\n**4. Year-over-Year Comparison**\n```json\n{\"keyword\": \"sunscreen\", \"region\": \"AU\", \"dayRangeStart\": \"2023-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\n```\nCompare multi-year seasonality of \"sunscreen\" in Australia.\n\n**5. Regional Market Research**\n```json\n{\"keyword\": \"yoga mat\", \"region\": \"GB\"}\n```\nCheck the popularity trend of \"yoga mat\" in the United Kingdom.\n\n**6. Emerging Trend Detection**\n```json\n{\"keyword\": \"AI glasses\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\n```\nTrack the rise of \"AI glasses\" search interest over the past two years in the US.\n\n## Display Rules\n\n1. **Present data clearly**: Show trend data in well-formatted tables or describe the trend curve. Include key data points such as peak values, troughs, and notable changes.\n2. **Explain the scale**: Remind users that Google Trends values are on a 0-100 normalized scale, where 100 = peak popularity in the selected scope.\n3. **Highlight patterns**: Point out seasonal patterns, sudden spikes, or sustained growth/decline when visible in the data.\n4. **Chart data availability**: When the response includes `chartOption`, mention that visualization data is available and describe the trend shape.\n5. **Error handling**: When a query fails, explain the reason and suggest adjustments (e.g., check keyword spelling, try a different date range, ensure the keyword is in the correct language).\n## Important Limitations\n\n- **No secondary SQL processing**: Results from this tool are unstructured and cannot be fed into dynamic query tools for secondary analysis.\n- **Normalized values**: Trend values are relative (0-100), not absolute search volumes.\n- **Data availability**: Data is available from 2004 onward, but very niche terms may have sparse data.\n- **Single keyword per call**: Each API call handles one keyword. For multi-keyword comparisons, make separate calls and compare results.\n- **Language requirement**: Keywords must match the target region's language for accurate results.\n\n## User Expression & Scenario Quick Reference\n\n**Applicable** -- Queries about keyword search popularity trends:\n\n| User Says | Scenario |\n|-----------|----------|\n| \"How popular is XX keyword on Google\" | Basic trend lookup |\n| \"Is XX trending up or down\" | Trend direction analysis |\n| \"When does XX peak in searches\" | Seasonal peak detection |\n| \"Compare popularity of XX across months\" | Seasonal pattern analysis |\n| \"Is XX gaining traction in Germany\" | Regional trend check |\n| \"What's the search trend for XX over the past year\" | Historical trend analysis |\n| \"Holiday search trends for XX\" | Seasonal / event-driven analysis |\n\n**Not applicable** -- Needs beyond Google Trends search interest data:\n\n- Google Ads keyword planner or bid/CPC data\n- Absolute search volume numbers (Google Trends provides relative, not absolute data)\n- Social media trending topics (Twitter/X, TikTok, etc.)\n- Amazon-specific search term data (use ABA Data Explorer instead)\n- Website traffic analytics (Google Analytics, SimilarWeb, etc.)\n- Keyword ranking on search engine result pages (SEO rank tracking)\n\n**Boundary judgment**: When users say \"keyword research\" or \"market trend analysis\", if it specifically relates to search interest popularity over time from Google's perspective, this skill applies. If they want absolute traffic numbers, advertising metrics, or e-commerce-platform-specific data, 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-keys\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1786719251644\n}\n\nFile v1.0.6:references/api.md\n\n# 谷歌趋势-关键词趋势信息 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByKeys`\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| keyword | string | 是 | 关键词（关键词必须是国家的语言！比如美国要用英语关键词，德国要用德语关键词。如果不是对应国家的语言，请先翻译。）最大长度100字符 |\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| dayRangeStart | string | 否 | 时间范围开始时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n| dayRangeEnd | string | 否 | 时间范围结束时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n\r\n- 当同时提供 `dayRangeStart` 和 `dayRangeEnd` 时，自定义时间范围优先\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| trendInfoForKeys | array | 关键词趋势信息数组 |\r\n| trendInfoForKeys[].keyword | string | 关键词 |\r\n| trendInfoForKeys[].trendValues | array | 趋势值数组 |\r\n| trendInfoForKeys[].trendValues[].timeRange | string | 时间，格式为 yyyy-MM-dd |\r\n| trendInfoForKeys[].trendValues[].value | string | 值（归一化搜索热度，0-100） |\r\n| chartOption | object | 图表渲染元数据 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.data | array | 数据 |\r\n| costToken | integer | 消耗token |\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/getTrendByKeys \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"keyword\": \"wireless charger\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-01-01\"}'\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\nGoogle Trends keyword trend analysis for comparing normalized search interest by keyword, region, and custom date range.\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 query Google Trends-style keyword interest, compare regional or seasonal patterns, and present normalized trend values for market or keyword research.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill sends keyword requests and possible feedback content to LinkFox services.\n\nMitigation: Install only if third-party processing by LinkFox is acceptable for the intended queries, and avoid submitting sensitive keywords or feedback content.\n\nRisk: The skill uses API keys and includes phone/SMS onboarding flows for account access.\n\nMitigation: Prefer temporary environment variables or a secret manager for API keys, and run onboarding commands only when explicitly intended.\n\nRisk: The skill can initiate billing flows and credit-consuming API calls.\n\nMitigation: Confirm expected credit use before repeated calls and review any payment or plan-selection command before execution.\n\nRisk: The skill writes query outputs and cache data under a local linkfox directory.\n\nMitigation: Clear local linkfox output and cache directories after use when queries or results are sensitive.\n\n## Reference(s):\n\n- [谷歌趋势-关键词趋势信息 API 参考](references/api.md)\n- [解决认证和积分问题](references/onboarding.md)\n- [ClawHub skill page](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-keys)\n- [LinkFox Skills](https://skill.linkfox.com/)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with JSON API results and saved result files]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Google Trends values are normalized to a 0-100 scale; each tool call handles one keyword and may consume LinkFox credits.]\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, 22919 bytes\n\nFiles: references/api.md (4035b), references/onboarding.md (2046b), scripts/google_trends_keyword.py (13092b), scripts/onboarding.py (24089b), skill-card.md (2783b), SKILL.md (9635b), _meta.json (157b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: linkfox-google-trend-get-trend-by-keys\ndescription: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。\n---\n\n# Google Trends Keyword Trend Analysis\n\nThis skill guides you on how to query and analyze Google Trends keyword search interest data, helping users understand how keyword popularity changes over time across different regions.\n\n## Core Concepts\n\nGoogle Trends provides normalized search interest data (0-100 scale) reflecting how popular a given search term is relative to its peak popularity in the selected region and time range. A value of 100 represents peak popularity, 50 means the term is half as popular as its peak, and 0 means insufficient data.\n\n**Important language rule**: Keywords must be in the language of the target country. For example, use English keywords for the US, German keywords for Germany, Japanese keywords for Japan. If the user provides keywords in the wrong language, translate them before querying.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| keyword | string | Yes | The search keyword to analyze (max 100 characters). Must be in the target country's language. |\n| region | string | No | Country/region code. Defaults to `US`. |\n| dayRangeStart | string | No | Start date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n| dayRangeEnd | string | No | End date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n\nWhen both `dayRangeStart` and `dayRangeEnd` are provided, the custom time range takes priority.\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 doesn't specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByKeys`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_keyword.py '' [--inline]`\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-keys-.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## How to Build Queries\n\n### Principles for Effective Queries\n\n1. **Use the correct language**: Always ensure keywords match the target region's language. Translate first if needed.\n2. **Specify a region**: Default is US, but always confirm the user's intended market.\n3. **Use date ranges for focused analysis**: For seasonal trends or specific event analysis, provide `dayRangeStart` and `dayRangeEnd`.\n4. **Keep keywords concise**: Google Trends works best with short, focused search terms.\n\n### Usage Examples\n\n**1. Basic Keyword Trend (Default Region & Time)**\n```json\n{\"keyword\": \"wireless charger\"}\n```\nQuery the overall search interest trend for \"wireless charger\" in the US.\n\n**2. Keyword Trend in a Specific Region**\n```json\n{\"keyword\": \"Ladekabel\", \"region\": \"DE\"}\n```\nQuery the search interest for \"Ladekabel\" (charging cable) in Germany.\n\n**3. Custom Date Range Analysis**\n```json\n{\"keyword\": \"christmas gifts\", \"region\": \"US\", \"dayRangeStart\": \"2024-09-01\", \"dayRangeEnd\": \"2025-01-31\"}\n```\nAnalyze the seasonal trend of \"christmas gifts\" in the US from September 2024 through January 2025.\n\n**4. Year-over-Year Comparison**\n```json\n{\"keyword\": \"sunscreen\", \"region\": \"AU\", \"dayRangeStart\": \"2023-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\n```\nCompare multi-year seasonality of \"sunscreen\" in Australia.\n\n**5. Regional Market Research**\n```json\n{\"keyword\": \"yoga mat\", \"region\": \"GB\"}\n```\nCheck the popularity trend of \"yoga mat\" in the United Kingdom.\n\n**6. Emerging Trend Detection**\n```json\n{\"keyword\": \"AI glasses\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\n```\nTrack the rise of \"AI glasses\" search interest over the past two years in the US.\n\n## Display Rules\n\n1. **Present data clearly**: Show trend data in well-formatted tables or describe the trend curve. Include key data points such as peak values, troughs, and notable changes.\n2. **Explain the scale**: Remind users that Google Trends values are on a 0-100 normalized scale, where 100 = peak popularity in the selected scope.\n3. **Highlight patterns**: Point out seasonal patterns, sudden spikes, or sustained growth/decline when visible in the data.\n4. **Chart data availability**: When the response includes `chartOption`, mention that visualization data is available and describe the trend shape.\n5. **Error handling**: When a query fails, explain the reason and suggest adjustments (e.g., check keyword spelling, try a different date range, ensure the keyword is in the correct language).\n## Important Limitations\n\n- **No secondary SQL processing**: Results from this tool are unstructured and cannot be fed into dynamic query tools for secondary analysis.\n- **Normalized values**: Trend values are relative (0-100), not absolute search volumes.\n- **Data availability**: Data is available from 2004 onward, but very niche terms may have sparse data.\n- **Single keyword per call**: Each API call handles one keyword. For multi-keyword comparisons, make separate calls and compare results.\n- **Language requirement**: Keywords must match the target region's language for accurate results.\n\n## User Expression & Scenario Quick Reference\n\n**Applicable** -- Queries about keyword search popularity trends:\n\n| User Says | Scenario |\n|-----------|----------|\n| \"How popular is XX keyword on Google\" | Basic trend lookup |\n| \"Is XX trending up or down\" | Trend direction analysis |\n| \"When does XX peak in searches\" | Seasonal peak detection |\n| \"Compare popularity of XX across months\" | Seasonal pattern analysis |\n| \"Is XX gaining traction in Germany\" | Regional trend check |\n| \"What's the search trend for XX over the past year\" | Historical trend analysis |\n| \"Holiday search trends for XX\" | Seasonal / event-driven analysis |\n\n**Not applicable** -- Needs beyond Google Trends search interest data:\n\n- Google Ads keyword planner or bid/CPC data\n- Absolute search volume numbers (Google Trends provides relative, not absolute data)\n- Social media trending topics (Twitter/X, TikTok, etc.)\n- Amazon-specific search term data (use ABA Data Explorer instead)\n- Website traffic analytics (Google Analytics, SimilarWeb, etc.)\n- Keyword ranking on search engine result pages (SEO rank tracking)\n\n**Boundary judgment**: When users say \"keyword research\" or \"market trend analysis\", if it specifically relates to search interest popularity over time from Google's perspective, this skill applies. If they want absolute traffic numbers, advertising metrics, or e-commerce-platform-specific data, 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-keys\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1786099784113\n}\n\nFile v1.0.5:references/api.md\n\n# 谷歌趋势-关键词趋势信息 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByKeys`\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| keyword | string | 是 | 关键词（关键词必须是国家的语言！比如美国要用英语关键词，德国要用德语关键词。如果不是对应国家的语言，请先翻译。）最大长度100字符 |\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| dayRangeStart | string | 否 | 时间范围开始时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n| dayRangeEnd | string | 否 | 时间范围结束时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n\r\n- 当同时提供 `dayRangeStart` 和 `dayRangeEnd` 时，自定义时间范围优先\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| trendInfoForKeys | array | 关键词趋势信息数组 |\r\n| trendInfoForKeys[].keyword | string | 关键词 |\r\n| trendInfoForKeys[].trendValues | array | 趋势值数组 |\r\n| trendInfoForKeys[].trendValues[].timeRange | string | 时间，格式为 yyyy-MM-dd |\r\n| trendInfoForKeys[].trendValues[].value | string | 值（归一化搜索热度，0-100） |\r\n| chartOption | object | 图表渲染元数据 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.data | array | 数据 |\r\n| costToken | integer | 消耗token |\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/getTrendByKeys \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"keyword\": \"wireless charger\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-01-01\"}'\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 Google Trends keyword search-interest data through LinkFox and helps agents summarize normalized keyword trends by region and date range.\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, market researchers, and commerce operators use this skill to retrieve normalized Google Trends keyword interest data and analyze trend direction, seasonality, peaks, and regional search-interest patterns.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill uses LinkFox as a paid external service and each trend query consumes credits.\n\nMitigation: Tell users when a call will spend credits, avoid repeated exploratory calls for the same task, and get explicit approval before initiating payment or order flows.\n\nRisk: Keyword queries, account details, and feedback content may be sent to LinkFox services.\n\nMitigation: Avoid sending sensitive user content through trend queries or feedback, and review endpoint environment variables before use.\n\nRisk: The scripts can persist API responses, setup metadata, and payment QR output under a local linkfox directory.\n\nMitigation: Run the skill only in an expected workspace, protect API keys in environment variables, and remove local response or setup files when retention is not needed.\n\nRisk: Onboarding helpers can perform phone signup, API key generation, plan listing, and payment order creation.\n\nMitigation: Require explicit user approval before phone signup, API key generation, plan selection, or payment order steps.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-keys)\n- [Publisher profile](https://clawhub.ai/user/linkfox-ai)\n- [Google Trends keyword API reference](references/api.md)\n- [Authentication and billing onboarding](references/onboarding.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, json, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown trend summaries, JSON API responses, and shell commands or configuration snippets for setup and billing flows]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Trend results use a normalized 0-100 scale, full responses are saved locally, repeated identical calls may use a 24-hour cache, and each trend query consumes 6 credits.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release metadata)\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, 14095 bytes\n\nFiles: references/api.md (4035b), scripts/google_trends_keyword.py (13092b), skill-card.md (2654b), SKILL.md (10252b), _meta.json (157b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: linkfox-google-trend-get-trend-by-keys\ndescription: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。\n---\n\n# Google Trends Keyword Trend Analysis\n\nThis skill guides you on how to query and analyze Google Trends keyword search interest data, helping users understand how keyword popularity changes over time across different regions.\n\n## Core Concepts\n\nGoogle Trends provides normalized search interest data (0-100 scale) reflecting how popular a given search term is relative to its peak popularity in the selected region and time range. A value of 100 represents peak popularity, 50 means the term is half as popular as its peak, and 0 means insufficient data.\n\n**Important language rule**: Keywords must be in the language of the target country. For example, use English keywords for the US, German keywords for Germany, Japanese keywords for Japan. If the user provides keywords in the wrong language, translate them before querying.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| keyword | string | Yes | The search keyword to analyze (max 100 characters). Must be in the target country's language. |\n| region | string | No | Country/region code. Defaults to `US`. |\n| dayRangeStart | string | No | Start date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n| dayRangeEnd | string | No | End date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n\nWhen both `dayRangeStart` and `dayRangeEnd` are provided, the custom time range takes priority.\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 doesn't specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByKeys`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_keyword.py '' [--inline]`\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-keys-.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## How to Build Queries\n\n### Principles for Effective Queries\n\n1. **Use the correct language**: Always ensure keywords match the target region's language. Translate first if needed.\n2. **Specify a region**: Default is US, but always confirm the user's intended market.\n3. **Use date ranges for focused analysis**: For seasonal trends or specific event analysis, provide `dayRangeStart` and `dayRangeEnd`.\n4. **Keep keywords concise**: Google Trends works best with short, focused search terms.\n\n### Usage Examples\n\n**1. Basic Keyword Trend (Default Region & Time)**\n```json\n{\"keyword\": \"wireless charger\"}\n```\nQuery the overall search interest trend for \"wireless charger\" in the US.\n\n**2. Keyword Trend in a Specific Region**\n```json\n{\"keyword\": \"Ladekabel\", \"region\": \"DE\"}\n```\nQuery the search interest for \"Ladekabel\" (charging cable) in Germany.\n\n**3. Custom Date Range Analysis**\n```json\n{\"keyword\": \"christmas gifts\", \"region\": \"US\", \"dayRangeStart\": \"2024-09-01\", \"dayRangeEnd\": \"2025-01-31\"}\n```\nAnalyze the seasonal trend of \"christmas gifts\" in the US from September 2024 through January 2025.\n\n**4. Year-over-Year Comparison**\n```json\n{\"keyword\": \"sunscreen\", \"region\": \"AU\", \"dayRangeStart\": \"2023-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\n```\nCompare multi-year seasonality of \"sunscreen\" in Australia.\n\n**5. Regional Market Research**\n```json\n{\"keyword\": \"yoga mat\", \"region\": \"GB\"}\n```\nCheck the popularity trend of \"yoga mat\" in the United Kingdom.\n\n**6. Emerging Trend Detection**\n```json\n{\"keyword\": \"AI glasses\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\n```\nTrack the rise of \"AI glasses\" search interest over the past two years in the US.\n\n## Display Rules\n\n1. **Present data clearly**: Show trend data in well-formatted tables or describe the trend curve. Include key data points such as peak values, troughs, and notable changes.\n2. **Explain the scale**: Remind users that Google Trends values are on a 0-100 normalized scale, where 100 = peak popularity in the selected scope.\n3. **Highlight patterns**: Point out seasonal patterns, sudden spikes, or sustained growth/decline when visible in the data.\n4. **Chart data availability**: When the response includes `chartOption`, mention that visualization data is available and describe the trend shape.\n5. **Error handling**: When a query fails, explain the reason and suggest adjustments (e.g., check keyword spelling, try a different date range, ensure the keyword is in the correct language).\n## Important Limitations\n\n- **No secondary SQL processing**: Results from this tool are unstructured and cannot be fed into dynamic query tools for secondary analysis.\n- **Normalized values**: Trend values are relative (0-100), not absolute search volumes.\n- **Data availability**: Data is available from 2004 onward, but very niche terms may have sparse data.\n- **Single keyword per call**: Each API call handles one keyword. For multi-keyword comparisons, make separate calls and compare results.\n- **Language requirement**: Keywords must match the target region's language for accurate results.\n\n## User Expression & Scenario Quick Reference\n\n**Applicable** -- Queries about keyword search popularity trends:\n\n| User Says | Scenario |\n|-----------|----------|\n| \"How popular is XX keyword on Google\" | Basic trend lookup |\n| \"Is XX trending up or down\" | Trend direction analysis |\n| \"When does XX peak in searches\" | Seasonal peak detection |\n| \"Compare popularity of XX across months\" | Seasonal pattern analysis |\n| \"Is XX gaining traction in Germany\" | Regional trend check |\n| \"What's the search trend for XX over the past year\" | Historical trend analysis |\n| \"Holiday search trends for XX\" | Seasonal / event-driven analysis |\n\n**Not applicable** -- Needs beyond Google Trends search interest data:\n\n- Google Ads keyword planner or bid/CPC data\n- Absolute search volume numbers (Google Trends provides relative, not absolute data)\n- Social media trending topics (Twitter/X, TikTok, etc.)\n- Amazon-specific search term data (use ABA Data Explorer instead)\n- Website traffic analytics (Google Analytics, SimilarWeb, etc.)\n- Keyword ranking on search engine result pages (SEO rank tracking)\n\n**Boundary judgment**: When users say \"keyword research\" or \"market trend analysis\", if it specifically relates to search interest popularity over time from Google's perspective, this skill applies. If they want absolute traffic numbers, advertising metrics, or e-commerce-platform-specific data, 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-keys\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1783944638420\n}\n\nFile v1.0.4:references/api.md\n\n# 谷歌趋势-关键词趋势信息 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByKeys`\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| keyword | string | 是 | 关键词（关键词必须是国家的语言！比如美国要用英语关键词，德国要用德语关键词。如果不是对应国家的语言，请先翻译。）最大长度100字符 |\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| dayRangeStart | string | 否 | 时间范围开始时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n| dayRangeEnd | string | 否 | 时间范围结束时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n\r\n- 当同时提供 `dayRangeStart` 和 `dayRangeEnd` 时，自定义时间范围优先\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| trendInfoForKeys | array | 关键词趋势信息数组 |\r\n| trendInfoForKeys[].keyword | string | 关键词 |\r\n| trendInfoForKeys[].trendValues | array | 趋势值数组 |\r\n| trendInfoForKeys[].trendValues[].timeRange | string | 时间，格式为 yyyy-MM-dd |\r\n| trendInfoForKeys[].trendValues[].value | string | 值（归一化搜索热度，0-100） |\r\n| chartOption | object | 图表渲染元数据 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.data | array | 数据 |\r\n| costToken | integer | 消耗token |\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/getTrendByKeys \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"keyword\": \"wireless charger\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-01-01\"}'\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 LinkFox Google Trends keyword trend data to analyze normalized search interest over time by keyword, supported region, and optional date range.
\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 and developers use this skill to request Google Trends normalized search-interest data for keyword and market trend analysis across supported regions and date ranges. It helps an agent present trend values, peaks, troughs, seasonality, and relevant caveats for the selected keyword.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: LinkFox may receive keyword queries, API credentials, session or app metadata, and possible feedback content.
\nMitigation: Use an approved LinkFox account and API key, avoid sensitive keywords or feedback content, and keep the gateway pinned to the official LinkFox host.
\nRisk: Authentication or quota failures can lead to a remote onboarding-skill installation path.
\nMitigation: Review or disable the remote onboarding path before deployment, and require explicit user authorization before downloading or installing onboarding assets.
\nRisk: Responses and cache entries are retained in local linkfox data directories.
\nMitigation: Confirm that saved response and cache directories are acceptable for the workspace, and clean them according to local data retention policy.
\n\n\n## Reference(s):
\n- [谷歌趋势-关键词趋势信息 API 参考](artifact/references/api.md)
\n- [ClawHub skill page](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-keys)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, JSON, Files, Guidance]
\n**Output Format:** [Markdown guidance with shell command examples and JSON API responses; full responses are saved as JSON files and small responses may print inline.]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Accepts one keyword plus optional region and date range; uses a 24-hour local cache and summarizes responses larger than 8 KB unless inline output is requested.]
\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, 13422 bytes\n\nFiles: references/api.md (3913b), scripts/google_trends_keyword.py (13183b), skill-card.md (2813b), SKILL.md (9075b), _meta.json (157b)\n\nFile v1.0.3:SKILL.md\n\n---\r\nname: linkfox-google-trend-get-trend-by-keys\r\ndescription: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。\r\n---\r\n\r\n# Google Trends Keyword Trend Analysis\r\n\r\nThis skill guides you on how to query and analyze Google Trends keyword search interest data, helping users understand how keyword popularity changes over time across different regions.\r\n\r\n## Core Concepts\r\n\r\nGoogle Trends provides normalized search interest data (0-100 scale) reflecting how popular a given search term is relative to its peak popularity in the selected region and time range. A value of 100 represents peak popularity, 50 means the term is half as popular as its peak, and 0 means insufficient data.\r\n\r\n**Important language rule**: Keywords must be in the language of the target country. For example, use English keywords for the US, German keywords for Germany, Japanese keywords for Japan. If the user provides keywords in the wrong language, translate them before querying.\r\n\r\n## Parameters\r\n\r\n| Parameter | Type | Required | Description |\r\n|-----------|------|----------|-------------|\r\n| keyword | string | Yes | The search keyword to analyze (max 100 characters). Must be in the target country's language. |\r\n| region | string | No | Country/region code. Defaults to `US`. |\r\n| dayRangeStart | string | No | Start date for the time range (format: YYYY-MM-DD, from 2004 onward). |\r\n| dayRangeEnd | string | No | End date for the time range (format: YYYY-MM-DD, from 2004 onward). |\r\n\r\nWhen both `dayRangeStart` and `dayRangeEnd` are provided, the custom time range takes priority.\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 doesn't specify a region.\r\n\r\n## 调用方式\r\n\r\n- **API 端点**：`POST /googleTrend/getTrendByKeys`（完整参数/响应/错误码见 `references/api.md`）\r\n- **Python 脚本**：`python scripts/google_trends_keyword.py '' [--inline]`\r\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\r\n\r\n**输出策略（脚本默认行为）**：\r\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-keys-.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## How to Build Queries\r\n\r\n### Principles for Effective Queries\r\n\r\n1. **Use the correct language**: Always ensure keywords match the target region's language. Translate first if needed.\r\n2. **Specify a region**: Default is US, but always confirm the user's intended market.\r\n3. **Use date ranges for focused analysis**: For seasonal trends or specific event analysis, provide `dayRangeStart` and `dayRangeEnd`.\r\n4. **Keep keywords concise**: Google Trends works best with short, focused search terms.\r\n\r\n### Usage Examples\r\n\r\n**1. Basic Keyword Trend (Default Region & Time)**\r\n```json\r\n{\"keyword\": \"wireless charger\"}\r\n```\r\nQuery the overall search interest trend for \"wireless charger\" in the US.\r\n\r\n**2. Keyword Trend in a Specific Region**\r\n```json\r\n{\"keyword\": \"Ladekabel\", \"region\": \"DE\"}\r\n```\r\nQuery the search interest for \"Ladekabel\" (charging cable) in Germany.\r\n\r\n**3. Custom Date Range Analysis**\r\n```json\r\n{\"keyword\": \"christmas gifts\", \"region\": \"US\", \"dayRangeStart\": \"2024-09-01\", \"dayRangeEnd\": \"2025-01-31\"}\r\n```\r\nAnalyze the seasonal trend of \"christmas gifts\" in the US from September 2024 through January 2025.\r\n\r\n**4. Year-over-Year Comparison**\r\n```json\r\n{\"keyword\": \"sunscreen\", \"region\": \"AU\", \"dayRangeStart\": \"2023-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\r\n```\r\nCompare multi-year seasonality of \"sunscreen\" in Australia.\r\n\r\n**5. Regional Market Research**\r\n```json\r\n{\"keyword\": \"yoga mat\", \"region\": \"GB\"}\r\n```\r\nCheck the popularity trend of \"yoga mat\" in the United Kingdom.\r\n\r\n**6. Emerging Trend Detection**\r\n```json\r\n{\"keyword\": \"AI glasses\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\r\n```\r\nTrack the rise of \"AI glasses\" search interest over the past two years in the US.\r\n\r\n## Display Rules\r\n\r\n1. **Present data clearly**: Show trend data in well-formatted tables or describe the trend curve. Include key data points such as peak values, troughs, and notable changes.\r\n2. **Explain the scale**: Remind users that Google Trends values are on a 0-100 normalized scale, where 100 = peak popularity in the selected scope.\r\n3. **Highlight patterns**: Point out seasonal patterns, sudden spikes, or sustained growth/decline when visible in the data.\r\n4. **Chart data availability**: When the response includes `chartOption`, mention that visualization data is available and describe the trend shape.\r\n5. **Error handling**: When a query fails, explain the reason and suggest adjustments (e.g., check keyword spelling, try a different date range, ensure the keyword is in the correct language).\r\n## Important Limitations\r\n\r\n- **No secondary SQL processing**: Results from this tool are unstructured and cannot be fed into dynamic query tools for secondary analysis.\r\n- **Normalized values**: Trend values are relative (0-100), not absolute search volumes.\r\n- **Data availability**: Data is available from 2004 onward, but very niche terms may have sparse data.\r\n- **Single keyword per call**: Each API call handles one keyword. For multi-keyword comparisons, make separate calls and compare results.\r\n- **Language requirement**: Keywords must match the target region's language for accurate results.\r\n\r\n## User Expression & Scenario Quick Reference\r\n\r\n**Applicable** -- Queries about keyword search popularity trends:\r\n\r\n| User Says | Scenario |\r\n|-----------|----------|\r\n| \"How popular is XX keyword on Google\" | Basic trend lookup |\r\n| \"Is XX trending up or down\" | Trend direction analysis |\r\n| \"When does XX peak in searches\" | Seasonal peak detection |\r\n| \"Compare popularity of XX across months\" | Seasonal pattern analysis |\r\n| \"Is XX gaining traction in Germany\" | Regional trend check |\r\n| \"What's the search trend for XX over the past year\" | Historical trend analysis |\r\n| \"Holiday search trends for XX\" | Seasonal / event-driven analysis |\r\n\r\n**Not applicable** -- Needs beyond Google Trends search interest data:\r\n\r\n- Google Ads keyword planner or bid/CPC data\r\n- Absolute search volume numbers (Google Trends provides relative, not absolute data)\r\n- Social media trending topics (Twitter/X, TikTok, etc.)\r\n- Amazon-specific search term data (use ABA Data Explorer instead)\r\n- Website traffic analytics (Google Analytics, SimilarWeb, etc.)\r\n- Keyword ranking on search engine result pages (SEO rank tracking)\r\n\r\n**Boundary judgment**: When users say \"keyword research\" or \"market trend analysis\", if it specifically relates to search interest popularity over time from Google's perspective, this skill applies. If they want absolute traffic numbers, advertising metrics, or e-commerce-platform-specific data, 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-keys\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1783336775985\n}\n\nFile v1.0.3:references/api.md\n\n# 谷歌趋势-关键词趋势信息 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByKeys`\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| keyword | string | 是 | 关键词（关键词必须是国家的语言！比如美国要用英语关键词，德国要用德语关键词。如果不是对应国家的语言，请先翻译。）最大长度100字符 |\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| dayRangeStart | string | 否 | 时间范围开始时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n| dayRangeEnd | string | 否 | 时间范围结束时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n\r\n- 当同时提供 `dayRangeStart` 和 `dayRangeEnd` 时，自定义时间范围优先\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| trendInfoForKeys | array | 关键词趋势信息数组 |\r\n| trendInfoForKeys[].keyword | string | 关键词 |\r\n| trendInfoForKeys[].trendValues | array | 趋势值数组 |\r\n| trendInfoForKeys[].trendValues[].timeRange | string | 时间，格式为 yyyy-MM-dd |\r\n| trendInfoForKeys[].trendValues[].value | string | 值（归一化搜索热度，0-100） |\r\n| chartOption | object | 图表渲染元数据 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.data | array | 数据 |\r\n| costToken | integer | 消耗token |\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/getTrendByKeys \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"keyword\": \"wireless charger\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-01-01\"}'\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:
\nLooks up Google Trends keyword search-interest data for a keyword, region, and optional date range, then helps agents summarize trend direction, seasonality, peaks, troughs, and regional interest.
\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:
\nDevelopers and agents use this skill when a user asks for Google Trends-style keyword popularity, seasonality, or search-interest comparisons over time or across supported regions. It is suited for market research and keyword trend analysis where normalized relative interest is sufficient.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Keyword queries and authenticated requests are sent to LinkFox services.
\nMitigation: Use the skill only when the user accepts LinkFox handling the query, avoid sensitive business or personal terms unless approved, and keep API keys in environment variables.
\nRisk: Full API responses are saved locally by default and may include query context or returned trend data.
\nMitigation: Review the generated linkfox session files before sharing or committing workspace contents, and delete saved responses that are no longer needed.
\nRisk: The tool gateway can be overridden with LINKFOX_TOOL_GATEWAY.
\nMitigation: Leave LINKFOX_TOOL_GATEWAY unset unless the replacement host is explicitly trusted.
\nRisk: The skill asks agents to send automatic feedback to an external endpoint.
\nMitigation: Do not submit feedback that includes secrets, personal data, or sensitive business context without explicit user approval.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/linkfox-ai/skills/linkfox-google-trend-get-trend-by-keys)
\n- [API reference](references/api.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, code, configuration, guidance]
\n**Output Format:** [Markdown guidance with JSON parameters, shell command examples, saved JSON response files, and summarized trend analysis.]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [The script caches identical requests for 24 hours, saves full API responses under a local linkfox session directory, and may print either full JSON or a compact summary depending on response size.]
\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, 11962 bytes\n\nFiles: references/api.md (3913b), scripts/google_trends_keyword.py (13183b), SKILL.md (9075b), _meta.json (157b)\n\nFile v1.0.2:SKILL.md\n\n---\r\nname: linkfox-google-trend-get-trend-by-keys\r\ndescription: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。\r\n---\r\n\r\n# Google Trends Keyword Trend Analysis\r\n\r\nThis skill guides you on how to query and analyze Google Trends keyword search interest data, helping users understand how keyword popularity changes over time across different regions.\r\n\r\n## Core Concepts\r\n\r\nGoogle Trends provides normalized search interest data (0-100 scale) reflecting how popular a given search term is relative to its peak popularity in the selected region and time range. A value of 100 represents peak popularity, 50 means the term is half as popular as its peak, and 0 means insufficient data.\r\n\r\n**Important language rule**: Keywords must be in the language of the target country. For example, use English keywords for the US, German keywords for Germany, Japanese keywords for Japan. If the user provides keywords in the wrong language, translate them before querying.\r\n\r\n## Parameters\r\n\r\n| Parameter | Type | Required | Description |\r\n|-----------|------|----------|-------------|\r\n| keyword | string | Yes | The search keyword to analyze (max 100 characters). Must be in the target country's language. |\r\n| region | string | No | Country/region code. Defaults to `US`. |\r\n| dayRangeStart | string | No | Start date for the time range (format: YYYY-MM-DD, from 2004 onward). |\r\n| dayRangeEnd | string | No | End date for the time range (format: YYYY-MM-DD, from 2004 onward). |\r\n\r\nWhen both `dayRangeStart` and `dayRangeEnd` are provided, the custom time range takes priority.\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 doesn't specify a region.\r\n\r\n## 调用方式\r\n\r\n- **API 端点**：`POST /googleTrend/getTrendByKeys`（完整参数/响应/错误码见 `references/api.md`）\r\n- **Python 脚本**：`python scripts/google_trends_keyword.py '' [--inline]`\r\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\r\n\r\n**输出策略（脚本默认行为）**：\r\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-keys-.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## How to Build Queries\r\n\r\n### Principles for Effective Queries\r\n\r\n1. **Use the correct language**: Always ensure keywords match the target region's language. Translate first if needed.\r\n2. **Specify a region**: Default is US, but always confirm the user's intended market.\r\n3. **Use date ranges for focused analysis**: For seasonal trends or specific event analysis, provide `dayRangeStart` and `dayRangeEnd`.\r\n4. **Keep keywords concise**: Google Trends works best with short, focused search terms.\r\n\r\n### Usage Examples\r\n\r\n**1. Basic Keyword Trend (Default Region & Time)**\r\n```json\r\n{\"keyword\": \"wireless charger\"}\r\n```\r\nQuery the overall search interest trend for \"wireless charger\" in the US.\r\n\r\n**2. Keyword Trend in a Specific Region**\r\n```json\r\n{\"keyword\": \"Ladekabel\", \"region\": \"DE\"}\r\n```\r\nQuery the search interest for \"Ladekabel\" (charging cable) in Germany.\r\n\r\n**3. Custom Date Range Analysis**\r\n```json\r\n{\"keyword\": \"christmas gifts\", \"region\": \"US\", \"dayRangeStart\": \"2024-09-01\", \"dayRangeEnd\": \"2025-01-31\"}\r\n```\r\nAnalyze the seasonal trend of \"christmas gifts\" in the US from September 2024 through January 2025.\r\n\r\n**4. Year-over-Year Comparison**\r\n```json\r\n{\"keyword\": \"sunscreen\", \"region\": \"AU\", \"dayRangeStart\": \"2023-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\r\n```\r\nCompare multi-year seasonality of \"sunscreen\" in Australia.\r\n\r\n**5. Regional Market Research**\r\n```json\r\n{\"keyword\": \"yoga mat\", \"region\": \"GB\"}\r\n```\r\nCheck the popularity trend of \"yoga mat\" in the United Kingdom.\r\n\r\n**6. Emerging Trend Detection**\r\n```json\r\n{\"keyword\": \"AI glasses\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\r\n```\r\nTrack the rise of \"AI glasses\" search interest over the past two years in the US.\r\n\r\n## Display Rules\r\n\r\n1. **Present data clearly**: Show trend data in well-formatted tables or describe the trend curve. Include key data points such as peak values, troughs, and notable changes.\r\n2. **Explain the scale**: Remind users that Google Trends values are on a 0-100 normalized scale, where 100 = peak popularity in the selected scope.\r\n3. **Highlight patterns**: Point out seasonal patterns, sudden spikes, or sustained growth/decline when visible in the data.\r\n4. **Chart data availability**: When the response includes `chartOption`, mention that visualization data is available and describe the trend shape.\r\n5. **Error handling**: When a query fails, explain the reason and suggest adjustments (e.g., check keyword spelling, try a different date range, ensure the keyword is in the correct language).\r\n## Important Limitations\r\n\r\n- **No secondary SQL processing**: Results from this tool are unstructured and cannot be fed into dynamic query tools for secondary analysis.\r\n- **Normalized values**: Trend values are relative (0-100), not absolute search volumes.\r\n- **Data availability**: Data is available from 2004 onward, but very niche terms may have sparse data.\r\n- **Single keyword per call**: Each API call handles one keyword. For multi-keyword comparisons, make separate calls and compare results.\r\n- **Language requirement**: Keywords must match the target region's language for accurate results.\r\n\r\n## User Expression & Scenario Quick Reference\r\n\r\n**Applicable** -- Queries about keyword search popularity trends:\r\n\r\n| User Says | Scenario |\r\n|-----------|----------|\r\n| \"How popular is XX keyword on Google\" | Basic trend lookup |\r\n| \"Is XX trending up or down\" | Trend direction analysis |\r\n| \"When does XX peak in searches\" | Seasonal peak detection |\r\n| \"Compare popularity of XX across months\" | Seasonal pattern analysis |\r\n| \"Is XX gaining traction in Germany\" | Regional trend check |\r\n| \"What's the search trend for XX over the past year\" | Historical trend analysis |\r\n| \"Holiday search trends for XX\" | Seasonal / event-driven analysis |\r\n\r\n**Not applicable** -- Needs beyond Google Trends search interest data:\r\n\r\n- Google Ads keyword planner or bid/CPC data\r\n- Absolute search volume numbers (Google Trends provides relative, not absolute data)\r\n- Social media trending topics (Twitter/X, TikTok, etc.)\r\n- Amazon-specific search term data (use ABA Data Explorer instead)\r\n- Website traffic analytics (Google Analytics, SimilarWeb, etc.)\r\n- Keyword ranking on search engine result pages (SEO rank tracking)\r\n\r\n**Boundary judgment**: When users say \"keyword research\" or \"market trend analysis\", if it specifically relates to search interest popularity over time from Google's perspective, this skill applies. If they want absolute traffic numbers, advertising metrics, or e-commerce-platform-specific data, 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-keys\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1783066703965\n}\n\nFile v1.0.2:references/api.md\n\n# 谷歌趋势-关键词趋势信息 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByKeys`\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| keyword | string | 是 | 关键词（关键词必须是国家的语言！比如美国要用英语关键词，德国要用德语关键词。如果不是对应国家的语言，请先翻译。）最大长度100字符 |\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| dayRangeStart | string | 否 | 时间范围开始时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n| dayRangeEnd | string | 否 | 时间范围结束时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n\r\n- 当同时提供 `dayRangeStart` 和 `dayRangeEnd` 时，自定义时间范围优先\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| trendInfoForKeys | array | 关键词趋势信息数组 |\r\n| trendInfoForKeys[].keyword | string | 关键词 |\r\n| trendInfoForKeys[].trendValues | array | 趋势值数组 |\r\n| trendInfoForKeys[].trendValues[].timeRange | string | 时间，格式为 yyyy-MM-dd |\r\n| trendInfoForKeys[].trendValues[].value | string | 值（归一化搜索热度，0-100） |\r\n| chartOption | object | 图表渲染元数据 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.data | array | 数据 |\r\n| costToken | integer | 消耗token |\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/getTrendByKeys \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"keyword\": \"wireless charger\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-01-01\"}'\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, 11941 bytes\n\nFiles: references/api.md (3914b), scripts/google_trends_keyword.py (13185b), SKILL.md (9075b), _meta.json (157b)\n\nFile v1.0.1:SKILL.md\n\n---\r\nname: linkfox-google-trend-get-trend-by-keys\r\ndescription: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。\r\n---\r\n\r\n# Google Trends Keyword Trend Analysis\r\n\r\nThis skill guides you on how to query and analyze Google Trends keyword search interest data, helping users understand how keyword popularity changes over time across different regions.\r\n\r\n## Core Concepts\r\n\r\nGoogle Trends provides normalized search interest data (0-100 scale) reflecting how popular a given search term is relative to its peak popularity in the selected region and time range. A value of 100 represents peak popularity, 50 means the term is half as popular as its peak, and 0 means insufficient data.\r\n\r\n**Important language rule**: Keywords must be in the language of the target country. For example, use English keywords for the US, German keywords for Germany, Japanese keywords for Japan. If the user provides keywords in the wrong language, translate them before querying.\r\n\r\n## Parameters\r\n\r\n| Parameter | Type | Required | Description |\r\n|-----------|------|----------|-------------|\r\n| keyword | string | Yes | The search keyword to analyze (max 100 characters). Must be in the target country's language. |\r\n| region | string | No | Country/region code. Defaults to `US`. |\r\n| dayRangeStart | string | No | Start date for the time range (format: YYYY-MM-DD, from 2004 onward). |\r\n| dayRangeEnd | string | No | End date for the time range (format: YYYY-MM-DD, from 2004 onward). |\r\n\r\nWhen both `dayRangeStart` and `dayRangeEnd` are provided, the custom time range takes priority.\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 doesn't specify a region.\r\n\r\n## 调用方式\r\n\r\n- **API 端点**：`POST /googleTrend/getTrendByKeys`（完整参数/响应/错误码见 `references/api.md`）\r\n- **Python 脚本**：`python scripts/google_trends_keyword.py '' [--inline]`\r\n- **成本约束**：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\r\n\r\n**输出策略（脚本默认行为）**：\r\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-keys-.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## How to Build Queries\r\n\r\n### Principles for Effective Queries\r\n\r\n1. **Use the correct language**: Always ensure keywords match the target region's language. Translate first if needed.\r\n2. **Specify a region**: Default is US, but always confirm the user's intended market.\r\n3. **Use date ranges for focused analysis**: For seasonal trends or specific event analysis, provide `dayRangeStart` and `dayRangeEnd`.\r\n4. **Keep keywords concise**: Google Trends works best with short, focused search terms.\r\n\r\n### Usage Examples\r\n\r\n**1. Basic Keyword Trend (Default Region & Time)**\r\n```json\r\n{\"keyword\": \"wireless charger\"}\r\n```\r\nQuery the overall search interest trend for \"wireless charger\" in the US.\r\n\r\n**2. Keyword Trend in a Specific Region**\r\n```json\r\n{\"keyword\": \"Ladekabel\", \"region\": \"DE\"}\r\n```\r\nQuery the search interest for \"Ladekabel\" (charging cable) in Germany.\r\n\r\n**3. Custom Date Range Analysis**\r\n```json\r\n{\"keyword\": \"christmas gifts\", \"region\": \"US\", \"dayRangeStart\": \"2024-09-01\", \"dayRangeEnd\": \"2025-01-31\"}\r\n```\r\nAnalyze the seasonal trend of \"christmas gifts\" in the US from September 2024 through January 2025.\r\n\r\n**4. Year-over-Year Comparison**\r\n```json\r\n{\"keyword\": \"sunscreen\", \"region\": \"AU\", \"dayRangeStart\": \"2023-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\r\n```\r\nCompare multi-year seasonality of \"sunscreen\" in Australia.\r\n\r\n**5. Regional Market Research**\r\n```json\r\n{\"keyword\": \"yoga mat\", \"region\": \"GB\"}\r\n```\r\nCheck the popularity trend of \"yoga mat\" in the United Kingdom.\r\n\r\n**6. Emerging Trend Detection**\r\n```json\r\n{\"keyword\": \"AI glasses\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-12-31\"}\r\n```\r\nTrack the rise of \"AI glasses\" search interest over the past two years in the US.\r\n\r\n## Display Rules\r\n\r\n1. **Present data clearly**: Show trend data in well-formatted tables or describe the trend curve. Include key data points such as peak values, troughs, and notable changes.\r\n2. **Explain the scale**: Remind users that Google Trends values are on a 0-100 normalized scale, where 100 = peak popularity in the selected scope.\r\n3. **Highlight patterns**: Point out seasonal patterns, sudden spikes, or sustained growth/decline when visible in the data.\r\n4. **Chart data availability**: When the response includes `chartOption`, mention that visualization data is available and describe the trend shape.\r\n5. **Error handling**: When a query fails, explain the reason and suggest adjustments (e.g., check keyword spelling, try a different date range, ensure the keyword is in the correct language).\r\n## Important Limitations\r\n\r\n- **No secondary SQL processing**: Results from this tool are unstructured and cannot be fed into dynamic query tools for secondary analysis.\r\n- **Normalized values**: Trend values are relative (0-100), not absolute search volumes.\r\n- **Data availability**: Data is available from 2004 onward, but very niche terms may have sparse data.\r\n- **Single keyword per call**: Each API call handles one keyword. For multi-keyword comparisons, make separate calls and compare results.\r\n- **Language requirement**: Keywords must match the target region's language for accurate results.\r\n\r\n## User Expression & Scenario Quick Reference\r\n\r\n**Applicable** -- Queries about keyword search popularity trends:\r\n\r\n| User Says | Scenario |\r\n|-----------|----------|\r\n| \"How popular is XX keyword on Google\" | Basic trend lookup |\r\n| \"Is XX trending up or down\" | Trend direction analysis |\r\n| \"When does XX peak in searches\" | Seasonal peak detection |\r\n| \"Compare popularity of XX across months\" | Seasonal pattern analysis |\r\n| \"Is XX gaining traction in Germany\" | Regional trend check |\r\n| \"What's the search trend for XX over the past year\" | Historical trend analysis |\r\n| \"Holiday search trends for XX\" | Seasonal / event-driven analysis |\r\n\r\n**Not applicable** -- Needs beyond Google Trends search interest data:\r\n\r\n- Google Ads keyword planner or bid/CPC data\r\n- Absolute search volume numbers (Google Trends provides relative, not absolute data)\r\n- Social media trending topics (Twitter/X, TikTok, etc.)\r\n- Amazon-specific search term data (use ABA Data Explorer instead)\r\n- Website traffic analytics (Google Analytics, SimilarWeb, etc.)\r\n- Keyword ranking on search engine result pages (SEO rank tracking)\r\n\r\n**Boundary judgment**: When users say \"keyword research\" or \"market trend analysis\", if it specifically relates to search interest popularity over time from Google's perspective, this skill applies. If they want absolute traffic numbers, advertising metrics, or e-commerce-platform-specific data, 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-keys\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1783057657865\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/getTrendByKeys`\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| keyword | string | 是 | 关键词（关键词必须是国家的语言！比如美国要用英语关键词，德国要用德语关键词。如果不是对应国家的语言，请先翻译。）最大长度100字符 |\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| dayRangeStart | string | 否 | 时间范围开始时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n| dayRangeEnd | string | 否 | 时间范围结束时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n\r\n- 当同时提供 `dayRangeStart` 和 `dayRangeEnd` 时，自定义时间范围优先\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| trendInfoForKeys | array | 关键词趋势信息数组 |\r\n| trendInfoForKeys[].keyword | string | 关键词 |\r\n| trendInfoForKeys[].trendValues | array | 趋势值数组 |\r\n| trendInfoForKeys[].trendValues[].timeRange | string | 时间，格式为 yyyy-MM-dd |\r\n| trendInfoForKeys[].trendValues[].value | string | 值（归一化搜索热度，0-100） |\r\n| chartOption | object | 图表渲染元数据 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.data | array | 数据 |\r\n| costToken | integer | 消耗token |\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/getTrendByKeys \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"keyword\": \"wireless charger\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-01-01\"}'\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上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。 Tags: latest:1.0.7 Version history: v1.0.7 | 2026-09-14T05:19:29.114Z","codeSnippets":[],"executableExamples":[{"language":"json","snippet":"{\"keyword\": \"wireless charger\"}"},{"language":"json","snippet":"{\"keyword\": \"Ladekabel\", \"region\": \"DE\"}"},{"language":"json","snippet":"{\"keyword\": \"christmas gifts\", \"region\": \"US\", \"dayRangeStart\": \"2024-09-01\", \"dayRangeEnd\": \"2025-01-31\"}"},{"language":"json","snippet":"{\"keyword\": \"sunscreen\", \"region\": \"AU\", \"dayRangeStart\": \"2023-01-01\", \"dayRangeEnd\": \"2025-12-31\"}"},{"language":"json","snippet":"{\"keyword\": \"yoga mat\", \"region\": \"GB\"}"},{"language":"json","snippet":"{\"keyword\": \"AI glasses\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-12-31\"}"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: linkfox-google-trend-get-trend-by-keys\ndescription: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。\n---\n\n# Google Trends Keyword Trend Analysis\n\nThis skill guides you on how to query and analyze Google Trends keyword search interest data, helping users understand how keyword popularity changes over time across different regions.\n\n## Core Concepts\n\nGoogle Trends provides normalized search interest data (0-100 scale) reflecting how popular a given search term is relative to its peak popularity in the selected region and time range. A value of 100 represents peak popularity, 50 means the term is half as popular as its peak, and 0 means insufficient data.\n\n**Important language rule**: Keywords must be in the language of the target country. For example, use English keywords for the US, German keywords for Germany, Japanese keywords for Japan. If the user provides keywords in the wrong language, translate them before querying.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|-----------|------|----------|-------------|\n| keyword | string | Yes | The search keyword to analyze (max 100 characters). Must be in the target country's language. |\n| region | string | No | Country/region code. Defaults to `US`. |\n| dayRangeStart | string | No | Start date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n| dayRangeEnd | string | No | End date for the time range (format: YYYY-MM-DD, from 2004 onward). |\n\nWhen both `dayRangeStart` and `dayRangeEnd` are provided, the custom time range takes priority.\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 doesn't specify a region.\n\n## 调用方式\n\n- **API 端点**：`POST /googleTrend/getTrendByKeys`（完整参数/响应/错误码见 `references/api.md`）\n- **Python 脚本**：`python scripts/google_trends_keyword.py '' [--inline]`\n- **成本约束**：本工具会消耗算力；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。\n\n**输出策略（脚本默认行为）**：\n- **始终**将完整响应写入 `/linkfox///data/linkfox-google-trend-get-trend-by-keys-.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"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7dmc1t4j28hem1twwyav85p182pb1j\",\n \"slug\": \"linkfox-google-trend-get-trend-by-keys\",\n \"version\": \"1.0.7\",\n \"publishedAt\": 1789363169114\n}"},{"path":"references/api.md","content":"# 谷歌趋势-关键词趋势信息 API 参考\r\n\r\n## 调用规范\r\n\r\n- **请求地址**：`${LINKFOX_TOOL_GATEWAY}/googleTrend/getTrendByKeys`\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| keyword | string | 是 | 关键词（关键词必须是国家的语言！比如美国要用英语关键词，德国要用德语关键词。如果不是对应国家的语言，请先翻译。）最大长度100字符 |\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| dayRangeStart | string | 否 | 时间范围开始时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n| dayRangeEnd | string | 否 | 时间范围结束时间（希望自由指定时间范围时使用，以时间范围优先），格式为YYYY-MM-DD，从2004年开始 |\r\n\r\n- 当同时提供 `dayRangeStart` 和 `dayRangeEnd` 时，自定义时间范围优先\r\n\r\n## 响应结构\r\n\r\n| 字段 | 类型 | 说明 |\r\n|------|------|------|\r\n| trendInfoForKeys | array | 关键词趋势信息数组 |\r\n| trendInfoForKeys[].keyword | string | 关键词 |\r\n| trendInfoForKeys[].trendValues | array | 趋势值数组 |\r\n| trendInfoForKeys[].trendValues[].timeRange | string | 时间，格式为 yyyy-MM-dd |\r\n| trendInfoForKeys[].trendValues[].value | string | 值（归一化搜索热度，0-100） |\r\n| chartOption | object | 图表渲染元数据 |\r\n| chartOption.type | string | 数据类型 |\r\n| chartOption.fieldX | string | X轴字段 |\r\n| chartOption.fieldY | array | Y轴字段 |\r\n| chartOption.data | array | 数据 |\r\n| costToken | integer | 消耗token |\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/getTrendByKeys \\\r\n -H \"Authorization: $LINKFOXAGENT_API_KEY\" \\\r\n -H \"Content-Type: application/json\" \\\r\n -d '{\"keyword\": \"wireless charger\", \"region\": \"US\", \"dayRangeStart\": \"2024-01-01\", \"dayRangeEnd\": \"2025-01-01\"}'\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 "},{"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\nAnalyzes Google Trends keyword search interest by keyword, region, and optional custom date range through LinkFox's Google Trends API.\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 query Google Trends-style search interest and compare keyword popularity over time or across supported regions. It helps identify seasonal patterns, spikes, declines, and relative search interest on a normalized 0-100 scale.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill sends search queries, account identifiers, login flow data, payment actions, and feedback data to LinkFox services.\n\nMitigation: Install and use the skill only when LinkFox is trusted for those data types, and avoid submitting confidential or regulated search terms.\n\nRisk: API keys and full response files may persist locally or in shell configuration.\n\nMitigation: Use scoped credentials where possible, avoid placing API keys in shell startup files, and review or delete saved linkfox response files after use.\n\nRisk: Endpoint override environment variables can redirect traffic away from the documented LinkFox services.\n\nMitigation: Keep default endpoints for normal use and inspect LinkFox-related environment variables before running the scripts.\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-keys)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, JSON files]\n\n**Output Format:** [Markdown guidance with JSON response summaries and saved JSON response files]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Responses may be saved under a local linkfox session directory; small responses may be printed inline, while larger responses are summarized.]\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上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。 Skill: 谷歌趋势-关键词趋势 Owner: linkfox-ai Summary: Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说\"Google Trends\"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。 Tags: latest:1.0.7 Version history: v1.0.7 | 2026-09-14T05:19:29.114Z","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1361,"uniquenessScore":49,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-12T00:40:38.625Z","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:40:38.625Z","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-12T11:27:31.974Z","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"}]}}}