CtrlK
BlogDocsLog inGet started
Tessl Logo

shopify-liquid

Liquid is an open-source templating language created by Shopify. It is the backbone of Shopify themes and is used to load dynamic content on storefronts. Keywords: liquid, theme, shopify-theme, liquid-component, liquid-block, liquid-section, liquid-snippet, liquid-schemas, shopify-theme-schemas

56

Quality

62%

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-liquid/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 search-write-validate workflow and rich executable examples. Its main weaknesses are duplicated mandatory-instruction sections and inline reference material plus dangling schema file references.

Suggestions

Merge the top "Required Tool Calls" and bottom "MANDATORY" sections into one canonical workflow to remove the repeated flag and retry instructions.

Move the Liquid reference (delimiters, tags, filters, global objects) into a references/ file and link to it, keeping SKILL.md as an overview.

Either add the missing schemas/ files (section.json, theme_block.json, theme_settings.json, translations.json) or remove the dangling references to them.

DimensionReasoningScore

Conciseness

Most content is dense, useful reference (filter/tag/object lists, executable examples) that earns its tokens, but the search-then-validate workflow and the --artifact-id/--revision flag explanations are repeated in both the top "Required Tool Calls" section and the bottom "MANDATORY" sections, which could be consolidated.

2 / 3

Actionability

Guidance is concrete and copy-paste ready: exact commands (scripts/search_docs.mjs, scripts/validate.mjs with full flag sets) and complete executable Liquid examples for form, render, paginate, liquid, image_tag, and a full schema block.

3 / 3

Workflow Clarity

The sequence is explicit and gated — search before writing, validate before returning, and a defined failure loop (read error, search, fix, re-validate, max 3 retries then return best attempt) — with validation as a hard checkpoint before output.

3 / 3

Progressive Disclosure

Sections are well organized and the two script references resolve, but the large Liquid reference (delimiters, tags, filters, global objects) is inline rather than split into a reference file, and four referenced schema paths (schemas/section.json, theme_block.json, theme_settings.json, translations.json) do not exist in the bundle.

2 / 3

Total

10

/

12

Passed

Description

47%

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 explains what Liquid is rather than what the skill does or when to invoke it, leaving capability and trigger guidance implicit. It is distinctive but underspecified for activation.

Suggestions

Lead with the skill's concrete actions, e.g. "Generate, validate, and search reference for Shopify Liquid theme components (sections, blocks, snippets)."

Add an explicit trigger clause: "Use when building or editing Shopify themes, Liquid templates, or theme schemas."

Drop jargon keywords (liquid-schemas, shopify-theme-schemas) in favor of natural terms users say (shopify, template, storefront).

DimensionReasoningScore

Specificity

The text states what Liquid is ("an open-source templating language", "the backbone of Shopify themes", "used to load dynamic content") but names no concrete actions the skill itself performs (e.g. generate, validate, search) — it describes the language, not the skill's capabilities.

1 / 3

Completeness

It conveys the domain (Liquid / Shopify themes) so the "what" is partially identifiable, but there is no explicit "Use when..." trigger guidance; per the judging guidelines, a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Natural terms like "liquid", "theme", and "shopify-theme" appear, but the keyword list is padded with jargon users would not naturally say ("liquid-schemas", "shopify-theme-schemas", "liquid-component") and omits common variations like "shopify", "template", or "storefront".

2 / 3

Distinctiveness Conflict Risk

The Shopify Liquid theme niche is clearly delimited by both prose and keywords, making it unlikely to trigger for unrelated skills.

3 / 3

Total

8

/

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.