CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

72%

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

Fix and improve this skill with Tessl

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

Quality

Content

46%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 clean, well-organized index with a useful priority taxonomy, but it functions as a pointer document whose targets are absent: the referenced rules/*.md and AGENTS.md files are missing from the bundle, and the real reference files are never linked. As a result the skill delivers almost no actionable content and its progressive-disclosure structure does not resolve to any readable material.

Suggestions

Ship the referenced detail files (rules/*.md and AGENTS.md) in the bundle, or rewrite SKILL.md to point at the files that actually exist in references/ so the routing resolves.

Link the three orphaned reference files (saleor-key-directories.md, variant-state-machine.md, variant-utils-reference.md) from the relevant Quick Reference entries (e.g. dev-investigation, product-variants) so they are discoverable from the main skill.

Include at least one concrete inline example — e.g. a cache-tag revalidation snippet for data-caching or the codegen command for data-graphql — so the body carries some executable guidance rather than serving purely as an index.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no explanation of what Next.js, Tailwind, or Saleor are. Minor trimmable redundancy: the 'Rule Categories by Priority' table and the 'Quick Reference' section both enumerate the same six categories, and the intro sentence ('Contains 11 rules across 6 categories...') repeats the same map a third time.

4 / 5

Actionability

The body is purely an index: no code, commands, or specific steps — the most concrete instruction is 'Read individual rule files for detailed explanations and code examples'. Worse, those detail files ('rules/data-caching.md', 'rules/product-variants.md') and 'AGENTS.md' do not exist in the bundle, so the promised executable guidance is unreachable. This matches the anchor of high-level hints missing the specific steps to execute; not a 1 because concrete file paths and rule names are given.

2 / 5

Workflow Clarity

A routing sequence is implicitly present (match the task in 'When to Apply' → pick a category by priority → read the rule file), but the flow dead-ends: the rule files it routes to are missing from the bundle, and the three reference files that do exist are never connected to the routing. No multi-step process with validation is described, and none is strictly required for an index skill, but the incomplete routing keeps this at 'steps listed but gaps'.

3 / 5

Progressive Disclosure

Judged against the actual bundle: the body clearly signals references ('rules/data-caching.md', 'AGENTS.md'), but none of the referenced files exist, while the three files that do exist in references/ (saleor-key-directories.md, variant-state-machine.md, variant-utils-reference.md) are orphaned — never linked from SKILL.md, hence buried and undiscoverable. Navigation is broken in both directions, matching the anchor of references being buried/inaccessible; not a 1 because the body itself is well-sectioned and the signals are explicit.

2 / 5

Total

11

/

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: explicit what and when clauses, concrete trigger phrases, a clearly bounded project niche, and an explicit hand-off to the dependency skill for universal patterns. The only minor gap is that capabilities are expressed as topic areas rather than actions, and a few natural synonyms (PDP, revalidation, GraphQL) are omitted.

DimensionReasoningScore

Specificity

The description names the domain ('Project-specific patterns for the Saleor Paper storefront built with Next.js 16, TypeScript, and Tailwind CSS') and enumerates several concrete work areas ('product pages, checkout flow, caching, variant selection, filtering, SEO, or UI components'). It falls short of a 5 because it frames topics rather than listing concrete actions (no verbs like 'extract', 'configure', or 'debug'), and is above 3 because coverage of capability areas is broad, not just 1-2.

4 / 5

Completeness

Both questions are explicitly answered with concrete trigger phrases: what ('Project-specific patterns for the Saleor Paper storefront built with Next.js 16, TypeScript, and Tailwind CSS') and when ('Use when working with product pages, checkout flow, caching, variant selection, filtering, SEO, or UI components'). This matches the anchor-5 good example pattern exactly.

5 / 5

Trigger Term Quality

Phrases like 'checkout flow', 'caching', 'variant selection', 'filtering', 'SEO', and 'product pages' are natural terms a user working on this storefront would say. Not a 5 because common variations the body itself uses — 'PDP', 'revalidation', 'GraphQL', 'codegen' — are absent from the description.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear project-specific niche (the Saleor Paper storefront) and explicitly delimits the boundary against the sibling skill: 'For universal Saleor API patterns, see the saleor-storefront dependency.' Minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.