Content
75%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.
High-quality, dense guidance: a clear create-definitions → write-values → read-values workflow backed by concrete TOML and GraphQL examples, with explicit DO/DON'T guidance for checkout extensions and Functions. Weaknesses are minor — truncated GraphQL mutation bodies, no post-write verification steps, and some capitalized-emphasis padding.
Suggestions
Complete the `metafieldsSet` and `metaobjectUpsert` mutation examples (replace `{ ... }` with minimal valid selection sets) so all code blocks are copy-paste executable.
Trim redundant emphasis lines ("REMEMBER!!!", "NEVER, EVER") — each rule is already stated once in imperative form, so the repetition costs tokens without adding information.
Consider moving the checkout-extension and Shopify Functions sections into a reference file to shorten the main body, and add a brief note on verifying written values (e.g. re-query the metafield after `metafieldsSet`) as a checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and imperative with almost no padding — every section delivers rules or code. Minor token waste comes from the redundant ALL-CAPS emphasis ("REMEMBER!!! ... TAKE PRECEDENCE!", "NEVER, EVER") which restates rules already stated. It is above anchor 3 because there is no conceptual over-explanation, but not a clean 5 due to the repeated emphasis lines. | 4 / 5 |
Actionability | Concrete, near copy-paste-ready TOML and GraphQL blocks cover definitions, writes, and reads, plus checkout-extension and Functions examples. The mutation examples truncate their response bodies with `{ ... }` (metafieldsSet, metaobjectUpsert), so they are not fully executable as-is — matching 'mostly executable with minor gaps' rather than anchor 5. | 4 / 5 |
Workflow Clarity | The three-phase sequence is explicit and unambiguous ("ALWAYS: First, create definitions" → "NEXT: demonstrate writing" → "FINALLY: demonstrate reading"), with decision guidance (TOML for 99.99% of apps, GraphQL exceptions). There are no explicit validation/verification checkpoints after writes, which keeps it below anchor 5, though these operations are not destructive or batch. | 4 / 5 |
Progressive Disclosure | No bundle files exist; the single-file body (~195 lines) is well-organized with clear headers and includes a one-level external docs link and a named cross-skill reference ("shopify-use-shopify-cli"). The checkout-extension and Functions subsections could arguably live in a separate reference file, which is the minor organization gap separating it from anchor 5. | 4 / 5 |
Total | 16 / 20 Passed |