Shopify Commerce
PassAudited by ClawScan on May 13, 2026.
Overview
The visible artifacts are a coherent Shopify development guidance pack with no evidence of hidden execution or data exfiltration, though its examples involve high-impact Shopify APIs and credentials that users should approve carefully.
This skill appears safe to install as a Shopify development assistant. Before using it with a real store, keep credentials out of chat, grant the smallest Shopify scopes needed, review generated GraphQL mutations and CLI commands, and avoid live deployments or destructive operations without explicit confirmation.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the agent applies generated mutations or commands with real store credentials, it could change products, orders, customer records, themes, or fulfillment-related data.
The skill teaches use of Shopify Admin API capabilities that can modify important store data. This is aligned with the stated Shopify development purpose, but it is high-impact when applied to a real store.
Admin API (Server-Side) ... Full CRUD on all store resources ... Use for: product management, order processing, customer data, metafields, fulfillment
Use a development store when possible, review all mutations and deploy commands, and require explicit confirmation before write, delete, deploy, or live-theme actions.
Over-broad Shopify scopes could let generated code access or modify more store data than necessary.
The skill discusses OAuth scopes and privileged Shopify access needed for app development. It also advises least privilege, and the artifacts do not show hardcoded credentials or hidden credential use.
Request minimum necessary scopes: ... read_products / write_products ... read_orders / write_orders ... read_customers / write_customers ... read_themes / write_themes
Authorize only the scopes needed for the task, avoid sharing tokens in prompts, store secrets in environment variables or a secrets manager, and test against non-production stores first.