shopify-polaris-customer-account-extensions

Build custom functionality that merchants can install at defined points on the Order index, Order status, and Profile pages in customer accounts. Customer Account UI Extensions also supports scaffolding new customer account extensions using Shopify CLI commands.

Quality

80%

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-polaris-customer-account-extensions/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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 clear, well-validated workflow and real referenced scripts, but it loses conciseness through redundant mandatory sections and an oversized inline component catalog that belongs in a separate reference file.

Suggestions

Move the large component catalog (the s-* tag list) into a references/ file and link to it from SKILL.md, keeping only a short usage example inline.

Consolidate the duplicate validation/search flag explanations so the --target/--artifact-id/--revision details appear once rather than in both the Required Tool Calls steps and the MANDATORY sections.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the "MANDATORY: Validate" and "MANDATORY: Search" sections re-explain the --target/--artifact-id/--revision flags already given in the Required Tool Calls steps, and a ~200-line inline component catalog pads the file.	2 / 3
Actionability	Provides copy-paste-ready commands (search_docs.mjs, validate.mjs with full flag set), executable import snippets, the scaffold CLI command, and explicit ✅/❌ web-component attribute rules — fully actionable guidance.	3 / 3
Workflow Clarity	A clear numbered 1–5 sequence mandates search → write → validate → (retry) → return, with an explicit validation checkpoint and a 3-retry error-recovery feedback loop (read error, search correct values, fix, re-validate).	3 / 3
Progressive Disclosure	The referenced scripts/ files (search_docs.mjs, validate.mjs) exist and are cleanly signaled, but the ~200-line component API reference is dumped inline in SKILL.md rather than split into a separate reference file the body points to.	2 / 3
	Total	10 / 12 Passed

Description

82%Weight 40%Scale 1-3

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 specific and distinct, naming concrete install points and scaffolding via Shopify CLI with natural trigger terms. Its main weakness is the absence of an explicit "Use when…" trigger clause, leaving the "when to use" guidance only implied.

Suggestions

Add an explicit 'Use when...' clause naming trigger scenarios, e.g. 'Use when building customer account UI extensions for Order index, Order status, or Profile pages, or when scaffolding a new customer account extension with Shopify CLI.'

Include common natural variants like 'Polaris' or 'UI Framework' that developers may say when referring to these extensions.

Dimension	Reasoning	Score
Specificity	Names concrete actions — "install at defined points on the Order index, Order status, and Profile pages" and "scaffolding new customer account extensions using Shopify CLI commands" — listing multiple specific capabilities rather than abstract language.	3 / 3
Completeness	Clearly answers "what does this do" but has no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Uses natural developer-facing terms a user would say — "customer account", "Order index", "Order status", "Profile pages", "Shopify CLI", "extensions" — giving good coverage of likely trigger phrasing.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche — Shopify customer-account UI extensions on specifically named account pages — making it unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 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-polaris-customer-account-extensions/SKILL.md
Commit: 11c74d6

Reviewed: 17 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.