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

90%

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

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.

An exceptionally actionable, well-sequenced operational guide: every command is executable, every failure mode has an explicit handling path, and validation precedes the risky crawl step. The only weaknesses are mild redundancy of security rules across sections and a dense defaults paragraph that could be split into a reference file.

DimensionReasoningScore

Conciseness

The body is dense, purely operational Shopify-specific knowledge (exit codes, signature form validation, precedence rules, expiry behavior) with no explanation of concepts Claude already knows. Not 5 because safety-critical points repeat across sections — the signature-bound-to-one-host rule appears in Hard limits, Step 1, and Security, and robots.txt and git-ignore handling each appear twice — which is trimmable redundancy.

4 / 5

Actionability

Copy-paste ready commands ('"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run shopify_env.py precheck <url>', 'run shopify_crawl.py <url> --out ./crawl'), a complete exit-code decision tree keyed to exact JSON fields ('aborted': 'rate_limited', 'truncated': true, discovery_capped), and every flag enumerated (--resume, --include/--exclude, --sample-per-template, --no-signature, --ignore-robots) cover the common cases.

5 / 5

Workflow Clarity

A clear four-step sequence with validation up front (the precheck validates signature form: web-bot-auth tag, @authority, key id, expiry) and explicit feedback loops for each failure mode — fix the pattern on exit 2, --resume after an aborted crawl, re-run the precheck against the apex/www host. Batch-crawl validation checkpoints are present, so no cap applies.

5 / 5

Progressive Disclosure

The body is well-sectioned (Hard limits, Routing, Steps 1-4, Setup, Security) and defers appropriately: setup detail goes to SHOPIFY-SETUP.md and steps 4+ to the parent seo-audit skill, both clearly signaled and one level deep. Not 5 because no bundle reference files exist and the dense Defaults paragraph (concurrency, delay, cap precedence) is inline detail that could live in a reference file.

4 / 5

Total

18

/

20

Passed

Description

87%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 description that states a concrete, mechanism-specific capability and pairs it with an explicit 'Use when' trigger list mixing natural user phrases with the relevant technical terms. Minor room to improve by adding a few more natural synonyms (e.g. 'Shopify store') and trimming jargon-only triggers.

DimensionReasoningScore

Specificity

Names several concrete actions — '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 the exact mechanism specified. It falls short of 5 because capabilities the skill actually has (precheck/check modes, fallback to plain seo-audit, resumable crawls) are not covered, but it clearly exceeds the 1-2-action level of 3.

4 / 5

Completeness

Explicitly answers both: what ('Uncapped, sitemap-complete crawl ... feeding the standard seo-audit pipeline') and when ('Use when the user says "Shopify audit", "crawl the whole store", ...') with a list of concrete trigger phrases, exactly matching the top anchor.

5 / 5

Trigger Term Quality

Good natural-phrase coverage: 'Shopify audit', 'crawl the whole store', 'rate limited while crawling', plus the '.shopify-env' file reference. Not 5 because 'signature-agent' and 'web-bot-auth' are technical header names rather than phrases users naturally say, and common variations like 'Shopify store' or 'Shopify SEO' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche — Shopify storefront crawling via the merchant's Crawler Access signature with a project-local .shopify-env — with distinct triggers ('Crawler access', 'web-bot-auth', '.shopify-env') that would not fire for unrelated skills, including the parent seo-audit skill it extends.

5 / 5

Total

18

/

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

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.