Wenmai Alpha Google Trends Scraper

---
name: wenmai-alpha-google-trends-scraper
description: "Google Trends 趋势采集接口，用于查询关键词在指定地区和时间范围内的搜索热度、趋势变化及接口支持的关联数据。当用户提到 Google Trends、关键词热度、需求趋势、季节性、地区兴趣、趋势对比或搜索趋势时触发此技能。只要用户希望用 Google 搜索热度判断市场需求或关键词走势，也应触发此技能。"
metadata:
  author: wenmai-ai
  version: "1.0.0"
---

# Wenmai Alpha Google Trends Scraper

## Purpose
Use this Skill to fetch Google Trends Scraper data through Wenmai standard API. It is useful for Google Search / SERP / Trends.

The Skill calls exactly one fixed standard API endpoint:

- Endpoint: `POST /wmapi/v1/alpha/google-trends-scraper`
- Auth: Header `secret-key: $WENMAI_API_KEY`
- Script: `scripts/alpha_google_trends_scraper.py`

## How To Run

请参考 https://skill.wenmai-ai.com/wenmaiskills/use_guide.html 获取 `secret-key`；额度或余额不足时，按该指南完成充值。运行脚本前，把复制的 key 导出为 `WENMAI_API_KEY`（或 `WENMAI_SECRET_KEY`）。

```bash
export WENMAI_API_KEY=sk-...
python3 scripts/alpha_google_trends_scraper.py '{"geo": "", "category": "", "maxItems": 0, "startUrls": [{"url": "https://trends.google.com/trends/explore?q=web+scraping&geo=US"}], "timeRange": "", "isMultiple": false, "viewedFrom": "", "searchTerms": ["webscraping"], "spreadsheetId": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgVE2upms", "maxConcurrency": 3, "customTimeRange": "2024-01-01 2024-12-31", "skipDebugScreen": false, "maxRequestRetries": 3, "pageLoadTimeoutSecs": 3}'
```

The script prints the raw Wenmai API response as formatted JSON. Read `references/api.md` when you need parameter details, field meanings, allowed values, defaults, request examples, or response fields.

## Parameter Rules

Required top-level fields: none documented by the API reference; pass at least one meaningful query, URL, ID, keyword, mode, or filter parameter from `references/api.md`.

Default assumptions: preserve the user's requested marketplace, country, language, URL list, keyword list, IDs, filters, pagination, and result limits. For scraper-style endpoints, avoid expanding result limits unless the user asks for a broader scrape.

## Response Rules

Present returned data in compact tables when the user asks for inspection or comparison. For long arrays, summarize the most decision-relevant rows first, then offer to continue with more rows. Keep raw numbers and source URLs traceable to response fields.

If the API response contains an `error` or a non-`OK` `code`, report the message and `requestId` if present, then suggest parameter corrections. Never invent missing data.