CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

59

Quality

74%

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

70%Weight 40%Scale 1-5

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

A highly actionable body with an excellent validate-and-retry workflow, undermined by notable redundancy — the mandatory tool-call workflow is repeated three times — and by large inline reference catalogs (components, targets, APIs) that should live in separate files under references/.

Suggestions

State the search/write/validate/retry workflow once in the numbered 'Required Tool Calls' section and delete the two duplicated 'MANDATORY' sections, keeping only error-recovery details not already covered.

Move the ~90-line component example catalog and the extension target/API lists into references/ files (e.g. references/components.md, references/targets.md) and link to them from the body.

Remove the embedded system-prompt text ('You are an assistant that helps Shopify developers...') and the duplicated privacy notices — consolidate to one — since they consume context without adding actionable guidance.

DimensionReasoningScore

Conciseness

The search-then-validate workflow is stated three separate times ('Required Tool Calls', 'MANDATORY: Search Before Writing Code', 'MANDATORY: Validate Before Returning Code'), an ~90-line component example catalog and ~90-line target list are inlined, and embedded system-prompt filler ('You are an assistant that helps Shopify developers...') pads the file — several unnecessary or duplicated sections.

2 / 5

Actionability

Everything is executable: an exact scaffold command (shopify app generate extension...), exact script invocations with every instrumentation flag explained, complete component examples showing all props, and prescriptive attribute rules with correct/incorrect examples.

5 / 5

Workflow Clarity

The sequence is explicit with validation checkpoints and a genuine feedback loop: search, write, validate (mandatory, --target required), then on failure read the error, search for the type, fix, and re-validate up to 3 retries before returning code.

5 / 5

Progressive Disclosure

Section headers exist and the referenced scripts (scripts/search_docs.mjs, scripts/validate.mjs) are real bundle files invoked directly, but the large component catalog and extension-target/API lists are inline content that belongs in separate reference files, and no references/ files exist to move them to.

3 / 5

Total

15

/

20

Passed

Description

66%Weight 40%Scale 1-5

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 domain-specific description that clearly names the Shopify checkout extension niche with several concrete capability areas and a scaffolding action, hindered mainly by the complete absence of a 'when to use this skill' trigger clause and some missing natural-language variations.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or scaffolding checkout UI extensions, customizing checkout steps (shipping, payment, order summary), or working with Shop Pay.'

Include the natural terms users and docs actually use, such as 'checkout customization', 'checkout UI', and 'shopify.extension.toml', to broaden trigger-term coverage.

State the concrete actions the skill performs (search the docs, write component code, validate against the API version) rather than the generic 'build custom functionality'.

DimensionReasoningScore

Specificity

The description enumerates concrete checkout areas ('product information, shipping, payment, order summary, and Shop Pay') and a concrete action ('scaffolding new checkout extensions using Shopify CLI commands'), but the main verb 'Build custom functionality' stays generic, so it lists several specifics with minor gaps rather than comprehensive coverage.

4 / 5

Completeness

The 'what' is clear and specific, but there is no 'Use when...' clause or any equivalent trigger guidance for when Claude should invoke the skill, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Natural terms users would say are present ('checkout', 'shipping', 'payment', 'Shop Pay', 'Shopify CLI', 'extensions'), but common variations like 'checkout customization', 'checkout UI', or file/manifest terms (shopify.extension.toml) are missing.

4 / 5

Distinctiveness Conflict Risk

'Shop Pay', 'Shopify CLI', 'merchants', and 'checkout flow' carve a clear niche with distinct triggers, but it could overlap with closely related sibling Shopify/Polaris skills, matching the 'mostly distinct; minor overlap risk' anchor rather than full distinctiveness.

4 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/plugins

Path

plugins/shopify/skills/shopify-polaris-checkout-extensions/SKILL.md

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.