Agent Skills
Agent Skills are SKILL.md guidance files — one per domain — that teach your agent which command to run for each task, along with the domain's fields, boundaries, and safety rules. The CLI works without them, but skills make your agent significantly more accurate.
Install
One command installs the skills for the agent you already use. For the per-agent commands and how to confirm they loaded, see Get started → Add the Agent Skills.
The same skills are also compiled into the CLI binary, so an agent can read the version that matches the installed CLI without installing anything: shoplazza skills list lists them, and shoplazza skills read <name> prints one (start with shoplazza skills read shoplazza-common). Once the skills are installed in ~/.agents/skills/, shoplazza update refreshes them along with the CLI.
Available skills
| Domain | Skill | Covers |
|---|---|---|
| Foundation | shoplazza-common | Auth and profiles, command layers, output envelope, schema introspection, reading filtered lists, and the safety protocol. Every other skill has the agent read it first. |
| Products | shoplazza-products | Create / price / stock / tag / publish products, variants, collections, images, gift cards, reviews, locations, suppliers |
| Discounts | shoplazza-discounts | Tiered rebates, coupon codes, flash sales, buy X get Y, free-shipping codes, coupon campaigns |
| Orders | shoplazza-orders | Search, fulfill, refund, update tracking, cancel, mark paid, transactions, fraud risk, shipping zones |
| Customers | shoplazza-customers | Customer profiles, tags, marketing subscription, addresses |
| Shop | shoplazza-shop | Store settings, metafields, media, analytics, blogs, pages, redirects, markets, languages |
| Themes | shoplazza-themes | Page and card editing, theme settings, app embeds, custom templates, AI-generated blocks, installed themes (not local theme development) |
| Webhook | shoplazza-webhook | Event subscriptions |
| Billing | shoplazza-billing | App charges: one-time, recurring, and usage |
How to invoke a skill
Prefix your request with /shoplazza-<domain>, then describe the task in plain language:
/shoplazza-products Add a new product: Summer print T-shirt, priced 129
The prefix loads that domain's commands and notes into context before the agent acts.
The prefix is not mandatory — each skill also has built-in trigger words — but stating it explicitly is more deterministic. The docs use /shoplazza-<domain> consistently for that reason.
Pick the right domain
Each skill owns exactly one domain. Match the task to the domain:
| Task | Skill |
|---|---|
| Create / price / restock a product, gift cards | /shoplazza-products |
| Tiered discount, coupon code, flash sale | /shoplazza-discounts |
| Ship, refund, or look up orders | /shoplazza-orders |
| Customer profiles and addresses | /shoplazza-customers |
| Store settings, metafields, media, analytics | /shoplazza-shop |
| Store page and card editing, theme settings, templates | /shoplazza-themes |
| Event subscriptions (webhooks) | /shoplazza-webhook |
| App billing — one-time, recurring, usage | /shoplazza-billing |
Domain boundaries to watch
Some tasks sit on a boundary between domains. The skills route them like this:
- Gift cards live in
products, notdiscounts. - Orders by customer email are searched in
orders; the customer profile itself is incustomers. - Buyer refunds live in
orders, not billing. - Page and card editing lives in
themes; the content of custom pages and blogs stays inshop.
The safety protocol
The foundation skill shoplazza-common sets a safety protocol for destructive (cancel, delete), batch, and money-moving writes such as refunds and charges:
- Preview — run the command with
--dry-runto print the request without sending it. - Restate — summarize what the operation will change.
- Confirm — wait for your explicit confirmation before executing.
Other writes, such as creating a product or discount with a + shortcut, run directly once the required values are confirmed; the agent asks for a missing price or amount instead of inventing one. See the refund and delete examples for the protocol in action.