What makes 亚马逊-店铺数据上传 notable?

1.5K downloads. Trust evidence available

How should 亚马逊-店铺数据上传 be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

亚马逊-店铺数据上传

亚马逊店铺 Feed 批量数据提交与处理状态管理。用于创建 Feed 文档、向预签名地址上传 Feed 内容、提交库存或 Listing 等批量文件、查询或列出 Feed、获取结果文档以及取消 Feed。用户提到亚马逊 Feed、批量更新库存或商品、提交 Listing Feed、POST_FLAT_FILE、feedType、feedDocumentId、feedId、Feed 处理状态、Feed 结果、取消 Feed、Feeds API 时触发。即使未明确说“Feed”，只要希望通过亚马逊 SP-API 批量提交结构化商品或库存数据，也应触发此技能；单个 Listing 的增删改查使用 linkfox-amazon-store-listings。 Skill: 亚马逊-店铺数据上传 Owner: linkfox-ai Summary: 亚马逊店铺 Feed 批量数据提交与处理状态管理。用于创建 Feed 文档、向预签名地址上传 Feed 内容、提交库存或 Listing 等批量文件、查询或列出 Feed、获取结果文档以及取消 Feed。用户提到亚马逊 Feed、批量更新库存或商品、提交 Listing Feed、POST_FLAT_FILE、feedType、feedDocumentId、feedId、Feed 处理状态、Feed 结果、取消 Feed、Feeds API 时触发。即使未明确说“Feed”，只要希望通过亚马逊 SP-API 批量提交结构化商品或库存数据，也应触发此技能；单个 Listing 的增删改查使用 linkfox-amazon-store-listings。 Tags: latest:1.0.8 Version history: v1.0.8 |

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.5k

Updated

Oct 10, 2026

Version

1.0.8

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.5K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.5K downloadsadoption · observed Oct 10, 2026
Latest release: 1.0.8release · observed Sep 14, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s171g8b6m2khwdy9ye8bxj0wx183vd4z:linkfox-amazon-store-feeds

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-linkfox-ai-linkfox-amazon-store-feeds/snapshot"

Documentation

CLAWHUB

105,715 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: linkfox-amazon-store-feeds
description: 亚马逊店铺 Feed 批量数据提交与处理状态管理。用于创建 Feed 文档、向预签名地址上传 Feed 内容、提交库存或 Listing 等批量文件、查询或列出 Feed、获取结果文档以及取消 Feed。用户提到亚马逊 Feed、批量更新库存或商品、提交 Listing Feed、POST_FLAT_FILE、feedType、feedDocumentId、feedId、Feed 处理状态、Feed 结果、取消 Feed、Feeds API 时触发。即使未明确说“Feed”，只要希望通过亚马逊 SP-API 批量提交结构化商品或库存数据，也应触发此技能；单个 Listing 的增删改查使用 linkfox-amazon-store-listings。
---

# Amazon 店铺 Feeds

本 skill 与 **`linkfox-amazon-store-auth`** 等同属 **Amazon Store** 系列：依赖 **`linkfox-amazon-store-auth`** 选店（`sellerId`+`region`）；直接 **`POST /spApi/developerProxy`** 传入 `sellerId`+`region`，由服务端解析 token（勿传 `amzAccessToken`，除非兼容旧调用）。转发 **GET / POST / DELETE**。

## 调用方式

- **API 端点**：`POST /spApi/developerProxy`（不同操作通过请求体区分；完整参数/响应/错误码见 `references/api.md`）
- **Python 脚本**：`python scripts/<脚本名>.py '<JSON 参数>' [--inline]`（可用脚本见上文脚本一览）
- **成本约束**：本工具会消耗算力；失败/空结果不得自动换关键词、翻页或连续试探；需要继续检索时先向用户说明会产生额外消耗。

**输出策略（脚本默认行为）**：
- **始终**将完整响应写入 `<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-amazon-store-feeds-<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/套餐到期/需充值/请充值"，或类似含义的内容。

## 官方参考索引

| 能力 | 文档 |
|------|------|
| createFeedDocument | [createFeedDocument](https://developer-docs.amazon.com/sp-api/reference/createfeeddocument) |
| getFeedDocument | [getFeedDocument](https://developer-docs.amazon.com/sp-api/reference/getfeeddocument) |
| createFeed | [createFeed](https://developer-docs.amazon.com/sp-api/reference/createfeed) |
| getFeed | [getFeed](https://developer-docs.amazon.com/sp-api/reference/getfeed) |
| getFeeds | [getFeeds](https://developer-docs.amazon.com/sp-api/reference/getfeeds) |
| cancelFeed | [cancelFeed](https://developer-docs.amazon.com/sp-api/reference/cancelfeed) |

---

## Prerequisites

1. 依赖 **`linkfox-amazon-store-auth`**；运行 `python scripts/check_auth_dependency.py`，exit **42** 时需先安装授权 skill。
2. 应用需具备 **Feeds** 相关角色；`feedType` 须与上传文件格式匹配（见 Amazon Feed Type Values 文档）。

---

## 典型工作流

1. **`create_feed_document.py`** → 得到 `feedDocumentId` 与 **`url`**（上传地址）。
2. **`upload_feed_document.py`** → 对 `url` **PUT** 上传 feed 文件（**不经** developerProxy）。
3. **`create_feed.py`** → 传入 `inputFeedDocumentId`、`feedType`、`marketplaceIds`。
4. **`get_feed.py`** / **`get_feeds.py`** → 轮询 `processingStatus`（如 IN_QUEUE、IN_PROGRESS、DONE、FATAL）。
5. 处理完成后用 **`get_feed_document.py`** 下载 **resultFeedDocumentId** 对应文档（再按返回 URL 自行下载结果文件）。

---

## Current Capabilities

| 能力 | path | method | 脚本 |
|------|------|-

_meta.json

{
  "ownerId": "kn7dmc1t4j28hem1twwyav85p182pb1j",
  "slug": "linkfox-amazon-store-feeds",
  "version": "1.0.8",
  "publishedAt": 1789361821950
}

references/api.md

# linkfox-amazon-store-feeds — API 参考（Feeds v2021-06-30）

## 1. 调用链

| 步骤 | 端点 | 说明 |
|------|------|------|
| 1 | `POST {BASE}/spApi/storeTokens` | `{"sellerId","region"}` → `accessToken` |
| 2 | `POST {BASE}/spApi/developerProxy` | 转发 SP-API（除文档上传/下载 URL 外） |

环境变量：`LINKFOX_AGENT_API_KEY`（或 `LINKFOXAGENT_API_KEY`，必填）（如未配置 按 SKILL.md 的 **## 解决认证和算力问题** 处理）；`LINKFOX_TOOL_GATEWAY`（可选，默认 `https://tool-gateway.linkfox.com`，回退 `STORE_API_BASE_URL` / `SPAPI_BASE_URL`）。

### developerProxy Body

| 字段 | 说明 |
|------|------|
| region | NA / EU / FE |
| path | 如 `feeds/2021-06-30/feeds`，无前导 `/` |
| method | GET / POST / DELETE |
| amzAccessToken | storeTokens 返回值 |
| queryString | 无 `?` 前缀 |
| body | POST 时为 JSON 字符串 |
| contentType | 一般 `application/json` |

网关响应：`errcode`、`httpStatus`、`body`（字符串）。成功 HTTP 可能为 **200 / 201 / 202 / 204**。

---

## 2. 脚本入参摘要

### 公共

| 字段 | 必填 | 说明 |
|------|------|------|
| sellerId | 是 | 卖家 ID |
| region | 是 | 区域 |
| skipDepCheck | 否 | 跳过本地 auth 探测 |

### create_feed_document.py

| 字段 | 必填 | 说明 |
|------|------|------|
| contentType | 是 | 与将要上传的文件 MIME 一致，如 `text/tab-separated-values; charset=UTF-8` |

解析字段：**`feedDocument`**（含 `feedDocumentId`、`url` 等，以 Amazon 为准）。

### upload_feed_document.py（不经 developerProxy）

| 字段 | 必填 | 说明 |
|------|------|------|
| uploadUrl | 是 | createFeedDocument 返回的 `url` |
| contentType | 是 | 与 createFeedDocument 相同 |
| filePath | 三选一 | 本地文件路径 |
| content | 三选一 | UTF-8 字符串内容 |
| contentBase64 | 三选一 | Base64 编码内容 |

### create_feed.py

| 字段 | 必填 | 说明 |
|------|------|------|
| feedType | 是 | 如 `POST_FLAT_FILE_INVLOADER_DATA` |
| marketplaceIds | 是 | 1～25 个站点 ID |
| inputFeedDocumentId | 是 | 已上传内容的文档 ID |
| feedOptions | 否 | 因 feedType 而异的对象 |

### get_feed.py / cancel_feed.py

| 字段 | 必填 |
|------|------|
| feedId | 是 |

### get_feeds.py

| 字段 | 必填 | 说明 |
|------|------|------|
| feedTypes | 条件 | 与 nextToken 二选一；最多 10 个 |
| nextToken | 条件 | 分页时**单独**传此参数 |
| marketplaceIds | 否 | 最多 10 个 |
| processingStatuses | 否 | CANCELLED, DONE, FATAL, IN_PROGRESS, IN_QUEUE |
| createdSince / createdUntil | 否 | ISO 8601 |
| pageSize | 否 | 1～100，默认 10 |

### get_feed_document.py

| 字段 | 必填 | 说明 |
|------|------|------|
| feedDocumentId | 是 | |
| enableContentEncodingUrlHeader | 否 | boolean；GZIP 时便于客户端自动解压 |

---

## 3. Feed 标准流程

```text
createFeedDocument → PUT uploadUrl (upload_feed_document.py)
    → createFeed → poll getFeed until DONE/FATAL
    → getFeedDocument(resultFeedDocumentId) → GET 结果 url
```

---

## 4. 常见 feedType（示例）

以 [Feed Type Values](https://developer-docs.amazon.com/sp-api/docs/feed-type-values) 为准，例如：

- `POST_PRODUCT_DATA` / `POST_INVENTORY_AVAILABILITY_DATA`
- `POST_FLAT_FILE_INVLOADER_DATA`
- `POST_ORDER_FULFILLMENT_DATA`

---

## 5. 错误与限制

- **401**：HTTP 401 或 authorized error：按 SKILL.md 的 **## 解决认证和算力问题** 处理。
- **402**：HTTP 402：按 SKILL.md 的 **## 解决认证和算力问题** 处理。
- **403**：权限或 feedType 未授权。
- **1005**（网关）：path 未在白名单，需放行 `feeds/2021-06-30/`。
- **429**：降频；getFeeds 等有独立 usage plan。
- 上传 U

references/onboarding.md

# 解决认证和算力问题

调用本 skill 时若网关返回 **auth** 或 **billing** 错误，走本 skill 自带的 `scripts/onboarding.py` 完成引导。

**auth 场景**：`errcode=401` 或消息含 `authorized error`/`鉴权失败`/`未授权`/`unauthorized`；或 `LINKFOX_AGENT_API_KEY` 与 `LINKFOXAGENT_API_KEY` 均为空。
1. 若已配置 key → 先让用户重启会话（最常见误判），仍失败让用户重新取 key 或换手机号重注册
2. 未配置 → 询问：自助去 https://agent.linkfox.com/ 取 key，或提供手机号让脚本注册
3. 手机号路径：
   - `python scripts/onboarding.py send-code <phone>` → 展示 JSON 里的 phone/agreements
   - 收到验证码后：`python scripts/onboarding.py login <phone> <code>`
   - 拿到 `api_key` 后把下面三平台配置转发给用户，提示重启会话生效：
     - Windows PowerShell（永久）：`setx LINKFOX_AGENT_API_KEY "<key>"`
     - macOS zsh：`echo 'export LINKFOX_AGENT_API_KEY="<key>"' >> ~/.zshrc && source ~/.zshrc`
     - Linux bash：`echo 'export LINKFOX_AGENT_API_KEY="<key>"' >> ~/.bashrc && source ~/.bashrc`
     - 变量名 `LINKFOX_AGENT_API_KEY`（主推）或 `LINKFOXAGENT_API_KEY`（老规范）任一即可

**billing 场景**：`errcode=402` 或消息含 `算力/余额/quota/insufficient/充值/套餐到期`。
- `python scripts/onboarding.py list-plans` → 有 AskUserQuestion 就弹菜单，否则输出编号清单让用户选
- 校验 `plan_id` ∈ 清单、支付方式 ∈ 该套餐 `available_methods`（通常 `wechat/alipay`）
- `python scripts/onboarding.py order <plan_id> <method>` → 展示优先级 PNG > `pay_url` > `ascii_qr`（标注兜底）
- 已付款可选调 `python scripts/onboarding.py query <order_id>`，不主动轮询

排除 `errcode=403`（无权限，不归入这两类）。所有子命令输出 stdout JSON，`error` 字段已含阶段前缀，透传给用户即可。完整用法：`python scripts/onboarding.py --help`。

skill-card.md

## Description:

Helps agents manage Amazon store Feed workflows for bulk inventory or listing data, including creating feed documents, uploading feed content to presigned URLs, submitting feeds, checking status, retrieving result documents, and cancelling feeds.

This skill is ready for commercial/non-commercial use.

## Publisher:

[linkfox-ai](https://clawhub.ai/user/linkfox-ai)

### License/Terms of Use:

MIT-0

## Use Case:

External users and developers use this skill to automate Amazon SP-API Feeds tasks for bulk store data updates, including feed document creation, upload, submission, polling, result retrieval, and cancellation. It is intended for workflows that already have LinkFox authorization and the required Amazon Feeds permissions.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill handles login, API keys, billing flows, feed uploads, and saved response files that may contain seller data or presigned URLs.

Mitigation: Use a least-privilege LinkFox key, upload only explicit feed files to fresh Amazon presigned URLs, avoid endpoint override environment variables unless you control them, and clean up saved linkfox response files after use.

Risk: Repeated bad requests, authorization failures, missing resources, or high-frequency polling can trigger Amazon SP-API store-protection cooldown behavior.

Mitigation: Stop automatic retries, fix parameters or authorization before retrying, follow retryAfter or blockedUntil when present, and reduce polling or pagination frequency.

## Reference(s):

- [ClawHub skill page](https://clawhub.ai/linkfox-ai/skills/linkfox-amazon-store-feeds)
- [API reference](references/api.md)
- [Onboarding and authentication guidance](references/onboarding.md)
- [Amazon SP-API createFeedDocument](https://developer-docs.amazon.com/sp-api/reference/createfeeddocument)
- [Amazon SP-API getFeedDocument](https://developer-docs.amazon.com/sp-api/reference/getfeeddocument)
- [Amazon SP-API createFeed](https://developer-docs.amazon.com/sp-api/reference/createfeed)
- [Amazon SP-API getFeed](https://developer-docs.amazon.com/sp-api/reference/getfeed)
- [Amazon SP-API getFeeds](https://developer-docs.amazon.com/sp-api/reference/getfeeds)
- [Amazon SP-API cancelFeed](https://developer-docs.amazon.com/sp-api/reference/cancelfeed)
- [Amazon Feed Type Values](https://developer-docs.amazon.com/sp-api/docs/feed-type-values)

## Skill Output:

**Output Type(s):** [text, markdown, shell commands, configuration, guidance]

**Output Format:** [Markdown guidance with Python shell commands and JSON response summaries]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Scripts persist full JSON responses under a local linkfox session directory and print full or summarized JSON to stdout.]

## Skill Version(s):

1.0.8 (source: server release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generate

Github ReposUpdated 16h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.