saleor-paper-storefront

Project-specific patterns for the Saleor Paper storefront built with Next.js 16, TypeScript, and Tailwind CSS. Use when working with product pages, checkout flow, caching, variant selection, filtering, SEO, or UI components. For universal Saleor API patterns, see the saleor-storefront dependency.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/saleor-paper-storefront/SKILL.md

Quality

Content

58%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 is a concise, well-organized overview/index, but it provides no actionable guidance and its progressive disclosure is broken: it points to non-existent rule files and AGENTS.md while ignoring the reference files that actually ship with the skill.

Suggestions

Replace the broken references to rules/*.md and AGENTS.md with links to the actual bundle files in references/ (saleor-key-directories.md, variant-state-machine.md, variant-utils-reference.md), or add the missing rule files so the paths resolve.

Add at least one concrete, actionable example or command per category (or inline a representative pattern) so the body instructs rather than merely indexing.

Wire the references/ files into the Quick Reference so the variant state machine, key-directories, and utils reference materials are discoverable from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview (priority table, quick-reference index, navigation) with no padded explanations of concepts Claude already knows; only the "How to Use" section restates obvious file-purpose structure and could be trimmed, fitting anchor 4.	4 / 5
Actionability	The body offers no executable code or commands and only navigates the reader to read other files ("Read individual rule files for detailed explanations and code examples"), giving high-level hints without the specific steps to actually do anything — matching anchor 2.	2 / 5
Workflow Clarity	As a single-purpose overview/index skill with no destructive or batch operations, the "When to Apply" trigger list plus the priority-ranked category table make its purpose and discovery path unambiguous, meeting the simple-skill exception for a 5.	5 / 5
Progressive Disclosure	Scored against the actual bundle: the body references rules/data-caching.md, rules/product-variants.md, and AGENTS.md, none of which exist, while the real references/ files (saleor-key-directories.md, variant-state-machine.md, variant-utils-reference.md) are never referenced — references are broken/orphaned and content is misplaced, fitting anchor 2.	2 / 5
	Total	13 / 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.

The description is well-scoped, third-person, and answers both what the skill covers and when to use it with concrete trigger terms. Its only shortcoming is that the "what" lists capability domains rather than fully concrete enumerated actions.

Dimension	Reasoning	Score
Specificity	Names the domain (Saleor Paper storefront) plus several concrete capability areas — "checkout flow, caching, variant selection, filtering, SEO, or UI components" — matching anchor 4's several-specific-actions profile, though not the fully enumerated concrete actions of a 5.	4 / 5
Completeness	Both "what" (project-specific storefront patterns) and "when" ("Use when working with product pages, checkout flow...") are present and explicit, but the "what" is somewhat generic ("patterns") rather than a concrete action list, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	"product pages, checkout flow, caching, variant selection, filtering, SEO, UI components" are natural terms a user would say, giving good keyword coverage; it falls short of 5 only because it lacks synonyms and file extensions.	4 / 5
Distinctiveness Conflict Risk	Scoped to a single named project (Saleor Paper storefront) and explicitly routes universal API patterns to the saleor-storefront dependency, giving it a clear niche with minimal conflict risk as in anchor 5.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: adamsardo/nextjs-saleor-commerce
Path: skills/saleor-paper-storefront/SKILL.md
Commit: 7ab58fd

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.