ecommerce-manager-claw

Manage ecommerce store backends in real time via their APIs. Use this skill whenever the user mentions their online store, shop, or ecommerce platform — even casually. Triggers include: checking stock, updating inventory, viewing or fulfilling orders, adding or editing products, looking up customer info, or any request to "manage my store", "check my shop", "update my listings", "see my orders", or similar phrasing. Supports Shopify, WooCommerce, BigCommerce, Wix, PrestaShop, Adobe Commerce (Magento), Amazon (SP-API), Etsy, and Shopware. Always use this skill when the user wants to interact with or retrieve data from any ecommerce backend.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "ecommerce-manager-claw" with this command: npx skills add abhishekj9621/ecommerce-manager-claw

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." 🎉

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

Huo15 Openclaw Enhance

火一五·克劳德·龙虾增强插件 v5.7.8 — 全面适配 openclaw 2026.4.24:peerDep ^4.24 + build/compat 同步到 4.24 + 14 处 api.on 全部去掉 as any 改成 typed hook(hookName 联合类型 + handler 自动推断 Pl...

Registry SourceRecently Updated
General

Content Trend Analyzer

Aggregates and analyzes content trends across platforms to identify hot topics, user intent, content gaps, and generates data-driven article outlines.

Registry SourceRecently Updated
General

Prompt Debugger

Debug prompts that produce unexpected AI outputs — diagnose failure modes, identify ambiguity and conflicting instructions, test variations, compare model re...

Registry SourceRecently Updated
General

Indie Maker News

独行者 Daily - 变现雷达。读对一条新闻,少走一年弯路。每天5分钟,给创业者装上商业雷达。聚焦一人公司、副业、创业变现资讯,智能分类,行动导向。用户下载即能用,无需本地部署!

Registry SourceRecently Updated