Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Orbit
v1.0.2Orbit integration. Manage Organizations. Use when the user wants to interact with Orbit data.
⭐ 0· 66·1 current·1 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (Orbit integration) match the instructions: the SKILL.md shows how to manage Orbit via Membrane. Nothing requested is obviously unrelated to interacting with Orbit.
Instruction Scope
Instructions are focused on using the Membrane CLI to discover connections, run actions, and proxy requests to Orbit. They reference writing credentials to ~/.membrane/credentials.json and instruct use of browser-based auth/CLI flows; they do not request other unrelated files or environment variables. Note: the agent is instructed to run external CLI commands (npx) which will execute code fetched at runtime.
Install Mechanism
There is no static install spec, but SKILL.md relies on npx @membranehq/cli@latest. npx dynamically fetches and runs code from the npm registry on demand — a supply-chain/runtime-execution risk. While using an official npm package is expected for this purpose, pinning to a specific version or vetting the package would be safer than @latest.
Credentials
No environment variables or unrelated credentials are requested. The need for a Membrane account and local credentials is proportional to the stated purpose. Small inconsistency: the skill says Membrane 'handles authentication server-side' yet also documents a local ~/.membrane/credentials.json used by the CLI — this is expected for CLI sessions but worth noting.
Persistence & Privilege
The skill is not always-enabled and is user-invocable. Autonomous model invocation is allowed (platform default). Combined with instructions to run npx (remote code execution), autonomous invocation increases risk because an agent could run the CLI without additional explicit user approval.
What to consider before installing
This skill is coherent for an Orbit integration, but before installing: (1) confirm you trust the Membrane provider and the @membranehq/cli npm package (inspect its code or vendor/publisher identity), (2) prefer pinning to a specific CLI version rather than @latest to reduce supply-chain risk, (3) be aware the CLI stores credentials in ~/.membrane/credentials.json — check and control that file and its permissions, and (4) if you allow autonomous invocation, realize the agent could run npx commands on its own; restrict or review that behavior if you need stronger safeguards. If unsure, test the flow in an isolated environment (container or VM) first.Like a lobster shell, security has layers — review code before you run it.
latestvk97cq77yzqng9bps7h9bhkphrn843yrr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.