CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shopify

Query Shopify Admin/Storefront GraphQL APIs via curl.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/productivity/shopify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

This is a strong, highly actionable reference: every command is executable, the API-specific gotchas (scopes, GIDs, rate-limit costs, token formats) are genuinely non-obvious, and destructive operations are gated by an explicit safety section. The main structural weakness is that all of it lives in one large SKILL.md with no progressive disclosure into reference files, and a little time-sensitive editorial material sits outside a dedicated section.

Suggestions

Split the per-resource examples (orders, customers, inventory, metafields, webhooks, bulk operations) into references/*.md files, keeping SKILL.md as setup, the base curl pattern, and pitfalls.

Add inline validation checkpoints to the mutation flows (e.g. verify `product.id` is non-null and `userErrors` is empty before running `productVariantsBulkCreate`).

Consolidate date/version-sensitive notes (2026-01 API version, Jan 2026 legacy-app deprecation, frozen REST API) into a single 'Deprecated / time-sensitive' section.

DimensionReasoningScore

Conciseness

The body is dense and operational — scope lists, auth headers, GID formats, rate-limit costs, and pitfalls are non-obvious specifics Claude cannot know — with almost no padding of known concepts. Not 5 because of a few editorial lines ('No SDK, no app framework', 'Pipe through jq for readable output') and time-sensitive details (2026-01 versions, the Jan 2026 legacy-app cutoff) that sit in intro/callout text rather than a dedicated deprecation section.

4 / 5

Actionability

Everything is copy-paste executable: a reusable `shop_gql` curl/jq function, fully formed GraphQL queries with `$variables` JSON, and worked examples for every common case (search, paginate, create, update, inventory adjust/set, metafieldsSet, bulk operations, webhooks). Matches the 'fully executable; copy-paste ready; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced — a numbered prerequisites flow, the 3-step bulk-operation lifecycle with status polling, and pagination with cursor passing — plus explicit validation guidance ('Always check both' `errors` and `userErrors`) and a Safety section requiring confirmation before destructive mutations. Not 5 because validation is stated as a principle rather than an inline validate-fix-retry checkpoint in each flow (e.g. no explicit verify-product-created step before chaining variant creation).

4 / 5

Progressive Disclosure

Sections are clearly organized (API Basics, per-resource sections, Pitfalls, Safety), but this is a single 345-line file with no bundle files at all — the per-resource example library (products, orders, customers, inventory, metafields, webhooks, bulk) is inlined content that clearly belongs in separate reference files. Fits 'some structure but could be better organized; content that should be separate is inline'; not 4 because there is no split at all, and not 2 because the internal structure is strong, not minimal.

3 / 5

Total

16

/

20

Passed

Description

57%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 concise, in third person, and unambiguous about what the skill does, with a distinctive niche trigger ('Shopify'). Its main weaknesses are the missing 'when to use' trigger clause and thin keyword/action coverage relative to the skill's actual breadth (products, orders, customers, inventory, metafields, webhooks).

Suggestions

Add a 'Use when...' clause, e.g. 'Use when working with Shopify stores — products, orders, customers, inventory, metafields, or webhooks.'

List a few more concrete actions beyond querying (create products, adjust inventory, manage orders) to raise specificity and trigger coverage.

Include natural user phrasings/synonyms such as 'my shop', 'store', 'e-commerce' alongside the product name.

DimensionReasoningScore

Specificity

Names the domain ('Shopify Admin/Storefront GraphQL APIs') and one concrete action ('Query ... via curl'), which matches the 'names domain and 1-2 concrete actions' anchor. It is not 4 because only querying is stated — creating, updating, or managing (all covered in the body) are absent; it is above 2 because 'curl' and both API surfaces are concrete, not generic.

3 / 5

Completeness

It clearly answers 'what' ('Query Shopify Admin/Storefront GraphQL APIs via curl') but has no 'Use when...' or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete and specific, and not 4 because 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

'Shopify', 'Admin', 'Storefront', 'GraphQL', and 'curl' are relevant keywords, but common variations users naturally say ('my store', 'products', 'orders', 'inventory', 'e-commerce') are missing — the 'some relevant keywords but missing common variations or synonyms' anchor. Not 4 because keyword coverage stops at the product name plus API jargon.

3 / 5

Distinctiveness Conflict Risk

'Shopify' is a clear niche with distinct triggers — a user mentioning Shopify, store products, or shop orders would unambiguously route here, with minimal overlap risk against general curl/API skills. Fits the 'clear niche with distinct triggers' anchor; no neighboring anchor matches better.

5 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/productivity/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.