CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shopify-content

Create and manage Shopify pages, blog posts, navigation menus, redirects, and SEO metadata via the Admin API or browser automation. Use whenever the user wants to add a page to a Shopify store, write a Shopify blog post, update the storefront navigation, manage redirects, or tune SEO metadata on a Shopify site.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, well-structured skill body: concrete executable examples for every content type, a clear workflow ending in verification, and appropriate content splitting into a real, well-scoped reference file. The remaining gaps are minor — handling userErrors, per-item validation in the bulk loop, and a couple of trimmable explanation passages.

Suggestions

Add an explicit error-handling checkpoint after each mutation: instruct Claude to check the userErrors array and fix/retry on failure, which would also add the missing feedback loop for the bulk-content workflow.

Replace the bulk-content pseudocode with an executable snippet (or reference a script) that includes per-item verification rather than just sleep-based rate limiting.

Trim the basic HTML-semantics guidance to the one non-obvious rule (avoid inline styles — the theme handles styling) and note that the API version in endpoint URLs should be checked against the store's supported version.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete examples earning their tokens, but the semantic-HTML list ("Use `<h2>` through `<h6>` for headings", "Use `<p>`, `<ul>`, `<ol>` for body text") explains concepts Claude already knows, and the time-sensitive API version ("2025-01") is inlined in curl commands rather than isolated. These are minor instances of over-explanation that could be trimmed.

4 / 5

Actionability

Each content type gets an executable curl or GraphQL example with realistic field values, but the bulk-content section is pseudocode referencing undefined functions ("for page in pages_data: create_page(page)") and the browser-automation steps give no concrete selectors. Mostly executable with minor gaps.

4 / 5

Workflow Clarity

Clear sequence (determine content type → per-type creation steps → Step 3 verify with query-back and URLs for user review), and the verification step means the destructive/batch cap at 3 does not apply. However, every mutation returns userErrors yet the skill never instructs checking or handling them, and the bulk loop has no per-item validation — the explicit feedback loops of a 5 are missing.

4 / 5

Progressive Disclosure

Verified against the actual bundle: the single reference file (references/content-types.md) exists, is one level deep, and its contents match the advertised scope (API endpoints, metaobject patterns, browser-only operations). Bulk API reference tables are properly moved to the reference file while common-case examples stay inline, with clear section headers and a well-signaled Reference Files section.

5 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: concrete capabilities, explicit "Use whenever..." trigger guidance with natural user phrasing, and a clearly bounded Shopify content niche. Every capability in the skill body is surfaced in the description with no vague padding.

DimensionReasoningScore

Specificity

Lists five concrete content types (pages, blog posts, navigation menus, redirects, SEO metadata) plus two concrete methods (Admin API, browser automation) — comprehensive coverage of the skill's capabilities with no gaps.

5 / 5

Completeness

Explicitly answers both questions: the first sentence states what it does ("Create and manage Shopify pages, blog posts, navigation menus, redirects, and SEO metadata via the Admin API or browser automation") and the second gives explicit trigger guidance ("Use whenever the user wants to add a page to a Shopify store, write a Shopify blog post...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered: "add a page to a Shopify store", "write a Shopify blog post", "update the storefront navigation", "manage redirects", with synonyms (store/storefront/site) represented. These are exactly the phrases a user would say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Clear Shopify store-content niche with the platform name embedded in every trigger phrase; minimal risk of firing for the wrong skill since "Shopify" is a distinctive keyword users invoke directly.

5 / 5

Total

20

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jezweb/claude-skills

Path

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