shopify-customer

The Customer Account API allows customers to access their own data including orders, payment methods, and addresses.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/shopify/skills/shopify-customer/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a strong, well-validated workflow, but it pays for repeated command templates and mandatory-step restatements in conciseness, and it does not split deeper detail into referenced files. Tightening redundancy and externalizing reference material would lift both weaker dimensions.

Suggestions

State the search and validate commands once with their flags, then reference them by name in the mandatory-steps section instead of repeating the full command templates three times.

Move the generic "Think about all the steps..." checklist into a short reference file and link to it, improving both conciseness and progressive disclosure.

Trim redundant restatements of "you must run both scripts in every response" to a single authoritative instruction.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the search/validate command templates and the "mandatory" instructions are restated three times (Required Tool Calls, MANDATORY Search, MANDATORY Validate), which could be tightened.	2 / 3
Actionability	It provides exact executable commands with all required flags and a concrete example query ("customer orders query"), making the guidance copy-paste ready.	3 / 3
Workflow Clarity	The search → write → validate sequence is explicit, with a validation checkpoint and a search/fix/revalidate feedback loop capped at 3 retries, matching the level-3 anchor.	3 / 3
Progressive Disclosure	Referenced scripts (search_docs.mjs, validate.mjs) exist in the bundle, but all instructional content is inline with no signaled one-level-deep reference docs, so navigation is not well structured.	2 / 3
	Total	10 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person and accurately conveys what the API does, but it is essentially a single-sentence capability statement with no usage triggers and only one action verb. It is competent but not optimally specific or trigger-rich.

Suggestions

Add a "Use when..." clause with natural triggers, e.g. "Use when building customer-facing flows for order history, saved addresses, or payment methods with the Shopify Customer Account API."

Replace the single verb "access" with distinct concrete actions (e.g. "query orders, manage addresses, and update payment methods") to raise specificity.

Disambiguate from the Admin API in the description itself (e.g. "for authenticated customers managing their own account") to reduce conflict risk.

Dimension	Reasoning	Score
Specificity	It names the domain ("Customer Account API") and lists concrete objects ("orders, payment methods, and addresses") but uses only one verb ("access"), so it does not list multiple distinct concrete actions like the level-3 anchor.	2 / 3
Completeness	It states what the API does but provides no "Use when..." or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	"Customer Account API", "orders", "payment methods", and "addresses" are relevant domain terms, but phrasing is technical and lacks common natural variations a user would actually say.	2 / 3
Distinctiveness Conflict Risk	"Customer Account API" denotes a reasonably clear niche, but the description could still overlap with generic account-management skills and lacks distinct triggers that prevent misfires.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/shopify/skills/shopify-customer/SKILL.md
Commit: 11c74d6

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.