ce

Route storefront tasks to Commerce Engine sub-skills via decision-tree routing.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/commercengine/skills --skill ce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce
Source: https://github.com/commercengine/skills/tree/main/skills/ce
Command: npx skills add https://github.com/commercengine/skills --skill ce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routes storefront-related tasks to the correct Commerce Engine sub-skills, reducing context-switching and response time for agents.

Core Features & Use Cases

  • Routing: Analyze user intent and forward requests to the appropriate sub-skill (ce-setup, ce-auth, ce-catalog, ce-cart-checkout, ce-orders, ce-webhooks, ce-nextjs-patterns).
  • Scalability: Easily extendable to accommodate new sub-skills as the platform grows.
  • Use Case: An agent asks to set up the SDK and fetch product data; the router directs to ce-setup first, then ce-catalog as needed.

Quick Start

Route a user request to the appropriate Commerce Engine sub-skill (ce-setup, ce-auth, ce-catalog, ce-cart-checkout, ce-orders, ce-webhooks, ce-nextjs-patterns) based on their described task.

Frequently Asked Questions about ce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route storefront tasks to the correct Commerce Engine sub-skill?

To route storefront tasks, use a decision-tree router that analyzes user intent and forwards requests to the appropriate Commerce Engine sub-skill, reducing agent context-switching and response time.

What storefront operations does the Commerce Engine routing support?

Commerce Engine routing supports storefront operations including SDK setup, authentication, catalog management, cart, checkout, orders, webhooks, and Next.js patterns by directing tasks to specialized sub-skills.

Can I use this router for both Next.js patterns and webhook configurations?

Yes, you can use this router for Next.js patterns and webhook configurations, as it forwards user intents to dedicated sub-skills like ce-nextjs-patterns and ce-webhooks automatically.

How do I handle an agent request to set up the SDK and fetch catalog data?

To handle setting up the SDK and fetching catalog data, the router directs the agent to the ce-setup sub-skill first, then forwards to the ce-catalog sub-skill as needed.

What is the best way to scale routing when new Commerce Engine sub-skills are added?

The best way to scale routing for new sub-skills is to use the router's extensible design, which easily accommodates new Commerce Engine platform modules without breaking existing decision-tree logic.