linkfox-sellersprite-traffic-keyword

SellerSprite Traffic Keyword

This skill helps query and analyze traffic keyword lists for an Amazon ASIN via SellerSprite.

Core Concepts

• ASIN reverse lookup keywords: Use a product ASIN as input to view the list of keywords through which that product gains traffic.
• Traffic share type（trafficKeywordTypes): main traffic keywords, precise traffic keywords, and the preciseLongTailin the schema (the tool copy is "conversion loss keywords"), etc.
• Conversion type（conversionKeywordTypes): such as high-converting keywords, steady keywords, loss keywords, etc.
• Keyword tags（badges): such as organic search keywords, Amazon Choice recommended keywords, etc.

How to call

• API endpoint：POST /sellersprite/traffic/keyword(for full parameters/responses/error codes, see references/api.md）
• Python script：python scripts/sellersprite_traffic_keyword.py '<JSON 参数>' [--inline]
• Cost constraints: This tool consumes compute; by default, the same parameter combination in the same session is called only once, and the script has a 24h local cache. On failure/empty results, do not automatically switch keywords, paginate, or change zip codes to probe continuously; if further retrieval is needed, first explain to the user that additional consumption will be incurred.

Output strategy (script default behavior)：

• Alwayswrite the complete response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-sellersprite-traffic-keyword-<timestamp>.json（<cwd> is the working directory when the script is executed, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user task;writing to /tmp is prohibited, and if the current directory is not writable, report an error)
• Response body ≤ 8 KB: after writing to disk, print the complete JSON to stdout
• Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, the length of the largest list field + the first 3 samples)
• Add --inline to force full printing to stdout (also written to disk)

Data reading suggestions: First look at the summary to determine whether it is sufficient; when specific fields are needed, prefer using jqorConvertFrom-Json to extract on demand from the saved json file, avoiding bringing the entire JSON into context.

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide resolution:

Abnormal situations

• API Key not configured: The environment variable is not configured with LINKFOX_AGENT_API_KEY, and LINKFOXAGENT_API_KEY。
• Response 401 or 402 status code
• Response indicates insufficient compute or balance: The message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.

Key Parameters

Parameter	Type	Required	Description
marketplace	string	Yes	Marketplace, default US
asin	string	Yes	The product ASIN to reverse look up
month	string	No	Historical month, format yyyyMM; if not provided, defaults to the last 30 days
page	integer	No	Page number, default 1
size	integer	No	Number per page, default 50, maximum 100
keyword	string	No	Keyword filtering
badges	string	No	Keyword tags, multiple values separated by commas
trafficKeywordTypes	string	No	Traffic share type, multiple values separated by commas
conversionKeywordTypes	string	No	Conversion type, multiple values separated by commas
orderField	string	No	Sort field, default rankPosition
orderDesc	boolean	No	Whether to reverse the order, default false

Usage Examples

{
  "marketplace": "US",
  "asin": "B0XXXXXXXXX",
  "size": 50,
  "orderField": "rankPosition",
  "orderDesc": false
}

{
  "marketplace": "US",
  "asin": "B0XXXXXXXXX",
  "month": "202507",
  "trafficKeywordTypes": "primary,precise",
  "conversionKeywordTypes": "excellent,stable",
  "page": 1,
  "size": 100
}

Display Rules

1. Result display priority: keywords, organic positions, ad positions, traffic share type, conversion type.
2. Clearly indicate the query period (the last 30 days or a historical month).
3. When pagination exists, inform the total count and the current page.
4. Do not output subjective business advice unrelated to the API unless the user explicitly requests it.

Important Limitations

• Required parameters:marketplace、asin
• Up to 100 records per page per request
• Historical queries require passing yyyyMM

Computing power consumption rules

Consumes 15 computing power.

Users will pay fees due to computing power consumption. Please fully assess: when this skill needs to be called at high frequency, or when the user has insufficient expectations for computing power consumption, be sure to remind the user, and let the user decide whether to continue.

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.