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

亚马逊-店铺买家反馈

亚马逊商品与类目买家反馈洞察。用于按 ASIN 或 browse node 查询评论主题、主题提及量、星级影响、评价趋势、退货主题和退货趋势，帮助分析产品口碑及类目问题。用户提到亚马逊评论分析、评价主题、差评原因、评论趋势、退货原因、退货趋势、ASIN 口碑洞察、类目反馈、MENTIONS、STAR_RATING_IMPACT、Customer Feedback API 时触发。即使未明确提及 API，只要希望从聚合反馈中判断某个亚马逊商品或类目的常见好评、差评或退货问题，也应触发此技能。 Skill: 亚马逊-店铺买家反馈 Owner: linkfox-ai Summary: 亚马逊商品与类目买家反馈洞察。用于按 ASIN 或 browse node 查询评论主题、主题提及量、星级影响、评价趋势、退货主题和退货趋势，帮助分析产品口碑及类目问题。用户提到亚马逊评论分析、评价主题、差评原因、评论趋势、退货原因、退货趋势、ASIN 口碑洞察、类目反馈、MENTIONS、STAR_RATING_IMPACT、Customer Feedback API 时触发。即使未明确提及 API，只要希望从聚合反馈中判断某个亚马逊商品或类目的常见好评、差评或退货问题，也应触发此技能。 Tags: latest:1.0.8 Version history: v1.0.8 | 2026-09-14T04:56:07.576Z | user Update from 1.0.7 to 1.0.8 v1.0.7 | 2026-08-14T14:

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-customer-feedback

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-customer-feedback/snapshot"

Documentation

CLAWHUB

100,788 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: linkfox-amazon-store-customer-feedback
description: 亚马逊商品与类目买家反馈洞察。用于按 ASIN 或 browse node 查询评论主题、主题提及量、星级影响、评价趋势、退货主题和退货趋势，帮助分析产品口碑及类目问题。用户提到亚马逊评论分析、评价主题、差评原因、评论趋势、退货原因、退货趋势、ASIN 口碑洞察、类目反馈、MENTIONS、STAR_RATING_IMPACT、Customer Feedback API 时触发。即使未明确提及 API，只要希望从聚合反馈中判断某个亚马逊商品或类目的常见好评、差评或退货问题，也应触发此技能。
---

# Amazon 店铺 Customer Feedback

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

> 说明：接口属于 **Customer Feedback（买家评论/退货洞察）**，不是 Orders 订单 API。订单见 **`linkfox-amazon-store-orders`**。

## 调用方式

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

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

## 官方参考索引

| 能力 | 文档 |
|------|------|
| getItemReviewTopics | [getItemReviewTopics](https://developer-docs.amazon.com/sp-api/reference/getitemreviewtopics) |
| getItemBrowseNode | [getItemBrowseNode](https://developer-docs.amazon.com/sp-api/reference/getitembrowsenode) |
| getBrowseNodeReviewTopics | [getBrowseNodeReviewTopics](https://developer-docs.amazon.com/sp-api/reference/getbrowsenodereviewtopics) |
| getItemReviewTrends | [getItemReviewTrends](https://developer-docs.amazon.com/sp-api/reference/getitemreviewtrends) |
| getBrowseNodeReviewTrends | [getBrowseNodeReviewTrends](https://developer-docs.amazon.com/sp-api/reference/getbrowsenodereviewtrends) |
| getBrowseNodeReturnTopics | [getBrowseNodeReturnTopics](https://developer-docs.amazon.com/sp-api/reference/getbrowsenodereturntopics) |
| getBrowseNodeReturnTrends | [getBrowseNodeReturnTrends](https://developer-docs.amazon.com/sp-api/reference/getbrowsenodereturntrends) |

---

## Prerequisites

1. 依赖 **`linkfox-amazon-store-auth`**。
2. 通常需 **Brand Analytics** 或 **Selling Partner Insights** 等角色；站点以官方为准（常见 US/UK/DE 等）。
3. **ASIN** 一般为**子体 ASIN**；topics 类接口需 **`sortBy`**：`MENTIONS` 或 `STAR_RATING_IMPACT`（常各调一次对比）。

---

## Current Capabilities

| 脚本 | path 要点 |
|------|-----------|
| `get_item_review_topics.py` | `.../items/{asin}/reviews/

_meta.json

{
  "ownerId": "kn7dmc1t4j28hem1twwyav85p182pb1j",
  "slug": "linkfox-amazon-store-customer-feedback",
  "version": "1.0.8",
  "publishedAt": 1789361767576
}

references/api.md

# linkfox-amazon-store-customer-feedback — API 参考

Customer Feedback **v2024-06-01**，经 LinkFox `storeTokens` + `developerProxy` 调用。

官方总览：[Customer Feedback API](https://developer-docs.amazon.com/sp-api/docs/customer-feedback-api-v2024-06-01-use-case-guide)

---

## 1. 脚本与 path

| 脚本 | GET path |
|------|----------|
| `get_item_review_topics.py` | `customerFeedback/2024-06-01/items/{asin}/reviews/topics` |
| `get_item_browse_node.py` | `customerFeedback/2024-06-01/items/{asin}/browseNode` |
| `get_item_review_trends.py` | `customerFeedback/2024-06-01/items/{asin}/reviews/trends` |
| `get_browse_node_review_topics.py` | `customerFeedback/2024-06-01/browseNodes/{browseNodeId}/reviews/topics` |
| `get_browse_node_review_trends.py` | `customerFeedback/2024-06-01/browseNodes/{browseNodeId}/reviews/trends` |
| `get_browse_node_return_topics.py` | `customerFeedback/2024-06-01/browseNodes/{browseNodeId}/returns/topics` |
| `get_browse_node_return_trends.py` | `customerFeedback/2024-06-01/browseNodes/{browseNodeId}/returns/trends` |

---

## 2. 公共入参

| 字段 | 必填 | 说明 |
|------|------|------|
| sellerId | 是 | |
| region | 是 | NA / EU / FE 等 |
| marketplaceId | 是 | 单站点；或 `marketplaceIds` 数组取第一个 |
| skipDepCheck | 否 | |

---

## 3. 按接口

### getItemReviewTopics / getBrowseNodeReviewTopics / getBrowseNodeReturnTopics

| 字段 | 必填 |
|------|------|
| asin 或 browseNodeId | 是（按接口） |
| sortBy | 是 | `MENTIONS` \| `STAR_RATING_IMPACT` |

Query：`marketplaceId`、`sortBy`

解析字段：`itemReviewTopics` / `browseNodeReviewTopics` / `browseNodeReturnTopics`

### getItemBrowseNode

| 字段 | 必填 |
|------|------|
| asin | 是 |

Query：`marketplaceId`  
解析字段：`itemBrowseNode`

### getItemReviewTrends / getBrowseNodeReviewTrends / getBrowseNodeReturnTrends

Query：`marketplaceId`  
解析字段：`itemReviewTrends` / `browseNodeReviewTrends` / `browseNodeReturnTrends`

---

## 4. 推荐调用顺序（ASIN）

1. `get_item_review_topics`（`sortBy=MENTIONS` 与 `STAR_RATING_IMPACT` 各一次）
2. `get_item_review_trends`
3. `get_item_browse_node` → 取 `browseNodeId`
4. 对 browse node 调用 review/return 的 topics 与 trends

---

## 5. 限制

- 非订单接口；订单用 **`linkfox-amazon-store-orders`**。
- **401**：HTTP 401 或 authorized error：按 SKILL.md 的 **## 解决认证和算力问题** 处理。
- **402**：HTTP 402：按 SKILL.md 的 **## 解决认证和算力问题** 处理。
- **403**：角色或站点不支持。
- **1005**：网关需放行 `customerFeedback/2024-06-01/`。

---

## 6. Feedback

`skillName`: **`linkfox-amazon-store-customer-feedback`**

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:

Analyzes Amazon item and browse node customer feedback by querying review topics, review trends, return topics, and return trends through the Customer Feedback API.

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:

Amazon sellers, operators, and marketplace analysts use this skill to inspect aggregated review and return feedback for ASINs or browse nodes, including topics, mention volume, star-rating impact, and trend data.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The authoritative security scan marks this release suspicious because it handles seller feedback data, onboarding, billing, API keys, and locally retained response files.

Mitigation: Install only when the publisher is trusted, use scoped pre-provisioned credentials, avoid shared workspaces, and delete retained LinkFox output files when they are no longer needed.

Risk: The artifact supports environment overrides for service URLs used by its scripts.

Mitigation: Prefer the default service endpoints and avoid environment URL overrides unless the replacement endpoint has been reviewed and approved.

Risk: Repeated failed SP-API calls can trigger temporary store/interface protection responses.

Mitigation: Do not retry automatically after repeated 400, 403, 404, or 429 responses; fix parameters or authorization first and respect retry timing before trying again.

## Reference(s):

- [Skill API Reference](references/api.md)
- [Authentication and Billing Onboarding](references/onboarding.md)
- [Amazon Customer Feedback API v2024-06-01 Use Case Guide](https://developer-docs.amazon.com/sp-api/docs/customer-feedback-api-v2024-06-01-use-case-guide)
- [Amazon getItemReviewTopics Reference](https://developer-docs.amazon.com/sp-api/reference/getitemreviewtopics)
- [Amazon getItemBrowseNode Reference](https://developer-docs.amazon.com/sp-api/reference/getitembrowsenode)
- [Amazon getBrowseNodeReviewTopics Reference](https://developer-docs.amazon.com/sp-api/reference/getbrowsenodereviewtopics)
- [Amazon getItemReviewTrends Reference](https://developer-docs.amazon.com/sp-api/reference/getitemreviewtrends)
- [Amazon getBrowseNodeReviewTrends Reference](https://developer-docs.amazon.com/sp-api/reference/getbrowsenodereviewtrends)
- [Amazon getBrowseNodeReturnTopics Reference](https://developer-docs.amazon.com/sp-api/reference/getbrowsenodereturntopics)
- [Amazon getBrowseNodeReturnTrends Reference](https://developer-docs.amazon.com/sp-api/reference/getbrowsenodereturntrends)

## Skill Output:

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

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

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Scripts save full API responses under a local linkfox session data directory and may print either full JSO

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.