
linkfox-amazon-store-orders
亚马逊卖家订单查询与履约状态管理。用于搜索订单、获取订单详情、订单商品、买家信息和收货地址,处理发货确认、配送状态、管制商品订单及买家核验状态。用户提到亚马逊订单、卖家订单列表、订单详情、Amazon order ID、买家信息、收货地址、订单行、确认发货、更新 shipment 状态、管制订单、核验状态、searchOrders、getOrder、Orders API 时触发。即使未明确说“Orders API”,只要希望查询或处理亚马逊商城中产生的卖家订单,也应触发此技能;MCF、FBA 入仓和 External Fulfillment 货件使用对应履约技能。
- Installs
- 350
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-amazon-store-orders- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads linkfox-amazon-store-orders automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Amazon 店铺 Orders
本 skill 与 linkfox-amazon-store-auth、linkfox-amazon-store-report、linkfox-amazon-store-listings、linkfox-amazon-store-pricing 同属 Amazon Store 系列:依赖 linkfox-amazon-store-auth 选店(sellerId+region);直接 POST /spApi/developerProxy 传入 sellerId+region,由服务端解析 token(勿传 amzAccessToken,除非兼容旧调用)。转发上游 GET / POST / PATCH。
调用方式
- API 端点:
POST /spApi/developerProxy(不同 SP-API 操作通过 path/method 区分;完整参数/响应/错误码见references/api.md) - Python 脚本:
python scripts/<脚本名>.py '<JSON 参数>' [--inline](可用脚本见上文脚本一览) - 成本约束:本工具会消耗算力;失败/空结果不得自动换关键词、翻页或连续试探;需要继续检索时先向用户说明会产生额外消耗。
输出策略(脚本默认行为):
- 始终将完整响应写入
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-amazon-store-orders-<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:环境变量未配置
LINKFOX_AGENT_API_KEY,也未配置LINKFOXAGENT_API_KEY。 - 响应401或402状态码
- 响应提示算力或余额不足:消息含"算力余额不足/计费不足/余额不足/quota exceeded/insufficient balance/套餐到期/需充值/请充值",或类似含义的内容。
官方参考索引
| 能力 | 文档 |
|---|---|
| searchOrders | searchOrders |
| getOrder (v2026-01-01) | getOrder |
| getOrderBuyerInfo (deprecated) | getOrderBuyerInfo |
| getOrderAddress (deprecated) | getOrderAddress |
| getOrderItems (deprecated) | getOrderItems |
| getOrderItemsBuyerInfo (deprecated) | getOrderItemsBuyerInfo |
| updateShipmentStatus | updateShipmentStatus |
| getOrderRegulatedInfo | getOrderRegulatedInfo |
| updateVerificationStatus | updateVerificationStatus |
| confirmShipment | confirmShipment |
Prerequisites(必须先读)
本 skill 依赖 linkfox-amazon-store-auth。
- 运行
python scripts/check_auth_dependency.py;若 exit code 42 且 stderr 含DEPENDENCY_MISSING:,请先安装linkfox-amazon-store-auth。 - 不要在本 skill 内绕过依赖实现授权或令牌逻辑。
Current Capabilities(脚本一览)
| 能力 | developerProxy path(要点) | 脚本 |
|---|---|---|
| searchOrders | orders/2026-01-01/orders + Query | search_orders.py |
| getOrder | orders/2026-01-01/orders/{orderId} + Query | get_order.py |
| getOrderBuyerInfo | orders/v0/orders/{orderId}/buyerInfo | get_order_buyer_info.py |
| getOrderAddress | orders/v0/orders/{orderId}/address | get_order_address.py |
| getOrderItems | orders/v0/orders/{orderId}/orderItems + NextToken | get_order_items.py |
| getOrderItemsBuyerInfo | orders/v0/orders/{orderId}/orderItems/buyerInfo | get_order_items_buyer_info.py |
| updateShipmentStatus | orders/v0/orders/{orderId}/shipment,POST JSON | update_shipment_status.py |
| getOrderRegulatedInfo | orders/v0/orders/{orderId}/regulatedInfo | get_order_regulated_info.py |
| updateVerificationStatus | orders/v0/orders/{orderId}/regulatedInfo,PATCH JSON | update_verification_status.py |
| confirmShipment | orders/v0/orders/{orderId}/shipmentConfirmation,POST JSON | confirm_shipment.py |
共享逻辑见 scripts/_spapi_orders_common.py(仅供同目录脚本 import,非独立 CLI)。
Quick Parameters(摘要)
- searchOrders:
createdAfter或lastUpdatedAfter(二选一);marketplaceIds;可选fulfillmentStatuses、fulfilledBy、maxResultsPerPage、paginationToken(上一页nextToken)、includedData。 - getOrder:
orderId;可选includedData(如 BUYER、FULFILLMENT、PACKAGES)。 - getOrderItems / getOrderItemsBuyerInfo:可选
nextToken→ 查询参数NextToken。 - updateShipmentStatus:
marketplaceId、shipmentStatus(ReadyForPickup / PickedUp / RefusedPickup);可选orderItems。 - updateVerificationStatus:传
regulatedOrderVerificationStatus对象,或整包requestBody。 - confirmShipment:
requestBody为官方要求的完整对象(通常含packageDetail等)。
Scripts
export LINKFOXAGENT_API_KEY="<your-key>"
python scripts/search_orders.py '{"sellerId":"A1...","region":"NA","marketplaceIds":["ATVPDKIKX0DER"],"lastUpdatedAfter":"2026-05-01T00:00:00Z"}'
python scripts/get_order.py '{"sellerId":"A1...","region":"NA","orderId":"123-1234567-1234567","includedData":["FULFILLMENT","PACKAGES"]}'
Display Rules
- 先看网关
developerProxy.errcode/httpStatus,再解析各脚本附加字段(如searchOrders、order)。 - POST/PATCH 脚本:
stdout中含requestBody(组装后的 Amazon 请求体),便于排查。 - v0 买家/地址/行项目 接口在官方文档中为 deprecated;新集成优先用 v2026-01-01 的 searchOrders / getOrder 与
includedData拉齐业务字段。 - searchOrders 默认速率较低(官方约 0.0056 req/s),注意 429。
- 受限 PII / RDT 以 Amazon 数据保护政策为准;详见
references/api.md。
Important Limitations
- 权限:Orders 及相关角色;部分读取可能需 Restricted Data Token,不在本 skill 内实现。
- 路径白名单:若网关返回 1005 等拒绝转发,需后端放行
orders/v0/...与orders/2026-01-01/...前缀。 - 返回结构以 Amazon schema 为准;详见
references/api.md。
Amazon SP-API 接口保护与重试指引
同一店铺连续收到 Amazon SP-API 的 400、403、404 或 429 时,网关会返回 450、453、454 或 459 并短暂冷却。这些自定义状态码不是 Amazon 原生状态,也不表示封号;目的是避免持续异常或高频调用扩大店铺风险。
| 状态与 message | 范围 | 触发与冷却 | 处理 |
|---|---|---|---|
450:400,请求异常,请优化您的参数 | 店铺+接口 | 60 秒内超过 3 次:5 分钟;10 分钟内超过 4 次:20 分钟 | 停止原参数重试,检查必填字段、marketplace、ID、日期和请求体 |
453:403,店铺未授权,请先授权 | 店铺全部接口 | 60 秒内超过 2 次:5 分钟;10 分钟内超过 4 次:30 分钟 | 停止该店铺调用,检查授权、权限、店铺归属和区域 |
454:404,资源不存在,请优化您的参数 | 店铺+接口 | 60 秒内超过 3 次:5 分钟;10 分钟内超过 4 次:30 分钟 | 确认资源 ID、所属店铺/站点、资源状态和接口路径 |
459:429限流中,请降低频率 | 店铺+接口 | 首次:15 秒;2 分钟内超过 2 次:30 秒;3 分钟内超过 4 次:2 分钟 | 降低并发、分页和轮询频率并逐级退避 |
- 立即停止自动或并发重试,不得通过换脚本或重复创建任务绕过保护;优先遵循
retryAfter、blockedUntil,没有时按表中时长说明。 - 450/453/454 必须先修正参数、授权或资源标识,冷却后最多谨慎重试一次;再次触发则停止调用。453 期间停止该店铺全部 SP-API。
- 保留已有
reportId、feedId等任务 ID;写操作结果不确定时先查询状态,不直接重放。 - 向用户先说明店铺保护,再给原因、处理和等待时间。可回复:“为保护您的亚马逊店铺安全,检测到 Amazon SP-API 连续返回{原因},当前已进入短暂保护。请先{处理动作},预计{等待时间}后再试;这不代表封号,也不是套餐或算力限制。”不要只说“LinkFox 限流”或“服务器繁忙”。
算力消耗规则
不消耗算力。
Feedback: 见 references/api.md,skillName:linkfox-amazon-store-orders。
更多跨境 skill:LinkFox Skills
FAQ
What does the linkfox-amazon-store-orders skill do?
亚马逊卖家订单查询与履约状态管理。用于搜索订单、获取订单详情、订单商品、买家信息和收货地址,处理发货确认、配送状态、管制商品订单及买家核验状态。用户提到亚马逊订单、卖家订单列表、订单详情、Amazon order ID、买家信息、收货地址、订单行、确认发货、更新 shipment 状态、管制订单、核验状态、searchOrders、getOrder、Orders API 时触发。即使未明确说“Orders API”,只要希望查询或处理亚马逊商城中产生的卖家订单,也应触发此技能;MCF、FBA 入仓和 External Fulfillment 货件使用对应履约技能。
How do I install linkfox-amazon-store-orders?
Run npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-amazon-store-orders in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/linkfox-amazon-store-orders/ (personal) or .claude/skills/linkfox-amazon-store-orders/ (project).
Which AI agents can use linkfox-amazon-store-orders?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is linkfox-amazon-store-orders safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains linkfox-amazon-store-orders?
It is published by linkfox-ai in linkfox-ai/linkfox-skills. It has 350 recorded installs.
More from linkfox-ai/linkfox-skills
linkfox-multimodal-recognize-image
linkfox-ai/linkfox-skills
基于多模态AI的图片识别与分析。当用户想分析、描述、从图片URL中提取信息、image recognition, image analysis, image description, image content understanding, OCR text recognition, visual Q&A时触发此技能。当用户提到图片识别、图片分析、图片描述、识别图片内容、分析产品图、从图片中读取文字、描述图片、提取视觉内容或理解照片内容时触发。当用户提供图片URL并就其视觉内容提问时,即使未明确说"图片识别",也应触发此技能。
linkfox-amazon-search
linkfox-ai/linkfox-skills
模拟真实用户在亚马逊前台搜索,获取实时关键词排名和搜索结果页数据。当用户提到亚马逊商品搜索、搜索结果抓取、关键词在搜索页的排名、ASIN排名位置查询、竞品发现、搜索页价格对比、广告商品分析、新品监控、前台搜索模拟、Amazon search, keyword ranking, search results, ASIN ranking position, competitor discovery, price comparison, sponsored product analysis, real-time search, new product monitoring时触发此技能。即使用户未明确提及"搜索模拟",只要其需求涉及实时亚马逊搜索结果、商品排位数据或前台SERP分析,也应触发此技能。
linkfox-dld-product-search
linkfox-ai/linkfox-skills
在中国1688批发平台(阿里巴巴国内B2B市场)上搜索和分析商品,用于找货源、供应商发现和选品。当用户提到1688商品搜索、1688找货源、在1688上找供应商、批发商品查询、工厂货源、一件代发供应商搜索、1688关键词选品、批发价格对比、按销量筛选、任何1688平台上的选品调研、1688 search, 1688 product selection, find suppliers, factory lookup, wholesale pricing, supplier search, domestic sourcing, 1688 products时触发此技能。即使用户未明确说"1688",只要其需求涉及搜索批发商品、寻找国内供应商或从国内市场采购,也应触发此技能。
linkfox-mpstats-ozon-product-search
linkfox-ai/linkfox-skills
MPSTATS Ozon 俄罗斯站商品搜索与反查。按俄语关键词或 SKU 在 MPSTATS 数据库中检索 Ozon 商品,返回商品 ID、标题、品牌和卖家信息,是 Ozon 选品与竞品链路的起点。当用户提到 Ozon 选品、Ozon 商品搜索、俄罗斯电商选品、Ozon 关键词搜索、Ozon SKU 查询、MPSTATS Ozon、Ozon product search, MPSTATS Ozon, Russian marketplace, Ozon SKU lookup, Ozon keyword search 时触发此技能。即使用户未明确提到"MPSTATS",只要其意图是在 Ozon 俄罗斯站按关键词或 SKU 发现或反查商品,也应触发此技能。
linkfox-amazon-product-detail
linkfox-ai/linkfox-skills
通过ASIN获取亚马逊商品详细信息,包括标题、图片、五点描述、规格参数、A+页面、价格、评分评论、变体等;可在取得原始HTML时尝试提取Item Highlights(商品亮点)。当用户提到亚马逊商品详情、ASIN查询、商品页面数据、Listing分析、五点描述提取、Item Highlights提取、标题补充信息、商品图片获取、变体查看、竞品Listing研究、价格查询、评论拆解、商品规格查询、Amazon product details, ASIN lookup, listing analysis, bullet points, variant info, product pricing, ratings and reviews, A+ content, product specifications, product images时触发此技能。即使用户未明确说"商品详情",只要其需求涉及通过ASIN获取亚马逊商品页面的结构化数据,也应触发此技能。
linkfox-sellersprite-product-search
linkfox-ai/linkfox-skills
使用卖家精灵数据搜索和筛选亚马逊商品,支持价格、月销量、BSR排名、毛利率、评分、配送方式、标签、卖家来源等多维度条件,覆盖多个亚马逊站点。当用户提到亚马逊选品调研、产品筛选、销量过滤、产品发掘、BSR分析、小众商品发现、竞品分析、市场机会评估、按商品维度的市场规模估算、毛利率筛选、SellerSprite product selection, Amazon product selection, sales filtering, BSR analysis, profit screening, market analysis, product selection tool时触发此技能。即使用户未明确提及"卖家精灵",只要其需求涉及筛选和分析亚马逊商品级数据进行选品,也应触发此技能。
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.