Msg91
v1.0.2MSG91 integration. Manage data, records, and automate workflows. Use when the user wants to interact with MSG91 data.
⭐ 0· 79·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (MSG91 integration) lines up with the instructions: all actions use Membrane to call MSG91 APIs, discover actions, and run/send requests. There are no unrelated secrets, binaries, or paths requested.
Instruction Scope
The SKILL.md instructs the agent/user to install and run the @membranehq/cli (via npm or npx) and to use membrane commands (login, connect, action list/run, request). These instructions stay within the MSG91 integration scope. One minor note: SKILL.md tells the user to install a global npm CLI even though the skill metadata has no formal install spec — this is expected for an instruction-only skill but worth being aware of.
Install Mechanism
There is no packaged install spec in the registry (instruction-only). The SKILL.md recommends installing the Membrane CLI via npm (or using npx). This is a common, reasonable approach; the instruction points at a named npm package rather than an obscure URL.
Credentials
The skill declares no required env vars or credentials and explicitly advises not to ask users for MSG91 API keys, instead creating a Membrane connection. Requested capabilities are proportional to the stated purpose (requires a Membrane account and network).
Persistence & Privilege
The skill is not forced-always, does not request system-level persistence, and is user-invocable. It does not instruct modifying other skills or global agent configs.
Assessment
This skill is instruction-only and uses the Membrane CLI to interact with MSG91. Before installing or following the instructions: 1) Confirm you trust Membrane (@membranehq) and review the npm package and its repository (ensure package integrity and provenance). 2) Expect to sign in to your Membrane account in a browser (the CLI opens an auth flow); don't paste other secrets into these commands. 3) The skill relies on Membrane to manage MSG91 credentials server-side — verify Membrane's privacy/security policies if you care about who can access message/contact data. 4) Use npx if you prefer not to install a global npm package. 5) Avoid running membrane commands with JSON input that contains unrelated secrets; ensure you only pass intended data to the connector.Like a lobster shell, security has layers — review code before you run it.
latestvk97e6pmw7cvfz5r0cbj5czsrds8426hr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.