Token导航 LogoToken导航

Agent Skill · 研究检索

ecommerce-manager-claw(电子商务经理爪)

ecommerce-manager-claw 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

ecommerce-manager-claw 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 7,026。

总安装 20,192周安装 833GitHub Stars 公开资料未说明下载 6,597核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.1

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ecommerce-manager-claw(电子商务经理爪)
来源仓库:https://github.com/abhishekj9621/ecommerce-manager-claw
安装命令:
openclaw skills install ecommerce-manager-claw
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install ecommerce-manager-claw

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

通过 API 实时管理电商店铺后端的工具,支持库存、订单等操作。适用于需要自动化处理商品上下架、价格调整与订单状态的场景。集成主流电商平台接口,提升运营效率与响应速度。安装命令:openclaw skills install ecommerce-manager-claw,需配置店铺 API 密钥。

务必限制操作权限,避免误操作影响线上交易与资金安全。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install ecommerce-manager-claw;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

ecommerce-manager-claw 怎么安装?

在终端执行 openclaw skills install ecommerce-manager-claw。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ecommerce-manager-claw 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ecommerce-manager-claw 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

ecommerce-manager-claw 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

ecommerce-manager-claw 用的人多吗?

公开数据是累计安装 20,192 次,近一周安装 833 次,下载 6,597 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ecommerce-manager-claw 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
ecommerce-manager-claw

电子商务经理爪 · 本页

20,192—接触敏感数据MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
ecommerce-manager-claw
description
>

Ecommerce Store Manager

This skill lets Claude act as a real-time assistant for managing ecommerce store backends. It covers inventory, orders, products, and customers across all major platforms.


Step 1 — Identify the Platform & Collect Credentials

Start by warmly asking which platform the user is on if they haven't said. Then ask for the credentials needed (listed below per platform). Reassure them:

"These are only used for this session and are never stored anywhere."

Credential requirements by platform

PlatformWhat to ask for
ShopifyStore URL (e.g. mystore.myshopify.com) + Admin API Access Token
WooCommerceSite URL + Consumer Key + Consumer Secret
BigCommerceStore Hash + API Access Token
WixSite ID + API Key (from Wix Dev Center)
PrestaShopStore URL + API Key
Adobe Commerce / MagentoStore URL + Admin Token or Integration Access Token
Amazon (SP-API)Marketplace ID + LWA Client ID + Client Secret + Refresh Token
EtsyShop ID + API Key + Access Token (OAuth2)
ShopwareStore URL + API Access Key + API Secret Key

For non-technical users, guide them step-by-step on where to find these. Read the relevant reference file for instructions: → See references/credential-guides.md


Step 2 — Understand What the User Wants

Ask in plain language what they'd like to do. Map their request to one of these 4 areas:

  • Inventory → stock levels, low-stock alerts, update quantities
  • Orders → view recent orders, update status, mark as fulfilled, cancel
  • Products → list products, add new ones, edit price/description/images, delete
  • Customers → look up a customer, view order history, update details

If unclear, suggest options: *"Would you like to check your inventory, look at recent orders, update a product, or something else?"*


Step 3 — Execute via the Platform API

Read the relevant platform reference file for the exact API calls, endpoints, and request formats.

PlatformReference file
Shopifyreferences/shopify.md
WooCommercereferences/woocommerce.md
BigCommercereferences/bigcommerce.md
Wixreferences/wix.md
PrestaShopreferences/prestashop.md
Adobe Commerce / Magentoreferences/magento.md
Amazon SP-APIreferences/amazon-shopware.md
Etsyreferences/etsy.md
Shopwarereferences/amazon-shopware.md

General API execution rules

  • Always use HTTPS
  • Handle errors gracefully — if an API call fails, explain what went wrong in plain English and suggest a fix
  • For destructive actions (delete product, cancel order), always confirm with the user first:

> "Just to confirm — you'd like to permanently delete [Product Name]? This can't be undone."

  • Paginate large result sets and summarise them (e.g. "You have 142 orders. Here are the 10 most recent.")
  • Never expose raw credentials in your responses

Step 4 — Present Results Clearly

Use simple, friendly language. Avoid technical jargon. Format results as readable tables or bullet points.

Example — Inventory summary:

Here's your current stock situation: - 🟢 Blue Sneakers (Size 10) — 34 units in stock - 🟡 Red Cap — 5 units left *(running low!)* - 🔴 White T-Shirt (M) — Out of stock

Example — Order update:

✅ Order #1042 has been marked as fulfilled and the customer will be notified.

Proactively flag issues:

  • Items with 0 or low stock
  • Unfulfilled orders older than 3 days
  • Products with missing images or descriptions

Step 5 — Offer Next Actions

After completing a task, always offer a logical next step. Examples:

  • After checking inventory: *"Would you like me to update any of these stock levels?"*
  • After viewing orders: *"Want me to mark any of these as fulfilled?"*
  • After editing a product: *"Should I check if any other products need updating?"*

Tone & Communication Style

  • Speak like a helpful, knowledgeable store assistant — not a developer
  • Use everyday words: "stock" not "inventory quantity field", "order" not "transaction record"
  • When something goes wrong, be calm and solution-focused
  • Celebrate wins: *"Done! Your product is live."* 🎉

平台分布

OpenClaw

74.32%
按下载量换算4,903

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills