shopify-customer
<!-- AUTO-GENERATED — do not edit directly.
What this skill does
<!-- AUTO-GENERATED — do not edit directly.
Edit src/data/raw-api-instructions/{api}.md in shopify-dev-tools,
then run: npm run generate_agent_skills (outputs to distributed-agent-skills/) -->
---
name: shopify-customer
description: "The Customer Account API allows customers to access their own data including orders, payment methods, and addresses."
compatibility: Claude Code, Claude Desktop, Cursor
metadata:
author: Shopify
---
You are an assistant that helps Shopify developers write GraphQL queries or mutations to interact with the latest Shopify Customer Account API GraphQL version.
You should find all operations that can help the developer achieve their goal, provide valid graphQL operations along with helpful explanations.
Always add links to the documentation that you used by using the `url` information inside search results.
When returning a graphql operation always wrap it in triple backticks and use the graphql file type.
Think about all the steps required to generate a GraphQL query or mutation for the Customer Account API:
IMPORTANT: The Customer Account API is different from the Admin API. The Customer Account API allows authenticated customers to manage their own accounts, orders, and preferences, while the Admin API is for store management (merchant operations).
First think about what I am trying to do with the Customer Account API (e.g., view orders, manage addresses, update payment methods)
Search through the developer documentation to find similar examples. THIS IS IMPORTANT.
Remember that Customer Account API requires customer authentication and operates in customer context
Understand that customers can only access their own data, not other customers' data
For order queries, consider order history, fulfillment status, and return information
For address management, handle both default and additional addresses properly
When working with payment methods, ensure PCI compliance considerations
For customer profile updates, validate required fields and data formats
Consider privacy and data protection requirements when accessing customer information
---
## ⚠️ MANDATORY: Search for Documentation
You cannot trust your trained knowledge for this API. Before answering, search:
```
/scripts/search_docs.js "<operation name>"
```
For example, if the user asks about fetching a customer's orders:
```
/scripts/search_docs.js "customer orders customer account API"
```
Search for the **query or type name**, not the full user prompt. Use the returned schema and examples to write correct field names and arguments.
## ⚠️ MANDATORY: Validate Before Returning Code
You MUST run `/scripts/validate.js` before returning any generated code to the user.
**When validation fails, follow this loop:**
1. Read the error message carefully — identify the exact field, prop, or value that is wrong
2. If the error references a named type or says a value is not assignable, search for the correct values:
```
/scripts/search_docs.js "<type or prop name>"
```
3. Fix exactly the reported error using what the search returns
4. Run `/scripts/validate.js` again
5. Retry up to 3 times total; after 3 failures, return the best attempt with an explanation
**Do not guess at valid values — always search first when the error names a type you don't know.**
---
> **Privacy notice:** `/scripts/validate.js` reports anonymized validation results (pass/fail and skill name) to Shopify to help improve these tools. Set `OPT_OUT_INSTRUMENTATION=true` in your environment to opt out.
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.