Business Skills
Save useful Claude workflows as reusable, governed store operations.
Business Skills let a merchant turn a successful conversation with Claude into a reusable workflow.
The important detail is that a Business Skill is not just a saved prompt. SHOPMCP stores a structured definition of what the Skill is allowed to do, which tools it may use, which writes are blocked or require confirmation, and how each run should be recorded.
Business Skill vs Operation
A Business Skill keeps Claude reasoning at the center. An Operation is the compiled, repeatable execution layer for stable parts of a Skill, such as a scheduled review or recurring check.
What a Business Skill is
A Business Skill is a reusable merchant workflow created from a successful Claude conversation.
Examples:
- Review discounted product performance
- Find catalog items losing revenue while inventory remains high
- Check products with weak descriptions, missing images, or stale pricing
- Review refund patterns for recent orders
- Prepare a weekly inventory risk summary
Skills are useful when the workflow depends on business judgment, live store context, and explanation. Claude can choose the right supported read tools, compare results, and explain the outcome in merchant language.
What an Operation is
An Operation is a compiled, deterministic version of a repeatable workflow step.
Operations are useful when the system should run the same bounded workflow again:
- manually from the dashboard
- once at a selected time
- on a recurring schedule
- from a supported Shopify event, where appropriate
An Operation does not replace Claude reasoning for open-ended analysis. It exists for repeatability, scheduling, run history, and auditability.
How a Skill is created
Creation should happen through conversation, not a manual form builder.
The normal flow is:
- A merchant asks Claude to complete a real task.
- Claude uses the supported SHOPMCP tools to do the work.
- The merchant says something like "Save this as Product Health Review."
- SHOPMCP converts the understood workflow into a structured Skill definition.
- The definition is validated against allowed tools, scopes, and safety rules.
- The Skill is saved with a version, permission boundary, and audit trail.
The saved Skill should capture the intent and constraints of the workflow, not a verbatim copy of the original prompt.
Example: discounted product performance review
Merchant request:
Claude may use supported tools such as:
list_discountslist_orderslist_productsget_product
The Skill can compare discounted product sales against the previous non-discounted period, identify whether discount codes were actually used, and explain whether the discount activity created meaningful order volume or revenue.
If there is no discount usage, the correct result is not invented analysis. The Skill should report that there is no real discounted order data to compare and explain what data is missing.
Permissions and safety
Every Skill has an explicit permission boundary.
For example, a discounted product performance review may allow:
| Permission | Why it is needed |
|---|---|
discounts:read | Find active discounts and usage |
orders:read | Compare order volume and revenue |
products:read | Match discounted items to products and variants |
The same Skill should deny write scopes unless the workflow truly needs them.
Sensitive writes still use SHOPMCP's staged action model. Claude can propose a refund, fulfillment, inventory adjustment, price change, or discount change, but the action does not execute until an authorized user confirms it.
Running and inspecting Skills
The Business Skills dashboard is for management and inspection, not manual Skill building.
From the dashboard, merchants should be able to:
- view saved Skills
- inspect the current Skill definition
- see linked Operations
- pause, resume, or archive Skills
- review recent runs and run history
- inspect failures, tool usage, and audit events
The dashboard should make it clear whether a run was Claude-assisted or deterministic, whether it completed successfully, and whether any action was staged for approval.
Scheduling
Scheduled work should use Operations, not raw prompts.
Supported scheduling modes:
| Mode | Use case |
|---|---|
| Manual | Run a Skill or Operation when a merchant asks |
| Once | Run a bounded Operation at a selected future time |
| Recurring | Run a repeatable review on a schedule |
| Event-driven | Trigger a bounded Operation from a supported Shopify webhook |
For V1, scheduling should stay conservative. Read-only checks and summaries are the best fit. Writes should remain approval-gated.
Auditability
Every Skill and Operation run should keep enough history to answer:
- who started it
- which merchant workspace it ran against
- which tools were used
- what inputs were used
- whether anything was staged for approval
- whether it succeeded, failed, or was cancelled
- what changed in Shopify, if anything
This makes Business Skills part of the same governed connector model as the rest of SHOPMCP.
V1 boundaries
Business Skills V1 should not include:
- a drag-and-drop builder
- arbitrary code execution
- unbounded background agents
- silent writes to Shopify
- automatic creation of unsupported tools
- cross-store shared Skills without review
If a workflow needs a Shopify capability that SHOPMCP does not expose yet, the Skill should stop and say which capability is missing.
What to read next
Was this page helpful?
Your feedback helps keep this documentation accurate and useful.