Back to skill
Skillv1.0.0
ClawScan security
Bring Add · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousFeb 10, 2026, 3:43 PM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill appears to implement a Bring! shopping-list adder, but its runtime instructions require email/password credentials and npm-installed code while the registry metadata does not declare those credentials or an install step — review the code and dependencies before installing.
- Guidance
- This skill likely needs your Bring! account credentials and npm dependencies to run. Before installing or running it: 1) Inspect index.js, package.json and package-lock.json for network calls, unexpected modules, or code that reads unrelated files or exfiltrates data. 2) Verify the authentication method — prefer tokens over storing plaintext passwords in env vars if possible. 3) Run npm install and the code in an isolated environment (container or VM) if you must test it. 4) Ask the publisher for a homepage or source repo to validate origin; the registry metadata lacking declared env vars is a transparency gap. If you cannot review the code and dependencies, avoid providing account credentials to this skill.
Review Dimensions
- Purpose & Capability
- concernThe SKILL.md and code indicate this interacts with the Bring! API (auth + batch updates), which legitimately requires credentials and Node runtime. However, the registry metadata lists no required environment variables or primary credential despite the README instructing users to export BRING_EMAIL and BRING_PASSWORD. That mismatch is unexpected and reduces transparency.
- Instruction Scope
- concernThe runtime instructions tell the agent/user to provide email/password env vars, run node index.js, pipe stdin, and perform API calls (batchUpdateList). Those steps are consistent with the described purpose, but the instructions reference sensitive credentials that are not declared elsewhere. No other out-of-scope file or system access is requested in SKILL.md.
- Install Mechanism
- concernThere is no formal install spec in the registry, but the SKILL.md instructs running npm install and the package files (package.json, package-lock.json, index.js) are included. The lack of an install specification in metadata means dependency installation will be manual or implicit — you should inspect package.json/package-lock.json and index.js for suspicious dependencies or post-install behavior before running npm install.
- Credentials
- concernSKILL.md requires BRING_EMAIL and BRING_PASSWORD to authenticate to Bring!. Those are sensitive credentials but are reasonable for this functionality — however, the skill metadata does not declare any required env vars or a primary credential, making the request for credentials non-transparent and disproportionate to what the registry advertises.
- Persistence & Privilege
- okNo special privileges are requested in registry flags: always, disableModelInvocation, and other persistence flags are not set. The skill is not declared as always-on or model-invocable by default beyond normal behavior.