AD openclaw-shopify-manager
Connect OpenClaw to Shopify with guided setup, local `.env` secret storage, Shopify OAuth, webhook validation, product and content operations, and host or Docker-sidecar deployment support. Use when connecting a Shopify store to OpenClaw, completing Shopify app setup, reading store information, listing or finding products, updating approved Shopify content, or running a small local Shopify connector for OpenClaw.
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securityreferences/security-and-behavior.md:20Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- no background tunneling binary, SOCKS proxy, VPN client, or reverse shell
-
low Dangerous commands
cmd-background-processreferences/systemd.md:36Starts a background / autostarted process (quoted — discussed, not commanded)- `sudo systemctl enable shopify-connector.service`
quoted
Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 657 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 416: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 39 items
- +4Reference files are cited in the instructions (5 of 6)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.