Inmobile
v1.0.2InMobile integration. Manage data, records, and automate workflows. Use when the user wants to interact with InMobile data.
⭐ 0· 118·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill claims to integrate with InMobile and all runtime instructions revolve around installing and using the Membrane CLI to connect to InMobile. There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
The SKILL.md instructs the user/agent to install and run the Membrane CLI, perform login (browser-based), create connections, run actions, and proxy arbitrary API requests through Membrane. It does not instruct reading unrelated local files or environment variables, but the proxy capability can be used to call arbitrary InMobile endpoints (expected for this integration) so users should understand that RPCs sent via the CLI will run against their connected account.
Install Mechanism
This is an instruction-only skill (no install spec), but it tells the user to run a global npm install (npm install -g @membranehq/cli). That is a normal way to obtain the required CLI, but it will install third-party code on the host — verify package provenance and version before installing.
Credentials
The skill does not request any environment variables or secrets from the skill manifest. It requires a Membrane account and will rely on Membrane to handle credentials for InMobile; this is proportionate but requires trusting the Membrane service to manage and proxy credentials correctly.
Persistence & Privilege
The skill does not request always:true or other elevated platform privileges. It is user-invocable and uses the normal default for autonomous invocation; it does not declare persistent config or system-wide changes.
Assessment
This skill is coherent: it simply tells the agent to use the Membrane CLI to access InMobile. Before installing or using it, verify the @membranehq/cli package source and version (global npm installs run code on your machine), confirm you trust the Membrane service (it will proxy and manage credentials for your InMobile account), and review what API calls the agent will make (the CLI supports arbitrary proxied requests). If you want tighter control, install the CLI manually and inspect its behavior, or limit the agent's permissions when first connecting. If anything about Membrane or the requested operations is unclear, ask the skill author for more detail before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97ae3neph37jed43sqg1bmch5842z3g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.