CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-shopify

Uncapped, sitemap-complete crawl of a Shopify storefront using the merchant's Crawler Access signature from a project-local .shopify-env, feeding the standard seo-audit pipeline. Use when the user says 'Shopify audit', 'crawl the whole store', 'Crawler access', 'signature-agent', 'web-bot-auth', 'rate limited while crawling', or audits a host listed in .shopify-env.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is seo-shopify in AgriciDaniel/claude-seo

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly operational, well-sequenced skill body: exact commands, exhaustive exit-code handling, explicit fallback and resume paths, and a strong security section for an untrusted-data crawl. The main costs are repetition of the signature host-binding rule across sections and a single setup reference that is signaled as a bare path rather than a proper link.

Suggestions

State the one-signature-per-host binding rule once (e.g., in 'Hard limits') and cross-reference it from Step 1, exit code 1, and Security instead of restating the full rationale in each place.

Convert the SHOPIFY-SETUP.md pointer into a clearly signaled link (e.g., 'See [SHOPIFY-SETUP.md](extensions/shopify/docs/SHOPIFY-SETUP.md)') so the one-level-deep reference is unambiguous.

Consider moving the exhaustive flag and defaults documentation (concurrency/delay clamps, sitemap walk bounds, precedence rules) into a short reference file, keeping only the flags needed for common crawl decisions inline.

DimensionReasoningScore

Conciseness

Nearly every line is operational Shopify-specific detail Claude cannot infer (web-bot-auth signature fields, exit-code semantics, clamped defaults), but the one-host signature-binding rule is restated at least four times ('Hard limits', the Step 1 fallback note, exit code 1, and Security) and the Security section overlaps itself on signature handling. This fits anchor 4 (efficient with minor over-explanation that could be trimmed) better than anchor 5, where every token would earn its place.

4 / 5

Actionability

The guidance is fully executable: exact invocations ('"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run shopify_env.py precheck <url>', 'shopify_crawl.py <url> --out ./crawl'), enumerated exit codes with prescribed responses, named fallback reasons, and precise flags and defaults. This matches anchor 5 — copy-paste-ready commands covering the common cases including the signed/unsigned and fallback branches.

5 / 5

Workflow Clarity

The four steps are clearly sequenced (precheck mode decision → crawl → audit on artifacts → score/report) with explicit validation checkpoints: the precheck branches on mode, every crawl exit code has a prescribed recovery action (resume with --resume, fall back to seo-audit, fix the regex pattern), and rate-limit handling distinguishes finished-with-warning from aborted. This is anchor 5 — feedback loops and error-recovery paths are present throughout the batch crawl workflow.

5 / 5

Progressive Disclosure

Good structure with well-labeled sections, a routing table, and a clearly purposed one-level-deep reference ('See extensions/shopify/docs/SHOPIFY-SETUP.md') for setup and env-format details, keeping them out of the main body. It falls short of anchor 5 because the reference is a bare path rather than a clearly signaled link, and the dense flag/defaults documentation could arguably live in a reference file; the bundle itself contains no additional files to verify organization against.

4 / 5

Total

18

/

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.

A model description: concrete third-person capability statement, an explicit 'Use when…' clause with quoted natural and technical triggers, and a clearly bounded Shopify niche that distinguishes it from the parent seo-audit skill. No vague language or over-claims are present.

DimensionReasoningScore

Specificity

Multiple concrete, specific actions are named — 'Uncapped, sitemap-complete crawl of a Shopify storefront', 'using the merchant's Crawler Access signature from a project-local .shopify-env', 'feeding the standard seo-audit pipeline' — with comprehensive coverage and no vague filler. This matches the anchor for multiple specific concrete actions; it is above anchor 4 because nothing in the capability list is generic or missing.

5 / 5

Completeness

It explicitly answers both questions: the 'what' is the uncapped signed crawl feeding the seo-audit pipeline, and the 'when' is an explicit 'Use when the user says…' clause with concrete quoted trigger phrases. This is exactly the anchor-5 good example pattern; a missing or weak 'when' clause (which would cap at 3) is not the case here.

5 / 5

Trigger Term Quality

The trigger list covers natural user phrasings and their synonyms: 'Shopify audit', 'crawl the whole store', 'Crawler access', 'rate limited while crawling', plus the technical terms ('signature-agent', 'web-bot-auth', '.shopify-env') a user with this setup would actually say. Below anchor 5 would require missing common variations, and none are apparent.

5 / 5

Distinctiveness Conflict Risk

The niche is unmistakable — Shopify storefronts the user administers, with Crawler Access signatures and a .shopify-env file — and triggers like 'Shopify audit' and 'Crawler access' are distinct from a generic seo-audit skill's triggers. Overlap risk with sibling seo skills is minimal because the description explicitly scopes to Shopify.

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

AgriciDaniel/claude-seo

Path

extensions/shopify/skills/seo-shopify/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.