Back to skill
Skillv1.0.1
ClawScan security
Shopify Theme Pro · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
ReviewMar 13, 2026, 4:40 PM
- Verdict
- Review
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's instructions are a plausible, thorough Shopify theme workflow, but the package metadata omits several expected requirements (binaries and environment variables) — an incoherence that merits caution before installing or running it.
- Guidance
- This skill appears to be a legitimate, detailed Shopify theme workflow, but its manifest is incomplete. Before installing or invoking it: 1) Confirm your environment has the required CLI tools (shopify CLI, npm, git, curl, grep, lsof, dotenv) — the skill will run shell commands that depend on them. 2) Expect it to read local files (.env.local, package.json, theme files). In particular it references SHOPIFY_CLI_THEME_TOKEN and CI secrets (DEV_THEME_ID, etc.); these are needed for pushing themes. If you install, supply tokens only to a secure secret store (not plaintext) and avoid giving access to a live/store token unless you intend to deploy to production. 3) Test first against a development theme and verify the skill prompts for explicit confirmation before --allow-live pushes. 4) Ask the publisher to update the skill metadata to declare required binaries and environment variables (SHOPIFY_CLI_THEME_TOKEN, required theme IDs) so you can review permissions ahead of time. 5) If you are concerned about autonomous runs, restrict invocation or require explicit user confirmation before permitting any network or file-accessing commands.
Review Dimensions
- Purpose & Capability
- concernThe SKILL.md content matches the advertised purpose (theme development, Liquid, deployment). However the metadata declares no required binaries or environment variables, while the instructions clearly assume CLI tools and secrets (shopify CLI, npm, git, curl, dotenv, lsof, grep and a SHOPIFY_CLI_THEME_TOKEN / theme IDs). This mismatch means the manifest understates what the skill actually needs.
- Instruction Scope
- noteInstructions are focused on Shopify theme development and deployment (pre-flight checks, artifact scans, push, post-verify). They explicitly tell the agent to read local files (package.json, .env.local, config/settings_data.json), run shell commands (shopify, npm, grep, lsof, curl, git) and to confirm before pushing live. All of these are coherent with deployment, but they involve accessing local files that can contain credentials and merchant data.
- Install Mechanism
- noteThis is instruction-only (no install spec, no code files to execute). That's lower risk for disk persistence. Still, the skill expects external tooling (shopify CLI, npm, dotenv) that the agent/environment must provide — despite metadata claiming none. The lack of an install spec is reasonable but the manifest should have declared the external tooling requirements.
- Credentials
- concernThe skill's metadata lists no required env vars, yet the instructions explicitly reference and require secrets: SHOPIFY_CLI_THEME_TOKEN (and CI/GitHub secrets like DEV_THEME_ID), and reading .env.local. Requesting and using those tokens is proportionate for a deployment skill — but they should be declared. The omission is an incoherence that could hide surprising secret access if the agent runs commands that read local env files.
- Persistence & Privilege
- okThe skill is not always-enabled and does not request elevated persistence. It's user-invocable and allows normal autonomous invocation, which is the platform default. There is no install-time modification of other skills or system-wide settings in the provided docs.
