ClawHub

Burst Sms

v1.0.2

Burst SMS integration. Manage data, records, and automate workflows. Use when the user wants to interact with Burst SMS data.

⭐ 0· 89·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
The skill delegates all Burst SMS interaction to the Membrane CLI/service, which aligns with the stated purpose. Minor mismatch: metadata lists no required binaries, but the SKILL.md explicitly instructs installing the Membrane CLI (via npm). This is not a security error but is an operational detail the user should be aware of.
✓
Instruction Scope
Runtime instructions are limited to installing and using the Membrane CLI, creating connections, listing actions, running actions, and optionally proxying raw API requests through Membrane. The instructions do not ask the agent to read local files or unrelated environment variables, nor to exfiltrate data to unexpected endpoints beyond Membrane and Burst SMS.
ℹ
Install Mechanism
There is no platform install spec (instruction-only). The SKILL.md recommends `npm install -g @membranehq/cli`. Installing global npm packages is common but gives the package code rights to run on the system during install — verify the @membranehq/cli package and source before installing.
✓
Credentials
The skill requests no environment variables or credentials and explicitly instructs to use Membrane-managed connections rather than asking for API keys. This is proportionate to the stated design (delegated auth via Membrane).
✓
Persistence & Privilege
The skill does not request always:true or any elevated platform persistence, and it doesn't instruct modification of other skills or system-wide settings. Autonomous invocation remains enabled by default (normal).
Assessment
This skill appears to be what it says: a Membrane-driven Burst SMS integration. Before installing or using it, confirm you trust the Membrane project and the npm package @membranehq/cli (review the package page, maintainers, and the GitHub repository). Be aware you will need network access and a Membrane account; the CLI will open a browser for authentication and Membrane will proxy API calls (so message/contact data will flow via Membrane/Burst SMS). If you prefer not to install global npm packages on your host, consider running the CLI in a container or isolated environment. Finally, review your organization’s data-sharing policy before connecting production accounts.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bn5vbq8sqmjbcdyqkhpk0798426zh

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments