linkfox-amazon-policy-feed

Amazon Policy & Regulation Feed

This skill retrieves Amazon's latest policy & regulation feed for cross-border sellers. It is a two-step (list then detail) flow: first list feed items by site / time window, then fetch the full article body by its id.

Core Concepts

• Source: Amazon official policy & regulation updates for sellers, curated by AI to surface items valuable to cross-border operations.
• AI summary: Each feed item includes a summaryZh field — an AI-generated 1-3 sentence Chinese summary for quick scanning.
• Two coupled tools:
  1. amazon/policyFeed — paginated list; returns structured records with title, AI summary, original URL, and publish time.
  2. amazon/policyFeedDetail — full article body (Markdown) for a single record id obtained from the list.
• Time range: Defaults to the last 7 days; supports custom time windows via publishedAtGte / publishedAtLte.

Parameters

List (amazon/policyFeed)

Parameter	Type	Required	Description	Default
site	string	No	Marketplace code (uppercase); site filtering only applies to some feed item types, others are always returned regardless of site	US
publishedAtGte	string	No	Publish/change time lower bound (incl.), yyyy-MM-dd HH:mm:ss	last 7 days
publishedAtLte	string	No	Publish/change time upper bound (incl.), yyyy-MM-dd HH:mm:ss	now
page	integer	No	Page number, starting at 1	1
pageSize	integer	No	Items per page, 1-100	20

Detail (amazon/policyFeedDetail)

Parameter	Type	Required	Description
id	string	Yes	Record ID (32-char string) from the list response data[].id

Supported Marketplaces (for site)

US, JP, UK, AU, BE, BR, CA, EG, FR, DE, IN, IT, MX, NL, PL, SA, SG, ES, SE, TR, AE, ZA, IE. Default is US when not specified. Note: site filtering only applies to some feed item types; others are always returned regardless of site.

How to Call

• API Endpoint：
  • POST /amazon/policyFeed（amazon_policy_feed.py. For complete parameters/responses/error codes, see references/api.md）
  • POST /amazon/policyFeedDetail（amazon_policy_feed_detail.py. For complete parameters/responses/error codes, see references/api.md）
• Python Script：python scripts/<脚本名>.py '<JSON 参数>' [--inline]
• Cost Constraints: This tool consumes compute; by default, the same parameter combination is called only once per session, and the script has a 24h local cache. On failure or empty results, do not automatically switch keywords, paginate, or repeatedly probe; if continued retrieval is needed, first explain to the user that it will incur additional consumption.

Output Strategy (Script Default Behavior)：

• Alwayswrite the complete response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-amazon-policy-feed-<timestamp>.json（<cwd> is the working directory when the script runs, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited; 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, length of the largest list field + 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, prioritize using jqorConvertFrom-Json to extract on demand from the saved json file, avoiding putting 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, nor is 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/plan expired/recharge required/please recharge", or content with similar meaning.

How to Build Queries

1. Set the time window: convert user's time reference into publishedAtGte / publishedAtLte. Leave empty for the default last 7 days.
2. Pick the marketplace: map user's target country to the site code (default US). Note this only filters some feed item types.
3. Paginate: increase page to scan deeper; max 100 items per page.
4. Drill into a record: take a record's id from the list and call the detail script to read the full body.

Usage Examples

1. Recent feed (last 7 days, US)

{"site": "US", "pageSize": 20}

2. Custom date range

{"site": "US", "publishedAtGte": "2026-05-01 00:00:00", "publishedAtLte": "2026-05-31 23:59:59"}

3. Japan site feed, page 2

{"site": "JP", "page": 2, "pageSize": 50}

4. Full body of one record

{"id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4"}

Display Rules

1. List view: present results as a table with title, AI summary (summaryZh), publish time, and original URL link.
2. Detail view: render the stdout Markdown as-is; the response also includes title and summaryZh for context.
3. Only present data: report what the feed says; do not add subjective business advice or speculate on future policy.
4. Timeliness note: data may lag the live page by a short period; the Amazon original is authoritative.
5. Error handling: on a failed call, explain the reason from the error response (e.g. invalid id -> re-fetch from the list) instead of guessing.

Important Limitations

• Default window is 7 days: without explicit time params, only the last 7 days are returned.
• Max 100 items per page: pageSize range is 1-100.
• Detail needs a valid list id: amazon/policyFeedDetail only accepts an id returned by amazon/policyFeed; unknown ids return an error.
• Not for aggregation: this skill's output is long-form text and metadata — not suited for second-pass statistical/aggregation analysis via _dataQuery_executeDynamicQuery.

User Expression & Scenario Quick Reference

Applicable — Amazon official policy & regulation feed:

User Says	Scenario
"What policy changes has Amazon had recently"	Recent policy feed overview
"Amazon US marketplace policy news from the past week"	Site-filtered policy news
"What recent policy and regulation updates does Amazon have"	General policy/regulation updates
"Amazon FBA latest policies and regulations"	Topic-specific policy lookup
"View the full text of this policy news"	Fetch full article body by id
"Amazon latest policy updates"	English trigger

Not applicable — beyond policy & regulation feed:

• Product / keyword / sales analytics, listing optimization, review analysis
• Real-time storefront search results or product detail
• Account-specific notifications inside an individual seller account
• Historical patent or trademark searches

Boundary judgment: if the user wants Amazon's officially published policy, regulation, or compliance updates for sellers (and its full text), this skill applies. If they want product/keyword/sales data, use the corresponding data skills.

Compute Consumption Rules

Consumes 15 compute.

Users pay fees due to compute consumption. Please fully evaluate: when this skill needs to be called frequently, or when the user's expectation of compute consumption is insufficient, 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.

---

For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.