CtrlK
BlogDocsLog inGet started
Tessl Logo

shopify-polaris-checkout-extensions

Build custom functionality that merchants can install at defined points in the checkout flow, including product information, shipping, payment, order summary, and Shop Pay. Checkout UI Extensions also supports scaffolding new checkout extensions using Shopify CLI commands.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/shopify/skills/shopify-polaris-checkout-extensions/SKILL.md
SKILL.md
Quality
Evals
Security

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.

Highly actionable with an excellent validated workflow and concrete code, but it is verbose due to repeated search/validate instructions and keeps large reference material inline rather than offloading it to separate files.

Suggestions

Consolidate the three search/validate sections into one canonical workflow block; the "MANDATORY" sections duplicate the top "Required Tool Calls" steps and the --artifact-id/--revision explanation.

Move the full component catalog and extension-target list into reference files (e.g. references/components.md, references/targets.md) and link to them from a concise overview, leaving only the most common components inline.

Delete the lines 25-28 assistant-persona paragraph, which restates the description without adding actionable guidance.

DimensionReasoningScore

Conciseness

Mostly efficient, but the search/validate workflow is restated three times (top "Required Tool Calls", then both "MANDATORY" sections) with the --artifact-id/--revision flags re-explained at lines 17 and 279, and the lines 25-28 intro restates the description — it could be tightened.

2 / 3

Actionability

Fully executable guidance throughout: copy-paste CLI scaffold command, concrete search_docs.mjs/validate.mjs invocations with all flags, a ~90-component catalog with real props, and ✅/❌ attribute-rule examples.

3 / 3

Workflow Clarity

Clear 5-step sequence (search → write → validate → on failure search/fix/revalidate max 3 → return only after passing) with an explicit validate→fix→retry feedback loop, satisfying the score-3 anchor.

3 / 3

Progressive Disclosure

The two scripts are referenced one level deep and clearly signaled, but the ~90-line component catalog (lines 131-222) and ~60-line extension-target list (lines 51-116) are inlined in SKILL.md rather than split into reference files, so structure is present but not optimally separated.

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.

A specific, well-scoped description with strong natural trigger terms and concrete actions, but it omits an explicit "Use when…" clause so it never tells Claude precisely when to invoke the skill.

Suggestions

Append an explicit trigger clause, e.g. "Use when building or scaffolding Shopify checkout UI extensions, or when the user mentions Shop Pay, checkout customization, or shopify.extension.toml targets."

Lead with the core capability (scaffold + build checkout extensions) before enumerating checkout areas to make the primary action unmistakable.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "build custom functionality" installed "at defined points in the checkout flow" and "scaffolding new checkout extensions using Shopify CLI commands" — matching the score-3 anchor of several specific actions.

3 / 3

Completeness

Clearly answers what the skill does, but lacks any "Use when…" trigger clause, so the "when" is only implied — the missing explicit trigger guidance caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Natural terms a Shopify developer would actually say are well covered: "checkout flow", "Shop Pay", "Shopify CLI", "checkout extensions", "shipping", "payment", "order summary".

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to Shopify checkout UI extensions and Shop Pay scaffolding, giving it a clear niche unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.