shopify-custom-data

MUST be used first when prompts mention Metafields or Metaobjects. Use Metafields and Metaobjects to model and store custom data for your app. Metafields extend built-in Shopify data types like products or customers, Metaobjects are custom data types that can be used to store bespoke data structures. Metafield and Metaobject definitions provide a schema and configuration for values to follow.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%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 concrete executable examples and a clear create-write-read sequence, but it loses points for emphatic filler, missing validation checkpoints in the write workflow, and a monolithic single-file structure with no progressive disclosure to reference files.

Suggestions

Remove emphatic meta-instructions ("REMEMBER!!!", "VERY CLOSELY and TAKE PRECEDENCE!", "Follow this guidance meticulously and thoroughly") — they add tokens without guidance value.

Add a validation checkpoint after writing values (e.g., re-query the metafield/metaobject to confirm the write persisted) to close the workflow's feedback loop.

Split the per-API GraphQL examples (Admin/Storefront/checkout/Functions) into a reference file and keep SKILL.md as an overview, improving progressive disclosure for a 200-line skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code-plus-terse-rules, but emphatic meta-instructions like "REMEMBER!!! ... VERY CLOSELY and TAKE PRECEDENCE!", "Follow this guidance meticulously and thoroughly", and "NEVER, EVER" are emphasis padding that adds tokens without information, fitting the 'mostly efficient but could be tightened' 2 anchor rather than the 'every token earns its place' 3 anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TOML definitions, GraphQL mutations/queries, and a TSX snippet with specific CLI commands, matching the 'fully executable code/commands' 3 anchor rather than the pseudocode 2 anchor.	3 / 3
Workflow Clarity	The create-definitions → write-values → read-values sequence is explicit ("ALWAYS: First...", "NEXT:", "FINALLY:"), but there are no validation or verification checkpoints (e.g., confirming a write succeeded or a definition deployed), which anchor 3 requires; this lands on the 'sequence present but checkpoints missing' 2 anchor.	2 / 3
Progressive Disclosure	Sections are clearly organized, but the ~200-line skill is monolithically inline with no split into reference files (no bundle files exist), and the only external link is a single docs URL at the end, fitting the 'content that should be separate is inline' 2 anchor rather than the well-signaled multi-reference 3 anchor.	2 / 3
	Total	9 / 12 Passed

Description

100%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, well-triggered, and complete — it clearly states what the skill does and exactly when to invoke it, with strong distinctiveness for the Shopify custom-data niche. Its only minor weakness is mild verbosity in the explanatory sentences, but no description dimension penalizes that.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete domain actions — "model and store custom data", "extend built-in Shopify data types", "store bespoke data structures", and "provide a schema and configuration" — matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers both what ("Use Metafields and Metaobjects to model and store custom data...") and when ("MUST be used first when prompts mention Metafields or Metaobjects"), satisfying the explicit-trigger requirement that caps 2 when the 'when' is only implied.	3 / 3
Trigger Term Quality	Uses the natural terms developers actually say ("Metafields", "Metaobjects", "custom data") with good coverage for this niche; not merely technical jargon, so it clears the 3 anchor rather than the 2 'missing common variations' anchor.	3 / 3
Distinctiveness Conflict Risk	Targets a highly specific Shopify niche (Metafields/Metaobjects) with distinct triggers unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor rather than the generic 2 anchor.	3 / 3
	Total	12 / 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-custom-data/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.