Back to skill
Skillv1.0.3
ClawScan security
Teamwork · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignApr 21, 2026, 1:04 PM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill is internally consistent: it uses the Membrane CLI to connect to Teamwork, asks users to authenticate via Membrane, and does not request unrelated credentials or filesystem access.
- Guidance
- This skill delegates auth and API calls to the Membrane service. Before installing, verify you trust Membrane (https://getmembrane.com) and/or inspect the @membranehq/cli package source on GitHub/npm. Installing the CLI with `npm install -g` requires elevated privileges on some systems—consider installing in a controlled or isolated environment if you have security concerns. Remember that using this skill means Teamwork access and tokens will be managed by Membrane rather than stored locally; review Membrane's privacy/security documentation if that matters for your org.
Review Dimensions
- Purpose & Capability
- okThe name/description (Teamwork integration) match the instructions: install Membrane CLI, create a Teamwork connection, discover and run Teamwork-related actions. Nothing requested is unrelated to interacting with Teamwork via Membrane.
- Instruction Scope
- noteInstructions are narrowly scoped to installing the @membranehq/cli, logging in, creating a connector, listing actions, and running actions. The only broader behavior is that authentication and API calls are mediated by Membrane (a third-party service) — so Teamwork data and auth are routed through Membrane's service rather than purely local calls. The skill does not instruct reading local files or unrelated env vars.
- Install Mechanism
- okNo install spec in the registry; the SKILL.md recommends npm install -g @membranehq/cli which is a standard npm install from the public registry (moderate risk vs no-install). This is an expected install method for a CLI; users should note global npm installs may require elevated privileges and install code from the npm package maintainer.
- Credentials
- okThe skill declares no required env vars or credentials. Authentication is performed interactively through Membrane (browser flow), which is appropriate for a connector-based integration. There are no requests for unrelated secrets or multiple external credentials.
- Persistence & Privilege
- okThe skill does not request always:true and does not modify other skills or global agent settings. It relies on Membrane to manage credentials server-side; the skill itself is instruction-only and does not request persistent elevated privileges.