CtrlK
BlogDocsLog inGet started
Tessl Logo

shopify-pos-ui

Build retail point-of-sale applications using Shopify's POS UI components. These components provide a consistent and familiar interface for POS applications. POS UI Extensions also supports scaffolding new POS extensions using Shopify CLI commands. Keywords: POS, Retail, smart grid

59

Quality

67%

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-pos-ui/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.

The body is highly actionable with a clear, validated workflow and real bundle scripts, but it is weakened by repeated tool-call instructions and a large inline target catalog that should be split out for better progressive disclosure.

Suggestions

Deduplicate the search/validate instructions: state the mandatory tool-call workflow once and have the later sections reference it rather than restating the same commands and flags.

Move the 34-target extension catalog into a separate reference file (e.g. references/extension-targets.md) and keep SKILL.md as a concise overview that links to it.

Tighten the scaffolding todo-flow and system-instructions blocks to remove redundant emphasis (e.g. repeated MANDATORY/NEVER phrasing) while preserving the key constraints.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete value, but the search/validate workflow is repeated three times ("Required Tool Calls", "MANDATORY: Search", and "MANDATORY: Validate" sections) and could be tightened, fitting the score-2 anchor.

2 / 3

Actionability

Provides fully executable commands (shopify app init / generate extension), copy-paste import and JSX snippets, and concrete attribute rules with examples, matching the score-3 anchor for executable guidance.

3 / 3

Workflow Clarity

A clear numbered sequence (search → write → validate → fix/re-validate → return) with explicit validation checkpoints and a max-3-retry feedback loop matches the score-3 anchor including error-recovery guidance.

3 / 3

Progressive Disclosure

The referenced scripts are real, one-level-deep, and clearly signaled, but the ~327-line body is monolithic with the full 34-target catalog inlined that could be split into a separate reference, matching score 2.

2 / 3

Total

10

/

12

Passed

Description

57%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 identifies a specific niche and concrete actions with explicit keywords, but lacks a proper "Use when..." trigger clause and has limited keyword coverage, capping completeness and trigger quality at 2.

Suggestions

Add an explicit "Use when..." clause naming the user situations that should invoke this skill (e.g. "Use when building or scaffolding Shopify POS UI extensions").

Expand the keyword list with common natural variations users would say, such as checkout, register, till, or POS tile/modal, to improve trigger coverage.

Strengthen specificity by listing a few more concrete capabilities (e.g. rendering tiles, modals, blocks, menu items) rather than just "build" and "scaffold".

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("Build retail point-of-sale applications", "scaffolding new POS extensions using Shopify CLI commands"), but the action list is not comprehensive, matching the score-2 anchor rather than the multi-action score-3 example.

2 / 3

Completeness

It clearly answers "what" (build POS apps, scaffold extensions) but lacks a "Use when..." clause; per the guideline a missing explicit trigger clause caps completeness at 2 even though the keyword list implies the "when".

2 / 3

Trigger Term Quality

The explicit "Keywords: POS, Retail, smart grid" plus "point-of-sale" gives some natural trigger terms, but coverage is thin and misses common variations like checkout, register, or till, fitting score 2.

2 / 3

Distinctiveness Conflict Risk

The niche is clear and specific — Shopify POS UI Extensions with distinct triggers (POS, Retail, smart grid) — making it unlikely to fire for unrelated skills, matching the score-3 anchor.

3 / 3

Total

9

/

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.