shopify-polaris-admin-extensions

Add custom actions and blocks from your app at contextually relevant spots throughout the Shopify Admin. Admin UI Extensions also supports scaffolding new adminextensions using Shopify CLI commands.

Quality

67%

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-admin-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 content is highly actionable with a clear, well-validated workflow and concrete copy-paste examples, but it suffers from redundant restatements of the search/validate workflow and a large inline component reference that would benefit from being split out. Tightening duplication and externalizing the prop catalog would improve token efficiency and structure.

Suggestions

De-duplicate the search/validate workflow: keep one authoritative sequenced version (the opening 'Required Tool Calls' list) and reference it from the later sections instead of restating it.

Move the dense s-* component prop catalog (lines 94–144) into a references/ file (e.g. COMPONENTS.md) and keep only a short usage example plus a pointer in SKILL.md.

Trim conceptual explanations of what admin actions/blocks/links are; assume Claude's domain knowledge and keep only Shopify-specific constraints.

Dimension	Reasoning	Score
Conciseness	The body is largely concrete but notably redundant — the search→write→validate workflow is fully laid out in the opening 'Required Tool Calls' section and then repeated near-verbatim in the closing 'MANDATORY: Search/Validate' sections — and includes conceptual padding ('Admin actions are a UI extension that you can use to create transactional workflows...') that could be trimmed by deduplicating the two workflow descriptions.	2 / 3
Actionability	Executable CLI commands ('shopify app generate extension --template admin_action --name my-admin-action'), complete component examples with prop values, import snippets, and fully-flagged search_docs.mjs/validate.mjs invocations are all copy-paste ready.	3 / 3
Workflow Clarity	A clear five-step sequence (search → write → validate → on failure search/fix/re-validate up to 3 retries → return) with explicit validation checkpoints and a feedback loop, satisfying the rubric's recovery-loop requirement.	3 / 3
Progressive Disclosure	The bundled scripts (search_docs.mjs, validate.mjs) are clearly referenced one level deep, but the large inline component-prop catalog (50+ lines of s-* element examples) and the API/component lists are monolithic reference content that would be better split into a references file rather than kept inline.	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 conveys a clear, specific Shopify Admin niche and names a couple of concrete actions, but it omits any explicit 'Use when...' trigger guidance and only partially enumerates capabilities. Adding trigger terms and a use-when clause would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building or scaffolding Shopify Admin UI extensions (admin actions, blocks, links, or print actions).'

Broaden the action list to cover all extension types the skill supports (actions, blocks, links, print actions) rather than only actions and blocks.

Include more natural trigger variations users would say ('Shopify admin extension', 'admin block', 'app embed', 'scaffold extension').

Dimension	Reasoning	Score
Specificity	It names the domain (Shopify Admin UI Extensions) and concrete actions ('Add custom actions and blocks', 'scaffolding new adminextensions using Shopify CLI commands'), but the action set is narrow rather than comprehensive — links and print actions covered in the body are absent here.	2 / 3
Completeness	The 'what' is stated (add actions/blocks, scaffold extensions) but there is no 'Use when...' clause or equivalent explicit trigger guidance for when Claude should invoke the skill, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Relevant keywords appear ('custom actions', 'blocks', 'Shopify Admin', 'scaffolding', 'Shopify CLI') that a developer would say, but common variations and surface terms ('admin extension', 'admin block', 'app embed') are limited compared to the multi-variation anchor for 3.	2 / 3
Distinctiveness Conflict Risk	The description is tightly scoped to Shopify Admin UI Extensions ('custom actions and blocks ... throughout the Shopify Admin'), a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 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-admin-extensions/SKILL.md
Commit: 11c74d6

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