Back to skill
Skillv1.0.3
ClawScan security
Deepl · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousApr 21, 2026, 5:04 PM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill's instructions mostly match a DeepL integration via the Membrane CLI, but there are inconsistencies and privacy/installation implications that you should understand before installing.
- Guidance
- This skill uses the Membrane CLI to access DeepL and asks you to install @membranehq/cli from npm and to log in to Membrane. Before installing: (1) verify you trust Membrane (privacy, data handling, and TLS) since your text and credentials will be routed through their service; (2) ensure you are comfortable running a global npm install and that you have npm permissions; (3) prefer installing/staging in a limited/test environment first; (4) confirm the package name and version on the npm registry and review its publisher and changelog; (5) note the SKILL.md omits declaring required binaries (npm/membrane) in metadata — treat that as a documentation gap and ask the publisher for clarification if needed.
Review Dimensions
- Purpose & Capability
- noteThe SKILL.md describes a DeepL integration implemented via the Membrane CLI and requires a Membrane account and network access — that matches the stated purpose. However, the registry metadata declares no required binaries or credentials while the runtime instructions clearly assume a 'membrane' CLI (installed via npm) and interactive login; that mismatch (missing declared binary requirement) is an incoherence.
- Instruction Scope
- okInstructions are focused on using the Membrane CLI to create a connection and run actions against DeepL. The skill does not instruct reading unrelated local files or environment variables, nor does it ask the agent to exfiltrate data. It does direct the user/agent to authenticate via Membrane (browser or headless flow), which will involve transmitting credentials to Membrane's service.
- Install Mechanism
- concernThere is no formal install spec, but the SKILL.md tells users to run 'npm install -g @membranehq/cli@latest'. That pulls code from the public npm registry (moderate risk). The skill does not declare that it requires 'npm' or the 'membrane' binary in its metadata, creating a provenance/visibility gap. Because installation is manual (instruction-only), the skill itself does not write files, but the required external CLI will.
- Credentials
- noteThe skill requests no local environment variables or API keys (it explicitly advises against asking users for DeepL keys). Instead it delegates auth and credential storage to Membrane's servers. This is proportionate to the described functionality, but it means translation data and credentials will be handled by a third-party service (Membrane), which has privacy and trust implications you should evaluate.
- Persistence & Privilege
- okThe skill is not always-enabled and does not request elevated platform privileges. It is an instruction-only skill and does not modify other skills or system-wide settings. Autonomous invocation is allowed by default, which is normal; there is no extra persistence requested.