← 返回 Skills 市场
linkfox-ai

Sif Keyword Traffic

作者 linkfox-ai · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ⚠ suspicious
103
总下载
0
收藏
0
当前安装
2
版本数
在 OpenClaw 中安装
/install linkfox-sif-keyword-traffic
功能描述
在给定关键词下拆解所有竞品 ASIN 的流量来源——自然搜索、SP 广告、SB 品牌广告、SBV 视频广告、SP 推荐、AC/ER/TR 等推荐位,支持按 ASIN 过滤、指定日期区间及新进流量词等筛选。当用户提到关键词流量来源、该关键词下哪些竞品在抢流量、自然流量与付费流量占比、SP广告曝光、品牌广告占比、SP...
使用说明 (SKILL.md)

SIF Keyword Traffic Source Summary

This skill guides you on how to query and analyze keyword traffic source data for Amazon products, helping sellers understand the traffic structure behind keywords — including organic search, Sponsored Products (SP) ads, brand ads, video ads, and various Amazon recommendation placements.

Core Concepts

The SIF Keyword Summary tool returns, for one given keyword, the list of ASINs appearing under that keyword along with their per-keyword traffic exposure breakdown and their product-level cross-channel traffic mix. It answers: Who is taking traffic under this keyword, and through which channels?

Traffic channels analyzed:

  • Natural Search — organic search result positions
  • SP Ads (Sponsored Products) — paid product ad placements (regular slot)
  • Brand Ads (SB) — top and bottom brand ad placements on the search results page
  • Video Ads (SBV) — Sponsored Brands Video placements
  • SP Recommendation slots — Trending now / Seen on social media / Customers frequently viewed / 4 stars and above
  • Amazon's Choice (AC) — Amazon's Choice badge recommendations
  • Editorial Recommendations (ER) — editorial/curated recommendation placements
  • Top Rated (TR) — high-rating recommendation placements

Two score families (important — do not mix):

  1. Product-level fields (no prefix, e.g. naturalSearchExposureScore): the ASIN's overall exposure across all keywords.
  2. Keyword-level fields (keyword… prefix, e.g. keywordNaturalExposureScore): the ASIN's exposure on just this one queried keyword.

Parameter Guide

Required Parameter

Parameter Type Description
searchKeyword string The search keyword to analyze. Translate to the target marketplace's language when applicable. Max 1000 characters.

Optional Parameters

Parameter Type Default Description
country string US Marketplace code (13 supported — see list below).
asins string (none) Comma-separated ASIN filter; if omitted, returns all ASINs appearing under the keyword. Max 1000 chars.
condition string (none) Filter by a specific traffic source. Only one value per request. See Condition Filters below.
last7d boolean true Use the latest 7 days. When false, the API uses startDate/endDate.
startDate string yyyy-MM-dd. Takes effect when last7d=false; if omitted, the system's latest integral week is used.
endDate string yyyy-MM-dd, paired with startDate.
sortBy string (default) Sort field. See sortBy section below.
pageNum integer 1 Page number for pagination.
pageSize integer 100 Results per page. Min 10, max 100.
desc boolean true Sort in descending order.

Supported Marketplaces

13 marketplaces: US (United States), UK (United Kingdom), DE (Germany), CA (Canada), JP (Japan), FR (France), ES (Spain), IT (Italy), MX (Mexico), AU (Australia), AE (United Arab Emirates), BR (Brazil), SA (Saudi Arabia).

Default marketplace is US. Codes outside this list will be rejected by the API pattern.

Condition Filters

Each request can include at most one condition filter. Flag-style:

Value Meaning
nfPosition Natural search traffic keywords
isSpAd SP ad keywords
isVedioAd Video ad keywords
isBrandAd Brand ad keywords
isPPCAd PPC ad keywords (all paid ad types)
isSearchRecommend Search recommendation keywords
acAd SP recommendation (Trending now / Customers frequently viewed / etc.)

Period-count filters (.total full / .in new-in):

Value Meaning
totalPeriod.in Newly-entered traffic keywords this period
nfKeywordCnt.total / nfKeywordCnt.in Keywords with (new) organic exposure
adKeywordCnt.total / adKeywordCnt.in Keywords with (new) ad exposure
allSpKeywordCnt.total / allSpKeywordCnt.in (New) SP-ad keywords (regular + recommendation)
spKeywordCnt.total / spKeywordCnt.in (New) SP regular keywords
recSpKeywordCnt.total / recSpKeywordCnt.in (New) SP recommendation keywords
allSbKeywordCnt.total / allSbKeywordCnt.in (New) SB-ad keywords
sbKeywordCnt.total / sbKeywordCnt.in (New) SB regular keywords
sbvKeywordCnt.total / sbvKeywordCnt.in (New) SBV keywords

sortBy

Leave empty for system default. Valid values:

totalKeywordNum (total keyword count), naturalKeywordNum, brandKeywordNum, vedioKeywordNum, acKeywordNum, erKeywordNum, trKeywordNum, sumScore (total exposure across all keywords), totalNfScore, totalSpSocre (note spelling), totalBrandScore, totalVedioScore, totalAcScore, totalTrScore, totalErScore.

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/sif_keyword_traffic.py directly to run queries.

Usage Examples

1. Basic keyword traffic overview Query the traffic source breakdown for a keyword in the US marketplace:

searchKeyword: "wireless charger", country: "US"

2. Filter for organic search traffic only See only ASINs that appear in natural search results for a keyword:

searchKeyword: "wireless charger", country: "US", condition: "nfPosition"

3. Analyze SP ad competition Find which ASINs are running SP ads for a keyword:

searchKeyword: "wireless charger", country: "US", condition: "isSpAd"

4. SP recommendation slots Find ASINs surfacing in SP recommendation slots (Trending now, Customers frequently viewed, etc.):

searchKeyword: "wireless charger", country: "US", condition: "acAd"

5. Keyword analysis for a non-US marketplace Analyze traffic sources in the Japan marketplace (use the local language keyword):

searchKeyword: "ワイヤレス充電器", country: "JP"

6. Focus on specific competitor ASINs Limit results to a small set of competing ASINs:

searchKeyword: "wireless charger", country: "US", asins: "B01NBNDC1T,B09VLJJPL6"

7. Custom date range

searchKeyword: "wireless charger", country: "US", last7d: false, startDate: "2026-04-05", endDate: "2026-04-11"

8. Rank ASINs by their overall SP exposure

searchKeyword: "wireless charger", country: "US", sortBy: "totalSpSocre", desc: true

9. Newly-entered traffic keywords this period

searchKeyword: "wireless charger", country: "US", condition: "totalPeriod.in"

Display Rules

  1. Present data clearly: Show query results in well-structured tables. Group data by traffic channel exposure ratios for easy comparison.
  2. Distinguish product-level vs keyword-level scores: Do not mix naturalSearchExposureScore (product-wide) with keywordNaturalExposureScore (this keyword only). Label columns so users know which scope they are reading.
  3. Highlight key ratios: When displaying results, emphasize the natural search exposure ratio vs. paid ad exposure ratio to help users quickly assess the organic-to-paid balance.
  4. Translate field names: Present field names in user-friendly language rather than raw API field names (e.g., "Natural Search Exposure Ratio" instead of "naturalSearchExposureRatio").
  5. Volume notice: When results are large (high total count), show core data and remind users they can paginate to see more results.
  6. Period annotation: When comparing exposure/counts, label the resolved window — default last7d; or startDate ~ endDate if a custom range was set. Also surface dataPeriodStartDate on each row.
  7. Error handling: When a query fails, explain the reason based on the msg field and suggest adjusting query parameters (e.g., checking keyword spelling or marketplace code).
  8. Percentage formatting: Display exposure ratios as percentages (e.g., 0.45 as "45%") for readability.
  9. Traffic source summary: When presenting a single ASIN's data, provide a brief traffic composition summary (e.g., "This product gets 60% of its exposure from organic search, 25% from SP ads, and 15% from brand ads"); prefer keyword-level fields when the user asks specifically about this keyword.

Important Limitations

  • Single condition filter: Only one condition value can be used per request. To compare multiple traffic sources, make separate requests.
  • Marketplace coverage: 13 marketplaces only — IN / NL / SE / PL / TR / SG are no longer available.
  • Keyword language: The searchKeyword should be in the language of the target marketplace for best results.
  • Result cap: Each page returns at most 100 records.
  • Scope: This endpoint focuses on per-keyword ASIN traffic; it does not return whole-ASIN metadata, cross-channel keyword counts, or variant aggregation. Use the ASIN traffic-source tool for those.

User Expression & Scenario Quick Reference

Applicable — Traffic source and competition structure analysis for Amazon keywords:

User Says Scenario
"Where does the traffic come from for this keyword" Traffic source breakdown
"How much organic vs paid traffic" Organic/paid ratio analysis
"Who's running SP ads for this keyword" SP ad competition analysis (condition=isSpAd)
"Which products are in SP recommendation slots" SP recommendation lookup (condition=acAd)
"Which products have Amazon's Choice" AC badge analysis (via amazonsChoiceExposureScore)
"Is this keyword dominated by ads" Ad saturation assessment
"Show me the brand ad competition" Brand ad landscape analysis
"Traffic structure for my competitor's keyword" Competitive traffic analysis
"Which products get editorial recommendations" ER placement analysis
"Compare these 2 ASINs on this keyword" ASIN filter via asins="B0A,B0B"
"For the week of March 8, traffic under this keyword" Custom startDate/endDate window
"Newly-entered traffic keywords this period" New-in filter (condition=totalPeriod.in)

Not applicable — Needs beyond keyword traffic source analysis:

  • Historical keyword ranking trends beyond current + custom window (use ABA data tools)
  • Advertising bid/budget optimization
  • Product reviews or listing content
  • Sales volume estimation
  • Full keyword search volume curve over time
  • Whole-ASIN traffic structure across all keywords (use the SIF ASIN traffic-source tool)

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.

安全使用建议
This skill calls an external LinkFox API and requires an API key (LINKFOXAGENT_API_KEY), but the registry metadata did not declare that requirement — treat that as a red flag. Before installing or enabling: (1) Confirm you are comfortable an external service (tool-gateway.linkfox.com) will receive whatever searchKeyword and optional ASINs you pass; avoid sending confidential data. (2) Verify the API key request is legitimate (the SKILL.md points to a Feishu doc; confirm the provider/trustworthiness). (3) Ask the skill author to update metadata to declare LINKFOXAGENT_API_KEY as a required env var and to reconcile the supported marketplaces/condition values between docs and code. (4) Test the skill with non-sensitive sample queries first. If you cannot verify the API provider or do not want an external service to receive your queries, do not install or provide the API key.
功能分析
Type: OpenClaw Skill Name: linkfox-sif-keyword-traffic Version: 1.0.1 The skill bundle is a legitimate tool for analyzing Amazon keyword traffic sources via the LinkFox API. The Python script (sif_keyword_traffic.py) implements standard API request logic using the urllib library, includes parameter validation, and securely retrieves credentials from environment variables. The instructions in SKILL.md and the API documentation in references/api.md are consistent with the stated purpose of e-commerce analytics, and the feedback mechanism is a standard feature for monitoring agent performance without signs of malicious intent or data exfiltration.
能力标签
requires-sensitive-credentials
能力评估
Purpose & Capability
The skill's stated purpose (query LinkFox's keyword/ASIN traffic summary) aligns with the code and API docs. However the registry metadata declares no required environment variables or primary credential, while both references/api.md and scripts/sif_keyword_traffic.py require an API key (LINKFOXAGENT_API_KEY). That is an incoherence: a network API client legitimately needs an API key, but the package metadata fails to declare it.
Instruction Scope
The SKILL.md and the Python script remain within the stated purpose: they construct a JSON POST and send it to the LinkFox tool gateway endpoint to get keyword traffic data. The docs also include a separate feedback endpoint (skill-api.linkfox.com) described only for feedback. The instructions do not attempt to read unrelated system files or exfiltrate other environment variables beyond the API key.
Install Mechanism
No install spec is provided (instruction-only plus an included helper script). There is no downloadable/embedded binary or archive; risk from install mechanism itself is low. The included Python script uses standard libraries (urllib) and is readable.
Credentials
The code requires LINKFOXAGENT_API_KEY (used as an Authorization header) but the skill metadata lists no required env vars or primary credential — this is a proportion/visibility mismatch. Requesting an API key is proportionate to contacting an external service, but the missing declaration and the external Feishu URL for obtaining the key should be disclosed clearly in metadata before installation. Also the script's VALID_COUNTRIES set differs from the 13 marketplaces listed in SKILL.md, indicating inconsistent parameter validation.
Persistence & Privilege
The skill does not request always: true and does not attempt to modify other skills or system configuration. It performs one-off network calls and exits; no persistent or privileged behavior is present.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install linkfox-sif-keyword-traffic
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /linkfox-sif-keyword-traffic 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.1
Update from 1.0.0 to 1.0.1
v1.0.0
Initial release
元数据
Slug linkfox-sif-keyword-traffic
版本 1.0.1
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 2
常见问题

Sif Keyword Traffic 是什么?

在给定关键词下拆解所有竞品 ASIN 的流量来源——自然搜索、SP 广告、SB 品牌广告、SBV 视频广告、SP 推荐、AC/ER/TR 等推荐位,支持按 ASIN 过滤、指定日期区间及新进流量词等筛选。当用户提到关键词流量来源、该关键词下哪些竞品在抢流量、自然流量与付费流量占比、SP广告曝光、品牌广告占比、SP... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 103 次。

如何安装 Sif Keyword Traffic?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install linkfox-sif-keyword-traffic」即可一键安装,无需额外配置。

Sif Keyword Traffic 是免费的吗?

是的,Sif Keyword Traffic 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Sif Keyword Traffic 支持哪些平台?

Sif Keyword Traffic 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Sif Keyword Traffic?

由 linkfox-ai(@linkfox-ai)开发并维护,当前版本 v1.0.1。

💬 留言讨论