CtrlK
BlogDocsLog inGet started
Tessl Logo

shopify

Query Shopify Admin/Storefront GraphQL APIs via curl.

60

Quality

71%

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.

The body is a strong, executable reference: concrete curl examples, clear sequencing for multi-step flows, and explicit safety/validation guidance for destructive operations. The main weakness is progressive disclosure — everything lives in one large file with no external references to offload detail.

Suggestions

Split large reference sections (e.g. Bulk Operations, Webhooks, the full Pitfalls catalog) into one-level-deep reference files (BULK.md, WEBHOOKS.md, PITFALLS.md) and link them from the body to improve progressive disclosure.

Add an explicit validate→fix→retry loop for bulk operations and mutations (e.g. after checking userErrors, retry the failing input) to make error recovery workflows fully explicit.

Trim a few explanatory sentences that restate concepts (e.g. what the leaky-bucket rate limit is) since Claude already knows the general model.

DimensionReasoningScore

Conciseness

Dense and efficient, surfacing non-obvious facts (auth header format, rate-limit cost model, GID rules) that earn their tokens; a few explanatory sentences could be trimmed but padding is minimal.

4 / 5

Actionability

Fully executable copy-paste curl snippets built on a reusable shop_gql function, covering the common cases (products, orders, customers, inventory, metafields, bulk, webhooks) with real arguments.

5 / 5

Workflow Clarity

Multi-step flows like Bulk Operations (start → poll → download) and Prerequisites are clearly sequenced with checkpoints, and the Safety section mandates confirmation before destructive mutations; minor validate→fix→retry loop detail is implicit rather than explicit.

4 / 5

Progressive Disclosure

Well-organized with clear section headers, but the ~345-line body inlines substantial reference-style content (bulk operations, webhooks, full pitfall catalog) with no bundle files or one-level-deep references to split it out.

3 / 5

Total

16

/

20

Passed

Description

65%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 specific and distinct but concise to a fault: it states what the skill does without any explicit 'when to use it' guidance. Adding a 'Use when...' clause and a couple of concrete capability examples would lift the completeness and specificity scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with Shopify stores, managing products/orders/inventory, or pulling customer and metafield data via the GraphQL APIs.'

Expand the 'what' with 2-3 concrete actions (e.g. 'list products, manage inventory, pull orders, update customers') to lift specificity from a single action to comprehensive coverage.

Include common user-facing synonyms ('Shopify store', 'e-commerce', 'products', 'orders') to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Shopify Admin/Storefront GraphQL APIs) and one concrete mechanism (curl), but does not enumerate multiple specific actions like listing products or pulling orders.

3 / 5

Completeness

The 'what' is clear (Query Shopify GraphQL APIs via curl) but there is no explicit 'Use when...' clause, capping completeness at 3 per the missing-trigger guidance.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('Shopify', 'GraphQL', 'Admin/Storefront APIs', 'curl') but omits common variations like 'products', 'orders', or 'e-commerce'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Shopify GraphQL via curl) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

15

/

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.

Validation13 / 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
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.