Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计提醒

linkfox-sif-keyword-trafficlinkfox sif 关键词流量

Agent Skill

linkfox-sif-keyword-traffic 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

3,070

周安装

123

GitHub Stars

公开资料未说明

下载量

994
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:linkfox-sif-keyword-traffic(linkfox sif 关键词流量)
来源仓库:https://github.com/linkfox-ai/linkfox-sif-keyword-traffic
安装命令:
openclaw skills install linkfox-sif-keyword-traffic
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install linkfox-sif-keyword-traffic

简介

拆解指定关键词下所有竞品的流量来源分布。

  • 区分自然搜索、SP广告、品牌广告与推荐位曝光情况。
  • 支持按ASIN过滤与日期区间筛选,识别新进流量词。
  • 数据存在更新延迟,分析时请注意时效性限制。
  • linkfox-sif-keyword-traffic 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
linkfox-sif-keyword-traffic
version
1.0.1
category
product-sourcing
description
在给定关键词下拆解所有竞品 ASIN 的流量来源——自然搜索、SP 广告、SB 品牌广告、SBV 视频广告、SP 推荐、AC/ER/TR 等推荐位,支持按 ASIN 过滤、指定日期区间及新进流量词等筛选。当用户提到关键词流量来源、该关键词下哪些竞品在抢流量、自然流量与付费流量占比、SP广告曝光、品牌广告占比、SP推荐位、推荐位广告/非广告拆分、搜索展示分析、Amazon's Choice或编辑推荐曝光、关键词竞争格局、ASIN流量构成、keyword traffic, traffic structure analysis, search share, ad share, traffic source distribution, SIF, traffic analysis, SP recommendation, recommend position breakdown时触发此技能。即使用户未明确提及"SIF",只要其需求涉及在某关键词下分析竞品 ASIN 的流量来源分布,也应触发此技能。

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

ParameterTypeDescription
searchKeywordstringThe search keyword to analyze. Translate to the target marketplace's language when applicable. Max 1000 characters.

Optional Parameters

ParameterTypeDefaultDescription
countrystringUSMarketplace code (13 supported — see list below).
asinsstring(none)Comma-separated ASIN filter; if omitted, returns all ASINs appearing under the keyword. Max 1000 chars.
conditionstring(none)Filter by a specific traffic source. Only one value per request. See Condition Filters below.
last7dbooleantrueUse the latest 7 days. When false, the API uses startDate/endDate.
startDatestringyyyy-MM-dd. Takes effect when last7d=false; if omitted, the system's latest integral week is used.
endDatestringyyyy-MM-dd, paired with startDate.
sortBystring(default)Sort field. See sortBy section below.
pageNuminteger1Page number for pagination.
pageSizeinteger100Results per page. Min 10, max 100.
descbooleantrueSort 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:

ValueMeaning
nfPositionNatural search traffic keywords
isSpAdSP ad keywords
isVedioAdVideo ad keywords
isBrandAdBrand ad keywords
isPPCAdPPC ad keywords (all paid ad types)
isSearchRecommendSearch recommendation keywords
acAdSP recommendation (Trending now / Customers frequently viewed / etc.)

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

ValueMeaning
totalPeriod.inNewly-entered traffic keywords this period
nfKeywordCnt.total / nfKeywordCnt.inKeywords with (new) organic exposure
adKeywordCnt.total / adKeywordCnt.inKeywords 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 SaysScenario
"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.*

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

90.38%
按下载量换算898

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills