BD shopify-admin-pro
Guarded Shopify Admin for OpenClaw: everything shopify-audit-pro does, plus acting as the store admin. Safety first: nothing is written without a preview and your explicit confirmation, delete/refund/cancel/publish and other high-risk actions need a second exact confirmation, a failed write is never blindly retried, your token goes only to your own *.myshopify.com store (no relay, no third-party plugin), secrets are never typed in chat, and a PII-free audit log records every call. Then the admin power: audits and reports, plus products, inventory, orders, fulfillment, refunds, discounts, customers, themes and bulk edits via the Admin GraphQL API. Only the scopes you grant are usable.
Guarded Shopify Admin for OpenClaw: everything shopify-audit-pro does, plus acting as the store admin.
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
edit-residuethe text marks something as outdated (lines 64, 69): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 22 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 85Steps. 45 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2635 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 692: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.