Back to skill
Skillv1.0.3
ClawScan security
Tastyigniter · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignApr 22, 2026, 1:43 PM
- Verdict
- benign
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill's instructions and requirements are coherent with a TastyIgniter integration via the Membrane CLI, but there are minor inconsistencies and an install-time risk (global npm install) you should consider before proceeding.
- Guidance
- This skill appears to do what it claims: it uses the Membrane CLI to talk to TastyIgniter. Before installing or running it: 1) Confirm @membranehq/cli and getmembrane.com are legitimate and review the CLI's npm page and repository (look at package.json and any postinstall scripts). 2) Prefer running commands with npx or inside a disposable container/VM to avoid globally installing binaries. 3) Don't share other credentials—this skill delegates auth to Membrane via a browser code flow. 4) If you must install globally, inspect the package source first and consider limiting network access or running in a sandbox. 5) If you want higher assurance, ask the publisher for the exact connector implementation or a pinned CLI release URL rather than installing the floating @latest tag.
Review Dimensions
- Purpose & Capability
- noteThe skill name and description match the SKILL.md: it uses Membrane to interact with TastyIgniter. Small inconsistency: the registry metadata lists no required binaries, but the instructions assume npm/node (npm install -g and npx). Requiring the Membrane CLI is reasonable for this integration.
- Instruction Scope
- okRuntime instructions are narrowly scoped to installing and using the Membrane CLI (login, connect, list/create/run actions). They do not instruct reading arbitrary files, asking for unrelated credentials, or sending data to unexpected endpoints. The skill explicitly recommends not asking users for API keys.
- Install Mechanism
- concernThere is no platform install spec, but SKILL.md tells the user to run `npm install -g @membranehq/cli@latest` (and uses npx). Installing an npm package globally or running npx will fetch and execute code from the npm registry and may run package lifecycle scripts. This is a moderate risk and should be done from a trusted source or in a sandboxed environment. Prefer npx or inspect the package before global install.
- Credentials
- okThe skill requests a Membrane account and network access only; it does not ask for unrelated environment variables or secrets. Authentication is delegated to Membrane via browser/OpenID-style flow, which is proportionate for this use.
- Persistence & Privilege
- noteThe skill itself is instruction-only and does not request 'always' or modify other skills. However, following the instructions will install a CLI binary on the system (persistent). Consider this before installing globally — use npx or a container if you want to avoid persistent changes.