SellerSprite Competitor Lookup

This skill guides you on how to query and analyze Amazon competitor product data, helping Amazon sellers discover competing products, benchmark performance, and extract actionable competitive intelligence.

Core Concepts

The SellerSprite Competitor Lookup tool provides comprehensive Amazon product data across 12 marketplaces. It allows querying products by ASIN, keyword, seller name, brand, or category, and returns detailed metrics including monthly sales volume, revenue, BSR ranking, pricing, ratings, and growth trends.

Data snapshots: The tool supports both real-time data (last 30 days) and historical monthly snapshots. Use nearly (default) for current data or a yyyyMM format (e.g., 202501) for historical snapshots. Historical snapshots capture all active listings for that month, enabling year-over-year and seasonal comparisons.

Category hierarchy: Amazon category names support multi-level paths separated by colons (:). For example, Electronics:Computers & Accessories:Monitors. Convert user-provided category descriptions into the proper colon-separated format.

Supported Marketplaces

US (United States), UK (United Kingdom), DE (Germany), FR (France), JP (Japan), CA (Canada), IT (Italy), ES (Spain), MX (Mexico), AU (Australia), TR (Turkey), IN (India)

Default marketplace is US. Use US when the user does not specify a marketplace.

Parameter Guide

Search Filters

Pagination & Sorting

Sort Field Options

Key Response Fields

调用方式

• API 端点：POST /sellersprite/competitor-lookup（完整参数/响应/错误码见 references/api.md）
• Python 脚本：python scripts/sellerspritecompetitorlookup.py '<JSON 参数>' [--inline]
• 成本约束：本工具会消耗积分；同一会话同一参数组合默认只调用一次，脚本带 24h 本地缓存。失败/空结果不得自动换关键词、翻页或改邮编连续试探；需要继续检索时先向用户说明会产生额外消耗。

输出策略（脚本默认行为）：

• 始终将完整响应写入 <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-sellersprite-competitor-lookup-<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：环境变量未配置 LINKFOXAGENTAPIKEY，也未配置 LINKFOXAGENTAPI_KEY。
• 响应401或402状态码
• 响应提示积分或余额不足：消息含"积分余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值"，或类似含义的内容。

Usage Examples

1. Look up competitors by ASIN

{
  "marketplace": "US",
  "asinList": "B072MQ5BRX,B08N5WRWNW"
}

Use case: Analyze specific competing products by their ASINs.

2. Search competitors by keyword

{
  "marketplace": "US",
  "keyword": "wireless earbuds",
  "matchType": 1,
  "order": {"field": "total_units", "desc": "true"},
  "size": 20
}

Use case: Discover top-selling products for a keyword, sorted by monthly sales.

3. Filter by brand and category

{
  "marketplace": "US",
  "brand": "Anker",
  "nodeLabel": "Electronics:Headphones",
  "order": {"field": "total_amount", "desc": "true"}
}

Use case: Analyze a specific brand's product lineup within a category.

4. Find products by seller name

{
  "marketplace": "DE",
  "sellerName": "Anker Direct",
  "order": {"field": "bsr_rank", "desc": "false"}
}

Use case: View all products from a particular seller sorted by BSR.

5. Historical snapshot comparison

{
  "marketplace": "US",
  "keyword": "space heater",
  "dataSnapshotMonth": "202412",
  "order": {"field": "total_units", "desc": "true"},
  "size": 20
}

Use case: Analyze seasonal product performance using historical data snapshots.

6. Show product variations

{
  "marketplace": "JP",
  "asinList": "B0XXXXXXXXX",
  "showVariation": "Y"
}

Use case: Examine all variation-level data for a product family.

Display Rules

1. Present data clearly: Show query results in well-formatted tables. Include key metrics such as ASIN, title, price, monthly sales, BSR, rating, and brand. Do not provide subjective business advice unless the user asks for it.
2. Keyword language: When searching by keyword, always translate the keyword to the target marketplace language (e.g., English for US/UK, German for DE, Japanese for JP). Remind the user of this if they provide keywords in the wrong language.
3. BSR clarification: When displaying BSR data, remind users that a lower BSR value indicates stronger sales performance.
4. Growth metrics: When showing growth rates, clarify whether positive values mean improvement or decline (positive BSR growth count means BSR increased, which means worsened ranking).
5. Pagination notice: When the total result count exceeds the returned page size, inform the user of the total count and offer to fetch additional pages.
6. Badge highlights: When products carry badges (Best Seller, Amazon's Choice, A+ Content, Video), highlight these in the results as they are important competitive signals.
7. Error handling: When a query fails, explain the reason based on the message field and suggest adjusting query parameters.
8. Snapshot guidance: When users want to do seasonal or trend analysis, proactively suggest using historical snapshots (e.g., last year's same month) for comparison.

Important Limitations

• Result cap: Each page returns 10-100 records (controlled by size). Use pagination for larger result sets.
• ASIN limit: A maximum of 40 ASINs can be queried at once via asinList.
• Historical snapshots: Only existing monthly snapshots can be queried; future dates are not supported.
• Keyword language: Keywords should match the marketplace language for best results.

User Expression & Scenario Quick Reference

Applicable -- Amazon competitor product data queries:

Not applicable -- Needs beyond competitor product data:

• ABA search term data or keyword ranking (use ABA Data Explorer instead)
• Advertising / PPC campaign management
• Product reviews content or sentiment analysis
• Listing copywriting or optimization suggestions
• Supplier sourcing or manufacturing costs
• Account health or policy compliance

积分消耗规则

消耗 15 积分。

用户会因积分消耗而支付费用。请充分评估：当需要高频调用本技能，或用户对积分消耗量预期不足时，务必提醒用户，由用户决定是否继续。

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.