Google Trends Keyword

Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comp...

Security Scan

The skill appears to implement Google Trends queries via an external LinkFox API (which legitimately requires an API key), but the package metadata omits that required credential and the skill points to external endpoints of an unknown owner — review the missing credential declaration and the external service before installing.

Purpose & Capability

The skill's code and documentation consistently implement Google Trends queries by calling LinkFox's tool gateway (https://tool-gateway.linkfox.com/googleTrend/getTrendByKeys), which aligns with the stated purpose. However, the registry metadata declares no required environment variables or primary credential while both references/api.md and the included script require an API key (LINKFOXAGENT_API_KEY). That mismatch is an inconsistency.

Instruction Scope

SKILL.md and the script instruct only to form queries, call the LinkFox API, and present results — they do not ask the agent to read unrelated local files or system credentials. The docs also include a separate feedback endpoint (skill-api.linkfox.com) in references; sending feedback to that endpoint is outside the core query flow but is documented separately. No hidden file I/O or other scope creep was found.

Install Mechanism

This is instruction-only with a small helper script included and no install spec. Nothing is downloaded from arbitrary URLs or written to nonstandard locations. Risk from installation is low.

Credentials

The code requires an API key in the environment variable LINKFOXAGENT_API_KEY and uses it as the Authorization header, which is proportionate to calling the external LinkFox service. However, the skill's declared requirements list no required env vars or primary credential — that omission is a concerning inconsistency. Also, the skill will transmit user-provided keywords and date ranges to an external API (linkfox domains), so users should consider data sensitivity before providing private queries.

Persistence & Privilege

The skill does not request 'always: true' and does not attempt to modify other skills or system settings. It runs only when invoked and prints instructions if the API key is missing.

Scan Findings in Context

[ENV_VAR_USAGE_LINKFOXAGENT_API_KEY] expected: Both references/api.md and scripts/google_trends_keyword.py require LINKFOXAGENT_API_KEY for Authorization. This is expected for an API-backed skill, but the registry metadata failed to declare that required env var.

[OUTBOUND_API_CALL_tool-gateway.linkfox.com] expected: The skill sends queries to https://tool-gateway.linkfox.com/googleTrend/getTrendByKeys and documents a separate feedback endpoint (skill-api.linkfox.com). Outbound network calls are expected for this skill's purpose, but users should verify the trustworthiness and privacy policy of these endpoints (owner unknown in registry).

What to consider before installing

This skill calls an external LinkFox API and requires an API key (environment variable LINKFOXAGENT_API_KEY), but the package metadata did not list that requirement — that's the primary inconsistency. Before installing or enabling: (1) Confirm you trust the LinkFox endpoints (tool-gateway.linkfox.com and skill-api.linkfox.com) and the skill owner; (2) Do not reuse sensitive credentials — create a least-privilege API key for this purpose; (3) If you care about query privacy, avoid sending sensitive or proprietary search terms to the external service; (4) Ask the publisher to update the skill metadata to declare LINKFOXAGENT_API_KEY as a required credential and to provide a homepage/official documentation for the service so you can verify ownership and privacy practices.

Google Trends Keyword Trend Analysis

This 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.

Core Concepts

Google 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.

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.

Parameters

Parameter	Type	Required	Description
keyword	string	Yes	The search keyword to analyze (max 100 characters). Must be in the target country's language.
region	string	No	Country/region code. Defaults to US.
dayRangeStart	string	No	Start date for the time range (format: YYYY-MM-DD, from 2004 onward).
dayRangeEnd	string	No	End date for the time range (format: YYYY-MM-DD, from 2004 onward).

When both dayRangeStart and dayRangeEnd are provided, the custom time range takes priority.

Supported Regions

US (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)

Default region is US. Use US when the user doesn't specify a region.

API Usage

This tool calls the LinkFox tool gateway API. See references/api.md for calling conventions, request parameters, and response structure. You can also execute scripts/google_trends_keyword.py directly to run queries.

How to Build Queries

Principles for Effective Queries

1. Use the correct language: Always ensure keywords match the target region's language. Translate first if needed.
2. Specify a region: Default is US, but always confirm the user's intended market.
3. Use date ranges for focused analysis: For seasonal trends or specific event analysis, provide dayRangeStart and dayRangeEnd.
4. Keep keywords concise: Google Trends works best with short, focused search terms.

Usage Examples

1. Basic Keyword Trend (Default Region & Time)

{"keyword": "wireless charger"}

Query the overall search interest trend for "wireless charger" in the US.

2. Keyword Trend in a Specific Region

{"keyword": "Ladekabel", "region": "DE"}

Query the search interest for "Ladekabel" (charging cable) in Germany.

3. Custom Date Range Analysis

{"keyword": "christmas gifts", "region": "US", "dayRangeStart": "2024-09-01", "dayRangeEnd": "2025-01-31"}

Analyze the seasonal trend of "christmas gifts" in the US from September 2024 through January 2025.

4. Year-over-Year Comparison

{"keyword": "sunscreen", "region": "AU", "dayRangeStart": "2023-01-01", "dayRangeEnd": "2025-12-31"}

Compare multi-year seasonality of "sunscreen" in Australia.

5. Regional Market Research

{"keyword": "yoga mat", "region": "GB"}

Check the popularity trend of "yoga mat" in the United Kingdom.

6. Emerging Trend Detection

{"keyword": "AI glasses", "region": "US", "dayRangeStart": "2024-01-01", "dayRangeEnd": "2025-12-31"}

Track the rise of "AI glasses" search interest over the past two years in the US.

Display Rules

1. 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.
2. Explain the scale: Remind users that Google Trends values are on a 0-100 normalized scale, where 100 = peak popularity in the selected scope.
3. Highlight patterns: Point out seasonal patterns, sudden spikes, or sustained growth/decline when visible in the data.
4. Chart data availability: When the response includes chartOption, mention that visualization data is available and describe the trend shape.
5. 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).

Important Limitations

• No secondary SQL processing: Results from this tool are unstructured and cannot be fed into dynamic query tools for secondary analysis.
• Normalized values: Trend values are relative (0-100), not absolute search volumes.
• Data availability: Data is available from 2004 onward, but very niche terms may have sparse data.
• Single keyword per call: Each API call handles one keyword. For multi-keyword comparisons, make separate calls and compare results.
• Language requirement: Keywords must match the target region's language for accurate results.

User Expression & Scenario Quick Reference

Applicable -- Queries about keyword search popularity trends:

User Says	Scenario
"How popular is XX keyword on Google"	Basic trend lookup
"Is XX trending up or down"	Trend direction analysis
"When does XX peak in searches"	Seasonal peak detection
"Compare popularity of XX across months"	Seasonal pattern analysis
"Is XX gaining traction in Germany"	Regional trend check
"What's the search trend for XX over the past year"	Historical trend analysis
"Holiday search trends for XX"	Seasonal / event-driven analysis

Not applicable -- Needs beyond Google Trends search interest data:

• Google Ads keyword planner or bid/CPC data
• Absolute search volume numbers (Google Trends provides relative, not absolute data)
• Social media trending topics (Twitter/X, TikTok, etc.)
• Amazon-specific search term data (use ABA Data Explorer instead)
• Website traffic analytics (Google Analytics, SimilarWeb, etc.)
• Keyword ranking on search engine result pages (SEO rank tracking)

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.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

1. The functionality or purpose described in this skill does not match actual behavior
2. The skill's results do not match the user's intent
3. The user expresses dissatisfaction or praise about this skill
4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

---

For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.