Back to skill
Skillv1.0.2
ClawScan security
Revel Systems · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignApr 2, 2026, 9:06 PM
- Verdict
- Benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- This is an instruction-only Revel Systems integration that consistently directs the agent to use the Membrane CLI for authentication and API calls and does not request unrelated credentials or system access.
- Guidance
- This skill is coherent but relies on installing and trusting the Membrane CLI and your Membrane account. Before installing or using it: (1) verify @membranehq/cli is from a trusted publisher (review the npm package and homepage), (2) perform the npm install in a non-root or isolated environment (container/VM) if you're cautious, (3) review and grant the connector the least privilege needed (limit access to only the Revel resources you want the skill to use), (4) be aware the skill can access sensitive POS data (orders, payments, customer info) via the Membrane proxy, and (5) monitor and revoke connections when no longer needed. If you need higher assurance, ask the publisher for an install spec or a signed release for the CLI before proceeding.
Review Dimensions
- Purpose & Capability
- okName/description and runtime instructions align: the skill's goal is to interact with Revel Systems and all steps use Membrane (a third-party integration/proxy) to authenticate and call Revel's API. Required resources (network, Membrane account, Membrane CLI) are proportionate to that purpose.
- Instruction Scope
- okSKILL.md only instructs installing and using the Membrane CLI (login, connect, list actions, run actions, and proxy requests). It does not direct the agent to read unrelated local files, environment variables, or system config. Note: the proxy capability allows forwarding arbitrary API requests to Revel via Membrane — expected for an integration but means the skill can access sensitive POS data (orders/payments) if granted.
- Install Mechanism
- noteThere is no registry install spec; the docs tell the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal but nontrivial operation (it fetches remote code from the npm registry). This is expected for a CLI-based integration but is a moderate risk compared to an instruction-only skill that requires no installs.
- Credentials
- okThe skill declares no required env vars, credentials, or config paths. Authentication is done through Membrane's interactive login flow (browser-based). There are no unexplained requests for unrelated secrets or system credentials.
- Persistence & Privilege
- okThe skill is not always-enabled and does not request elevated platform privileges. It relies on the Membrane CLI and browser login for auth; autonomous invocation is allowed by default (normal for skills) but not combined with other concerning flags.