What makes Shopee-店铺授权 notable?

972 downloads. Trust evidence available

How should Shopee-店铺授权 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

Shopee-店铺授权

Shopee（虾皮）店铺授权与管理技能，支持 ERP 与广告（AD）双应用分开授权。提供授权流程、已授权店铺查询以及授权状态读取。授权时可填写店铺名 shopName，region 支持 cn / global / br，appType 支持 erp / ad。当用户提到 Shopee 店铺授权、虾皮店铺绑定、ERP 授权、广告授权、appType、查询已授权 Shopee 店铺、Shopee seller authorization, bind Shopee shop, Shopee Ads authorization 时触发。即使未明确提及"Shopee"或"授权"，只要涉及虾皮卖家账号绑定、ERP/广告应用授权或店铺列表查询，也应触发。 Skill: Shopee-店铺授权 Owner: linkfox-ai Summary: Shopee（虾皮）店铺授权与管理技能，支持 ERP 与广告（AD）双应用分开授权。提供授权流程、已授权店铺查询以及授权状态读取。授权时可填写店铺名 shopName，region 支持 cn / global / br，appType 支持 erp / ad。当用户提到 Shopee 店铺授权、虾皮店铺绑定、ERP 授权、广告授权、appType、查询已授权 Shopee 店铺、Shopee seller authorization, bind Shopee shop, Shopee Ads authorization 时触发。即使未明确提及"Shopee"或"授权"，只要涉及虾皮卖家账号绑定、ERP/广告应用授权或店铺列表查询，也应触发。 Tags: latest:1.0.5 Version history: v1.0.5 | 202

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

972

Updated

Oct 11, 2026

Version

1.0.5

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 972 downloads reported by the source. Last updated 10/11/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 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 972 downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.5release · observed Aug 14, 2026
Handshake status: UNKNOWNsecurity

What changed

Newest first. Only changes that point at a source are listed.

Release 1.0.5release
Update from 1.0.4 to 1.0.5
Observed Aug 14, 2026 · source

Install and run

Setup complexity: low.

clawhub skill install s171g8b6m2khwdy9ye8bxj0wx183vd4z:linkfox-shopee-store-auth

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-shopee-store-auth/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

81,447 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: linkfox-shopee-store-auth
description: Shopee（虾皮）店铺授权与管理技能，支持 ERP 与广告（AD）双应用分开授权。提供授权流程、已授权店铺查询以及授权状态读取。授权时可填写店铺名 shopName，region 支持 cn / global / br，appType 支持 erp / ad。当用户提到 Shopee 店铺授权、虾皮店铺绑定、ERP 授权、广告授权、appType、查询已授权 Shopee 店铺、Shopee seller authorization, bind Shopee shop, Shopee Ads authorization 时触发。即使未明确提及"Shopee"或"授权"，只要涉及虾皮卖家账号绑定、ERP/广告应用授权或店铺列表查询，也应触发。
---

# Shopee 店铺授权与管理

Shopee Open Platform 的 OAuth 授权、已授权店铺列表、授权状态读取。**下游业务的前置依赖**（经 `/shopee/developerProxy` 调用开放接口）。

Shopee **ERP** 与 **广告（AD）** 使用不同应用与 Token，必须按能力分开授权。

## Core Concepts

- **双应用**：`appType=erp`（商品/订单/物流等，默认）与 `appType=ad`（站内广告）彼此独立；同店可同时有两条授权
- **授权流程**：生成 URL → 用户浏览器授权 → Shopee 推送 Token → 系统按 `state` 落库
- **店铺标识**：`shopId` 与 `merchantId` 二选一即可定位；判断是否已授权须同时匹配 **`shopId/merchantId + appType`**
- **shopName 建议填写**：调 `authorize_url.py` 前建议问用户要一个便于识别的店铺名（API 非必填）
- **授权 URL 1 小时有效**：每次授权重新调用 `authorize_url.py`，不要缓存旧地址
- **下游选店**：业务 skill 经 `developerProxy` 只传 **`shopId`/`merchantId` + path**；**勿**传 `accessToken`，也**勿**在 proxy 里传 `appType`（服务端按 path 自动路由：`api/v2/ads/**` → AD，其它 `api/v2/**` → ERP）
- **accessToken 约 4 小时有效**（`expireIn` 通常 14400）；过期需按对应 `appType` 重新授权

## Shopee authorization routing

- Use `appType=erp` for product, order, logistics, and other ERP authorization.
- Use `appType=ad` for Shopee Ads authorization.
- Treat a missing or blank `appType` as `erp`.
- Check authorization by both store identity and `appType`; one store may have separate ERP and AD records.
- If the user needs both capabilities, obtain two fresh authorization URLs and explain that both authorizations must be completed.
- Authorization URLs expire after one hour, so obtain a new URL for every authorization attempt.

When calling `developerProxy`, pass the Shopee API path plus `shopId` or `merchantId`. Do not pass `appType` or an access token. The service routes `api/v2/ads/**` through the AD application and all other `api/v2/**` paths through the ERP application.

## 可用脚本

| 脚本 | 作用 |
|------|------|
| `authorize_url.py` | 生成授权 URL（可选 `shopName` / `region` / **`appType`**） |
| `authorized_stores.py` | 列出已授权店铺（含 **`appType`**；同店可能两条） |
| `store_tokens.py` | 查指定应用的授权/令牌**状态**（非下游 token 来源；须带 `appType` 区分） |

入参、响应字段、错误码见 `references/api.md`。

## 调用方式

- **API 端点**：`POST /shopee/{authorizeUrl|storeTokens|authorizedStores}`（完整参数/响应/错误码见 `references/api.md`）
- **Python 脚本**：`python scripts/<脚本名>.py '<JSON 参数>' [--inline]`（可用脚本见上文）
- **成本约束**：本工具会消耗积分；失败/空结果不得自动连续试探；需要继续检索时先向用户说明会产生额外消耗。

**输出策略（脚本默认行为）**：
- **始终**将完整响应写入 `<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/<skill-name>-<timestamp>.json`（`<cwd>` 为脚本执行时的工作目录，在 Claude Code 里即当前项目目录；`<session>` 取自环境变量 `SESSION_ID`，按用户任务自动聚合；**禁止写入 /tmp**，当前目录不可写则报错）
- 响应体 ≤ 8 KB：落盘后把完整 JSON 打印到 stdout
- 响应体 > 8 KB：落盘后 stdout 只输出摘要（顶层字段、常见计数、最大列表字段的长度 + 前 3 条样本）
- 加 `--inline` 强制全量打印到 stdout（同样落盘）

**读数据建议**：先看摘要判断是否足够；需要具体字段时优先用 `jq`或`ConvertFrom-Json` 从保存的 json 文件按需抽取，避免整份 JSON 进入上下文。

## 解决认证和积分问题
发生以下异常情况时，采用 references/onboarding.md 引导解决问题：

_meta.json

{
  "ownerId": "kn7dmc1t4j28hem1twwyav85p182pb1j",
  "slug": "linkfox-shopee-store-auth",
  "version": "1.0.5",
  "publishedAt": 1786719748868
}

references/api.md

# linkfox-shopee-store-auth — 参数与字段参考

Shopee 授权、已授权店铺列表、授权状态读取。支持 **ERP / AD** 双应用。

业务 API 转发见 `/shopee/developerProxy`（path 须以 `api/v2` 开头；**勿**传 `accessToken` / `appType`）。

## 通用约定

- **Base URL**：`${LINKFOX_TOOL_GATEWAY}`
- **Method**：POST，`Content-Type: application/json`
- **Auth**：Header `Authorization: <api_key>`（读环境变量 `LINKFOX_AGENT_API_KEY` 或 `LINKFOXAGENT_API_KEY`；如未配置 按 SKILL.md 的 **## 解决认证和积分问题** 处理）

## 关键 ID 与应用类型

```
  一次 OAuth 授权（指定 appType）
        ▼
  authRecordId (1 条)  ← 与该应用的 access/refresh token 绑定
        │
        ├──► shopId      ─┐
        ├──► merchantId  ─┘  查询时二选一即可
        └──► appType: erp | ad
```

- `authRecordId`：授权记录 ID；同一店铺可因 `appType` 不同有多条
- `shopId`：店铺 ID，转发 Shopee API 时写为 `shop_id`
- `merchantId`：商户 ID，与 `shopId` 二选一；转发时写为 `merchant_id`
- `appType`：`erp`（默认）或 `ad`；空/`null` 在展示与 ERP 查找时视为 `erp`
- `shopIdList` / `merchantIdList`：JSON 字符串，含本次授权绑定的全部 ID

判断是否已授权须同时匹配：**店铺标识 + appType**。

## 接口

### 1. 生成授权 URL — `/shopee/authorizeUrl`

服务端自动组装 `state`、`callbackUrl`、`redirectUrl`。授权地址约 **1 小时**有效，每次重新获取。

**Request**：
| 参数 | 类型 | 必填 | 默认 | 说明 |
|------|------|------|------|------|
| `shopName` | string | 否 | - | 店铺展示名，便于在列表识别 |
| `region` | string | 否 | `cn` | `cn` / `global` / `br` |
| `appType` | string | 否 | `erp` | 只允许 `erp` 或 `ad` |

**Response**：
```json
{"sourceType": "shopee", "authorizeUrl": "https://open.shopee.cn/auth?...&state=abc123"}
```

授权完成后 Token 由 Shopee POST 到 `/shopee/oauth/tokenCallback`（系统内部）；浏览器跳转 `/shopee/oauth/redirect`，不作为公开接口。

ERP 示例：
```json
{"shopName": "Example Shop", "region": "cn", "appType": "erp"}
```

广告示例：
```json
{"shopName": "Example Shop", "region": "cn", "appType": "ad"}
```

---

### 2. 列已授权店铺 — `/shopee/authorizedStores`

**Request**：无（用当前用户上下文）

**Response**：
```json
{
  "total": 2,
  "stores": [
    {
      "authRecordId": 1,
      "shopId": "67890",
      "merchantId": "12345",
      "shopIdList": "[67890]",
      "merchantIdList": "[12345]",
      "shopName": "Test Shopee Shop",
      "region": "cn",
      "appType": "erp"
    },
    {
      "authRecordId": 2,
      "shopId": "67890",
      "merchantId": "12345",
      "shopName": "Test Shopee Shop",
      "region": "cn",
      "appType": "ad"
    }
  ]
}
```

同一个店铺可能返回 ERP、AD 两条。缺 `appType` 的历史记录按 **erp** 理解。

---

### 3. 查询授权状态 — `/shopee/storeTokens`

只返回授权状态/元数据，**不返回**原始 access token 或 refresh token（脚本侧也会剥离）。

**Request**（`shopId` 与 `merchantId` 二选一）：
| 参数 | 类型 | 必填 | 默认 | 说明 |
|------|------|------|------|------|
| `shopId` | string | 与 merchantId 二选一 | - | 店铺 ID |
| `merchantId` | string | 与 shopId 二选一 | - | 商户 ID |
| `appType` | string | 否 | `erp` | `erp` 或 `ad` |

**Response（状态示例）**：
```json
{
  "authRecordId": 1,
  "shopId": "67890",
  "merchantId": "12345",
  "appType": "ad",
  "tokenType": "Bearer",
  "expireIn": 14400,
  "status": "ok"
}
```

本接口**不触发刷新**，仅读 DB。`expireIn` 为 access_token 剩余有效秒数（通常 14400）。

**不要**用本接口取 token 再传给 `/shopee/developerProxy`；proxy 由服务端按 path 注入对应应用 Token。

---

### 4. 业务转发

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>`（workbuddy 宿主加 `--channel workbuddy`）
   - 拿到 `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:

Supports Shopee store authorization and management for separate ERP and Ads applications, including OAuth URL generation, authorized-store lookup, and authorization-status checks.

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 sellers, operators, and developers use this skill to bind Shopee stores to LinkFox, distinguish ERP and Ads authorization records, and confirm which store identity and application type are ready for downstream Shopee workflows.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill uses LinkFox account access and sends credential-bearing requests to configurable LinkFox endpoints.

Mitigation: Install only after reviewing the publisher, and run it in a clean environment with trusted LINKFOX_* URL variables.

Risk: OAuth authorization URLs and API responses may be copied to the clipboard or retained in local linkfox output directories.

Mitigation: Avoid shared machines, avoid exposing terminal output, and inspect or delete generated linkfox cache files after use.

Risk: The onboarding flow can request phone verification codes and create paid billing orders.

Mitigation: Provide phone codes or payment confirmation only when you explicitly intend to set up or purchase LinkFox service access.

Risk: Automatic feedback reporting may send skill feedback to LinkFox.

Mitigation: Do not include secrets, authorization URLs, shop identifiers, or other sensitive business data in feedback content.

## Reference(s):

- [API Reference](references/api.md)
- [Authentication and Billing Onboarding](references/onboarding.md)
- [ClawHub Skill Page](https://clawhub.ai/linkfox-ai/skills/linkfox-shopee-store-auth)
- [Publisher Profile](https://clawhub.ai/user/linkfox-ai)

## Skill Output:

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

**Output Format:** [Markdown guidance with JSON API responses and shell command examples]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Scripts persist full API responses under a local linkfox session directory and may print full or summarized JSON depending on response size.]

## Skill Version(s):

1.0.5 (source: server release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 3d 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.

MCPOPENCLAW

Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular