Run ecommerce operator skills across marketplace workflows
Use eCommerce-Skills to give compatible agents plain-text workflows for product research, listing optimization, review analysis, pricing, marketing, supply-chain checks, and growth planning for online sellers.
npx skills add agentskillexchange/skills --skill run-ecommerce-operator-skills-across-marketplace-workflows
Use eCommerce-Skills when an online-seller workflow needs a domain-specific agent playbook rather than a generic marketing or analytics prompt. The operator installs all skills or a named skill from the repository, then asks a compatible assistant to run focused ecommerce tasks such as Amazon or Shopify growth planning, product research, listing audits, review analysis, pricing checks, competitor comparisons, marketing automation, supply-chain review, or business analytics.
What this skill actually does
Invoke it instead of using marketplace dashboards normally when the task is planning, analysis, copy review, or decision support that should happen inside an agent session and remain reviewable before any store action. The scope boundary is the installed markdown skill pack and its named ecommerce workflows. It is not an ecommerce platform, Shopify or Amazon API connector, agency service, or generic business-advice listing.
Inputs and prerequisites: Node.js and npx skills CLI; compatible Skills host such as OpenClaw, Claude Code, Cursor, Windsurf, Codex, or another markdown-skill-capable agent.
Setup notes: Install the full skill pack with npx skills add nexscope-ai/eCommerce-Skills -g, or install one workflow with npx skills add nexscope-ai/eCommerce-Skills –skill -g, such as –skill ecommerce-growth-strategy. Restart or reload the target assistant before invoking the installed ecommerce workflow.
Source and verification boundary: use https://github.com/nexscope-ai/eCommerce-Skills as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.