linkfox-amazon-store-uploads

Original：🇺🇸 English

Translated

5 scriptsChecked / no sensitive code detected

亚马逊店铺文件上传（与 linkfox-amazon-store-auth 等同系列），经 /spApi/developerProxy 调用 Uploads API v2020-11-01 的 createUploadDestinationForResource，再向返回 URL 上传文件，供 A+ Content、Messaging 等 API 使用。当用户提到上传文件、createUploadDestinationForResource、upload destination、contentMD5、预签名上传、SP-API 上传、A+ 图片上传、Messaging 附件上传时触发。

23installs

Sourcelinkfox-ai/linkfox-skills

Added on2026-07-04

NPX Install

npx skill4agent add linkfox-ai/linkfox-skills linkfox-amazon-store-uploads

SKILL.md Content

View Translation Comparison →

Amazon 店铺 Uploads（文件上传）

本 skill 专用于 向 Amazon 申请上传目的地并上传文件，与 linkfox-amazon-store-auth
同系列：先 storeTokens
，再 developerProxy
调用 createUploadDestinationForResource，最后用 upload_to_destination.py
对返回的 URL 执行 PUT（不经网关）。

这是 Uploads API，不是 Orders 订单接口。订单见 linkfox-amazon-store-orders
；批量 Feed 文件见 linkfox-amazon-store-feeds
。

官方参考

createUploadDestinationForResource · Create an upload destination

Prerequisites

依赖 linkfox-amazon-store-auth
。
resource
须与下游 API 文档一致（例如 A+：
```
aplus/2020-11-01/contentDocuments
```
；Messaging 为对应 messages 资源路径）。
contentMD5
为待上传文件内容的 Base64 MD5 摘要；传 filePath
/ content
时脚本可自动计算。

工作流

text

create_upload_destination_for_resource  →  uploadDestination { uploadDestinationId, url, headers }
upload_to_destination (PUT url + headers)  →  在 A+/Messaging 等 API 中引用 uploadDestinationId

Scripts

脚本	说明
`create_upload_destination_for_resource.py`	POST `uploads/2020-11-01/uploadDestinations/{resource}`
`upload_to_destination.py`	PUT 到返回的 `url` （带 `headers` ）
`_spapi_uploads_common.py`	内部公共模块

示例

bash

export LINKFOXAGENT_API_KEY="<your-key>"

# 1) 创建上传目的地（自动根据 filePath 计算 contentMD5）
python scripts/create_upload_destination_for_resource.py '{
  "sellerId":"A1...",
  "region":"NA",
  "resource":"aplus/2020-11-01/contentDocuments",
  "marketplaceId":"ATVPDKIKX0DER",
  "filePath":"/path/to/banner.jpg",
  "contentType":"image/jpeg"
}'

# 2) 上传文件（将上一步 stdout 中的 uploadDestination 传入）
python scripts/upload_to_destination.py '{
  "uploadDestination": { "url": "...", "headers": { } },
  "filePath": "/path/to/banner.jpg"
}'

Display Rules

成功创建目的地常为 HTTP 201；先看 developerProxy
，再看 uploadDestination
。
resource
不要带前导
```
/
```
；path 中会对
```
/
```
做编码。
网关需放行 uploads/2020-11-01/
前缀。

Feedback：

skillName

：

linkfox-amazon-store-uploads

。

更多跨境 skill：LinkFox Skills

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/check_auth_dependency.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"

Pick
--out-dir
outside any git working tree (e.g.
/tmp/...
on Unix,
%TEMP%/...
on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

This skill exposes multiple entry scripts:
check_auth_dependency.py
,
create_upload_destination_for_resource.py
,
upload_to_destination.py
. Pass
--script scripts/<name>.py
to choose the one you need.

run

writes the full response to a file and emits only a schema preview + file path.

read

projects specific fields, with

--limit/--offset

for slicing and

--format json|jsonl|csv|table

for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

High field count per record, or fields you don't need
Batch/paginated results (multiple items per call)
Long-text fields (descriptions, reviews, HTML, time series)
Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via

read

.