OmniRoute API Keys
diegosouzapw/OmniRoute
Documents the OmniRoute REST endpoints for creating, listing, updating, regenerating and deleting API keys, with per-key scopes, spending limits, expiry and device lists.
Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis…
MITAuto-check passed
Install Linkfox Google Trend Get Trend By Keys
$ npx skills add linkfox-ai/linkfox-skills --skill linkfox-google-trend-get-trend-by-keys -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install linkfox-ai/linkfox-skills linkfox-google-trend-get-trend-by-keys --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/linkfox-ai/linkfox-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/linkfox-google-trend-get-trend-by-keys .claude/skills/linkfox-google-trend-get-trend-by-keys && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linkfox-google-trend-get-trend-by-keys" agent skill from https://github.com/linkfox-ai/linkfox-skills/tree/main/skills/linkfox-google-trend-get-trend-by-keys into .claude/skills/linkfox-google-trend-get-trend-by-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkfox-google-trend-get-trend-by-keys", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/linkfox-ai/linkfox-skills/tree/main/skills/linkfox-google-trend-get-trend-by-keysType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add linkfox-ai/linkfox-skills --skill linkfox-google-trend-get-trend-by-keys -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install linkfox-ai/linkfox-skills linkfox-google-trend-get-trend-by-keys --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/linkfox-ai/linkfox-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/linkfox-google-trend-get-trend-by-keys .agents/skills/linkfox-google-trend-get-trend-by-keys && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linkfox-google-trend-get-trend-by-keys" agent skill from https://github.com/linkfox-ai/linkfox-skills/tree/main/skills/linkfox-google-trend-get-trend-by-keys into .agents/skills/linkfox-google-trend-get-trend-by-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkfox-google-trend-get-trend-by-keys", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add linkfox-ai/linkfox-skills --skill linkfox-google-trend-get-trend-by-keys -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install linkfox-ai/linkfox-skills linkfox-google-trend-get-trend-by-keys --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/linkfox-ai/linkfox-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/linkfox-google-trend-get-trend-by-keys .cursor/skills/linkfox-google-trend-get-trend-by-keys && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linkfox-google-trend-get-trend-by-keys" agent skill from https://github.com/linkfox-ai/linkfox-skills/tree/main/skills/linkfox-google-trend-get-trend-by-keys into .cursor/skills/linkfox-google-trend-get-trend-by-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkfox-google-trend-get-trend-by-keys", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/linkfox-ai/linkfox-skills.git --path skills/linkfox-google-trend-get-trend-by-keys--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add linkfox-ai/linkfox-skills --skill linkfox-google-trend-get-trend-by-keys -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install linkfox-ai/linkfox-skills linkfox-google-trend-get-trend-by-keys --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/linkfox-ai/linkfox-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/linkfox-google-trend-get-trend-by-keys .gemini/skills/linkfox-google-trend-get-trend-by-keys && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linkfox-google-trend-get-trend-by-keys" agent skill from https://github.com/linkfox-ai/linkfox-skills/tree/main/skills/linkfox-google-trend-get-trend-by-keys into .gemini/skills/linkfox-google-trend-get-trend-by-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkfox-google-trend-get-trend-by-keys", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install linkfox-ai/linkfox-skills linkfox-google-trend-get-trend-by-keysInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add linkfox-ai/linkfox-skills --skill linkfox-google-trend-get-trend-by-keys -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/linkfox-ai/linkfox-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/linkfox-google-trend-get-trend-by-keys .github/skills/linkfox-google-trend-get-trend-by-keys && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linkfox-google-trend-get-trend-by-keys" agent skill from https://github.com/linkfox-ai/linkfox-skills/tree/main/skills/linkfox-google-trend-get-trend-by-keys into .github/skills/linkfox-google-trend-get-trend-by-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkfox-google-trend-get-trend-by-keys", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add linkfox-ai/linkfox-skills --skill linkfox-google-trend-get-trend-by-keys -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install linkfox-ai/linkfox-skills linkfox-google-trend-get-trend-by-keys --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/linkfox-ai/linkfox-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/linkfox-google-trend-get-trend-by-keys .opencode/skills/linkfox-google-trend-get-trend-by-keys && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linkfox-google-trend-get-trend-by-keys" agent skill from https://github.com/linkfox-ai/linkfox-skills/tree/main/skills/linkfox-google-trend-get-trend-by-keys into .opencode/skills/linkfox-google-trend-get-trend-by-keys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkfox-google-trend-get-trend-by-keys", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
linkfox-google-trend-get-trend-by-keys- GitHub stars
- 107
- Token cost
- ~2.1k tokens
- SKILL.md length
- 987 words
- Files
- 5 (incl. scripts, references)
- Skills in repo
- 177
- Repo updated
- First seen
- Licence
- MIT
At a glance
Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis…
- Works in 4 steps: Use the correct language: Always ensure… → Specify a region: Default is US, but… → Use date ranges for focused analysis:… → …
- SKILL.md covers Core Concepts, Parameters, Supported Regions and 调用方式, plus 6 more sections
- Runs Python scripts from its folder; calls python; needs LINKFOX_AGENT_API_KEY and LINKFOXAGENT_API_KEY
What it does
Linkfox Google Trend Get Trend By Keys is an agent skill from linkfox-ai/linkfox-skills. Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说"Google Trends"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/api.md`, `references/onboarding.md` and `scripts/google_trends_keyword.py`).
The licence is MIT.
Example prompts
- “Google Trends”
- “/linkfox-google-trend-get-trend-by-keys”
Requirements
- Python 3
- A credential in LINKFOX_AGENT_API_KEY
- A credential in LINKFOXAGENT_API_KEY
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Use the correct language: Always ensure keywords match the target region's language. Translate first if needed.
- Specify a region: Default is US, but always confirm the user's intended market.
- Use date ranges for focused analysis: For seasonal trends or specific event analysis, provide dayRangeStart and dayRangeEnd.
- Keep keywords concise: Google Trends works best with short, focused search terms.
What it can do on your machine
Read from SKILL.md and the folder at commit 38fef04. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
skill.linkfox.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
LINKFOX_AGENT_API_KEYLINKFOXAGENT_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Linkfox Google Trend Get Trend By Keys loads about 2.1k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 987 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from linkfox-ai/linkfox-skills at commit 38fef04, republished under its MIT licence (© linkfox-ai). 987 words, ~2,144 tokens.
Download SKILL.mdSave it as
.claude/skills/linkfox-google-trend-get-trend-by-keys/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- linkfox-google-trend-get-trend-by-keys
- description
- Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis, regional popularity, keyword comparison时触发此技能。即使用户未明确说"Google Trends"，只要其需求涉及对比不同时间段或区域的关键词搜索热度趋势，也应触发此技能。
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 端点：
POST /googleTrend/getTrendByKeys（完整参数/响应/错误码见references/api.md） - Python 脚本：
python scripts/google_trends_keyword.py '<JSON 参数>' [--inline] - 成本约束：本工具会消耗算力；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。
输出策略（脚本默认行为）：
- 始终将完整响应写入
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-google-trend-get-trend-by-keys-<timestamp>.json（<cwd>为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；<session>取自环境变量SESSION_ID，按用户任务自动聚合；禁止写入 /tmp，当前目录不可写则报错） - 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout
- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数如
total/costToken、最大列表字段的长度 + 前 3 条样本） - 加
--inline强制全量打印到 stdout（同样落盘）
读数据建议：先看摘要判断是否足够；需要具体字段时优先用 jq或ConvertFrom-Json 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。
解决认证和算力问题
发生以下异常情况时，采用 references/onboarding.md 引导解决问题：
异常情况
- 未配置API Key：环境变量未配置
LINKFOX_AGENT_API_KEY，也未配置LINKFOXAGENT_API_KEY。 - 响应401或402状态码
- 响应提示算力或余额不足：消息含"算力余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值"，或类似含义的内容。
How to Build Queries
Principles for Effective Queries
- Use the correct language: Always ensure keywords match the target region's language. Translate first if needed.
- Specify a region: Default is US, but always confirm the user's intended market.
- Use date ranges for focused analysis: For seasonal trends or specific event analysis, provide
dayRangeStartanddayRangeEnd. - 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
- 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.
- Explain the scale: Remind users that Google Trends values are on a 0-100 normalized scale, where 100 = peak popularity in the selected scope.
- Highlight patterns: Point out seasonal patterns, sudden spikes, or sustained growth/decline when visible in the data.
- Chart data availability: When the response includes
chartOption, mention that visualization data is available and describe the trend shape. - 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).
Show full SKILL.md (374 more words)Show less
Important Limitations
- Data analysis: The response is JSON. Read
trendInfoForKeys[].trendValues[]from the saved response; preservetimeRangeand values such as"<1"without converting them to zero._dataQuery_executeDynamicQueryqueries Linkfox session data stored in SLS, not arbitrary JSON files; use it only when the required stored-data mapping exists. - 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.
算力消耗规则
消耗 6 算力。
用户会因算力消耗而支付费用。请充分评估：当需要高频调用本技能，或用户对算力消耗量预期不足时，务必提醒用户，由用户决定是否继续。
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- Anything you believe could be improved
Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.
For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.
© linkfox-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references) in skills/linkfox-google-trend-get-trend-by-keys of linkfox-ai/linkfox-skills.
- SKILL.md
- references/api.md
- references/onboarding.md
- scripts/google_trends_keyword.py
- scripts/onboarding.py
Open the folder on GitHubat commit 38fef04
Compare with similar skills
Linkfox Google Trend Get Trend By Keys next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linkfox Google Trend Get Trend By Keys this skilllinkfox-ai/linkfox-skills | 107 | — | ~2.1k | Automated safety check: Pass | MIT | |
| OmniRoute API Keysdiegosouzapw/OmniRoute | 75k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Apify Trend Analysissickn33/agentic-awesome-skills | 47k | 2 repos | ~1.2k | Automated safety check: Notes | MIT | |
| OmniRoute Key and OAuth CLIdiegosouzapw/OmniRoute | 75k | — | ~621 | Automated safety check: Pass | MIT | |
| Configuring Hsm For Key Storagemukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~984 | Automated safety check: Pass | Apache-2.0 | |
| Add Hosted Keysimstudioai/sim | 30k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Apify Trend Analysis
sickn33/agentic-awesome-skills
Discover and track emerging trends across Google Trends, Instagram, Facebook, YouTube, and TikTok to inform content strategy.
OmniRoute Key and OAuth CLI
diegosouzapw/OmniRoute
Command reference for managing OmniRoute API keys and provider OAuth connections from the terminal: create, list, rotate, revoke and inspect limits.
Configuring Hsm For Key Storage
mukul975/Anthropic-Cybersecurity-Skills
Configures Hardware Security Modules for cryptographic key storage using the PKCS11 standard interface, covering key generation, signing, encryption, and key management on physical HSMs and SoftHSM2…
Add Hosted Key
simstudioai/sim
Add hosted API key support to a tool so Sim provides the key (metered and billed to the workspace) when a user has not brought their own.
Setup API Key
calesthio/OpenMontage
Guides users through setting up an ElevenLabs API key for ElevenLabs MCP tools.
More from linkfox-ai/linkfox-skills
All 177 skills in this repoLinkfox 1688 Search By Image
linkfox-ai/linkfox-skills
1688平台以图搜图，通过商品图片精准检索外观相似或同款的1688货源，返回标题、价格、起批量、月销量、复购率、交易评分等核心数据。当用户提到1688以图搜图、1688找货源、以图找同款、跨境找工厂、1688识图、图片找货源、找相似货源、image search 1688、find supplier by…
Linkfox Aba Intelligent Query
linkfox-ai/linkfox-skills
亚马逊ABA（品牌分析）搜索词数据的查询与分析，涵盖15个站点近3年的周维度数据。当用户提到ABA数据、亚马逊搜索词分析、关键词挖掘、搜索排名趋势、市场机会分析、季节性关键词、高点击低转化分析、蓝海词发现、竞品关键词分析、ABA data, search term report, keyword mining, search ranking trends, blue ocean…
Linkfox Amazon Alexa Search
linkfox-ai/linkfox-skills
通过亚马逊前台的 Alexa 购物助手发起自然语言问答，获取与问题相关的导购回答、推荐商品分组、ASIN 列表，以及可继续追问的问题。每次调用仅支持 1 条 prompt，如需追问须由 agent 总结上下文后拼接新问题发起新请求。可用 url 补充亚马逊页面上下文。当用户提到亚马逊 Alexa、Alexa 购物助手、亚马逊智能助手、AI…
Linkfox Amazon Opportunity Search By Metrics
linkfox-ai/linkfox-skills
亚马逊反向选品：基于历史商业洞察报告沉淀的指标数据池，按 30+ 项商业维度（市场规模与增长、价格区间与档位份额、竞争密度与头部集中度、人群画像如年龄/性别/收入、评论卖点与痛点等）反向筛选亚马逊赛道与关键词。当用户提到反向选品、指标筛选、细分市场反查、蓝海赛道挖掘、低竞争赛道、新人友好赛道、品牌分散市场、痛点切入、卖点反查、定价档位机会、人群画像选品、Amazon niche reverse…
Linkfox Amazon Product Detail
linkfox-ai/linkfox-skills
通过ASIN获取亚马逊商品详细信息，包括标题、图片、五点描述、规格参数、A+页面、价格、评分评论、变体等；可在取得原始HTML时尝试提取Item Highlights（商品亮点）。当用户提到亚马逊商品详情、ASIN查询、商品页面数据、Listing分析、五点描述提取、Item…
Linkfox Amazon Reviews List
linkfox-ai/linkfox-skills
按ASIN获取并分析亚马逊商品评论，支持15个站点(含美国站)，按星级筛选评论。当用户提到亚马逊评论、美国站评论、商品评价、买家投诉、差评、好评、星级评分、评论分析、评论情感、产品改良建议、Vine评论、已验证购买评论、竞品评论研究、Amazon reviews, US reviews, Amazon.com reviews, product feedback, negative review…
Questions about Linkfox Google Trend Get Trend By Keys
What does Linkfox Google Trend Get Trend By Keys do?
Google Trends关键词搜索热度对比与趋势分析，支持全球区域和自定义时间范围。当用户提到谷歌趋势、关键词随时间变化的热度、搜索兴趣对比、关键词趋势分析、季节性趋势检测、区域搜索热度、关键词热力图、多个关键词在Google上的对比、Google Trends, keyword popularity comparison, search trends, seasonal analysis…. Linkfox Google Trend Get Trend By Keys is an agent skill from linkfox-ai/linkfox-skills.
How do I install Linkfox Google Trend Get Trend By Keys in Claude Code?
Run `npx skills add linkfox-ai/linkfox-skills --skill linkfox-google-trend-get-trend-by-keys -a claude-code`. Or copy the skill folder (skills/linkfox-google-trend-get-trend-by-keys in linkfox-ai/linkfox-skills) into .claude/skills/linkfox-google-trend-get-trend-by-keys in your project. Claude Code loads it when a task matches its description.
How do I install Linkfox Google Trend Get Trend By Keys in Codex?
Run `npx skills add linkfox-ai/linkfox-skills --skill linkfox-google-trend-get-trend-by-keys -a codex`. Or copy the skill folder (skills/linkfox-google-trend-get-trend-by-keys in linkfox-ai/linkfox-skills) into .agents/skills/linkfox-google-trend-get-trend-by-keys in your project. Codex loads it when a task matches its description.
Can I use Linkfox Google Trend Get Trend By Keys in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add linkfox-ai/linkfox-skills --skill linkfox-google-trend-get-trend-by-keys -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkfox-google-trend-get-trend-by-keys, .gemini/skills/linkfox-google-trend-get-trend-by-keys, .github/skills/linkfox-google-trend-get-trend-by-keys and .opencode/skills/linkfox-google-trend-get-trend-by-keys in your project.
What does Linkfox Google Trend Get Trend By Keys need to run?
Going by SKILL.md and its folder, Linkfox Google Trend Get Trend By Keys needs Python for the scripts in its folder, the command-line tools its instructions call (python) and credentials named LINKFOX_AGENT_API_KEY and LINKFOXAGENT_API_KEY. Our summary lists: Python 3; A credential in LINKFOX_AGENT_API_KEY; A credential in LINKFOXAGENT_API_KEY.
Does Linkfox Google Trend Get Trend By Keys access the network?
SKILL.md names 1 domain. As links in the text: skill.linkfox.com. This is read from the text; nothing was executed.
Is Linkfox Google Trend Get Trend By Keys safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Linkfox Google Trend Get Trend By Keys use?
Linkfox Google Trend Get Trend By Keys is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Linkfox Google Trend Get Trend By Keys use?
About 2.1k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Linkfox Google Trend Get Trend By Keys?
Skills that share tags, products or a category with Linkfox Google Trend Get Trend By Keys: OmniRoute API Keys (diegosouzapw/OmniRoute, 75k stars), Apify Trend Analysis (sickn33/agentic-awesome-skills, 47k stars), OmniRoute Key and OAuth CLI (diegosouzapw/OmniRoute, 75k stars) and Configuring Hsm For Key Storage (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linkfox Google Trend Get Trend By Keys?
linkfox-ai (a GitHub user) maintains it in linkfox-ai/linkfox-skills, which has 107 GitHub stars. The repository holds 177 skills in this directory. The repository was last updated on September 14, 2026.
Source: linkfox-ai/linkfox-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.