Content
46%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |