CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shopify-hydrogen

Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, Dynamic Content with Metaobjects, Express Server, Google Tag Manager Integration, Infinite Scroll, Legacy Customer Account Flow, Markets, Partytown + Google Tag Manager, Subscriptions, Third-party API Queries and Caching. MANDATORY: Use this API for ANY Hydrogen storefront question - do NOT use Storefront GraphQL when 'Hydrogen' is mentioned.

52

Quality

65%

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

Quality

Content

37%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.

The body contains a genuinely good validated workflow (mandatory search → generate → validate → bounded retry loop), but it is buried in a monolithic 3,200-line TypeScript declaration dump that includes unrelated type-fest internals. The skill reads as a raw API index pasted into SKILL.md rather than a curated guide, destroying token efficiency and offering no progressive disclosure.

Suggestions

Move the entire TypeScript declaration dump out of SKILL.md into a references/ file (e.g. references/hydrogen-types.d.ts) and keep only the export surface or a few key component/type examples inline, since Claude can consult the full file on demand.

Delete the non-Hydrogen type-fest internals (UnionToIntersection, IsNever, IsAny, Simplify, OmitIndexSignature, Merge, Except, etc.) — they are generic third-party library documentation with no bearing on the skill's purpose.

Consolidate the duplicated workflow instructions (the top 'Required Tool Calls' section and the bottom 'MANDATORY: Search/Validate' sections) into one authoritative sequence, and add one complete, executable Hydrogen code example so the placeholders (YOUR_MODEL_NAME, YOUR_ARTIFACT_ID) are shown filled in.

DimensionReasoningScore

Conciseness

Roughly 3,200 of the ~3,450 body lines are a verbatim inlined .d.ts dump, including long stretches of type-fest internals ("UnionToIntersection", "KeysOfIteratorOf"-style IsNever/IsAny/Simplify/OmitIndexSignature definitions) that are generic TypeScript library documentation unrelated to Hydrogen. This is the severely padded extreme — massive token cost for content Claude either knows or would never need.

1 / 5

Actionability

The workflow commands are concrete ("scripts/search_docs.mjs \"<component tag name>\"", "scripts/validate.mjs --code '...' --model YOUR_MODEL_NAME --artifact-id YOUR_ARTIFACT_ID --revision REVISION_NUMBER") and both scripts exist in the bundle, but they contain unfilled placeholders with only prose guidance on filling them. There is no complete, copy-paste-ready Hydrogen code example anywhere in the body — guidance is type reference rather than instruction.

3 / 5

Workflow Clarity

The core loop is explicit and well-sequenced with a real feedback loop: search docs → write code → validate → on failure search the error type, fix, re-validate (max 3 retries) → "Return code only after validation passes". It is not a 5 because the same instructions are duplicated in two places (top "Required Tool Calls" and bottom "MANDATORY" sections with slightly different flag lists) and buried in a 3,000-line type wall, making the actual sequence hard to navigate.

4 / 5

Progressive Disclosure

The entire API type dump is inlined directly in SKILL.md instead of being a references/ file — content that clearly belongs in a separate file sits inline, matching the 2 anchor. The bundled scripts are real and properly referenced (no nesting issue), and there is no references/ directory at all, which prevents a 1 but offers no progressive structure.

2 / 5

Total

10

/

20

Passed

Description

78%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 strong, distinct description with an explicit trigger clause and a concrete recipe inventory. Its main weakness is that the capability statement ('cookbooks') describes the resource rather than the actions the agent performs, leaving the 'what' slightly under-specified relative to the very explicit 'when'.

DimensionReasoningScore

Specificity

"Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, … Third-party API Queries and Caching" names the domain and lists many specific concrete recipe topics with minor coverage gaps. It stays at 4 rather than 5 because the action itself is thin — it says the skill offers 'cookbooks/recipes' rather than stating concrete actions like 'implement cart logic' or 'build B2B flows'.

4 / 5

Completeness

Both halves are present: the 'what' ("Hydrogen storefront implementation cookbooks" with an enumerated recipe list) and an explicit 'when' ("MANDATORY: Use this API for ANY Hydrogen storefront question - do NOT use Storefront GraphQL when 'Hydrogen' is mentioned"). Not a 5 because the 'what' is implicit about what the agent actually does with those recipes, fitting the 4 anchor ('when' explicit, 'what' could be more explicit) better than the 5 anchor.

4 / 5

Trigger Term Quality

"Hydrogen storefront", "ANY Hydrogen storefront question", "when 'Hydrogen' is mentioned", plus recipe names ("Bundles", "Infinite Scroll", "Google Tag Manager Integration", "Markets", "Subscriptions") give good natural keyword coverage. A few natural variations users might say (e.g. "Shopify headless", "Storefront API cart", "metafields") are missing, which keeps it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"Hydrogen" (Shopify's headless storefront framework) is a clear niche with distinct triggers, and the description even disambiguates against the neighboring Storefront GraphQL skill ("do NOT use Storefront GraphQL"). Minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (3458 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 4 missing, 4 deeper-than-1-level, 24 suspicious

Warning

Total

14

/

16

Passed

Repository

openai/plugins

Path

plugins/shopify/skills/shopify-hydrogen/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.