EngageLab SMS
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This appears to be a straightforward EngageLab SMS helper, but it can send real SMS messages and change or delete SMS account resources without documented confirmation guardrails.
Install only if you trust the skill and need EngageLab SMS automation. Before using real credentials, verify the code against official EngageLab docs and require the agent to show and confirm recipients, message template/parameters, schedule, and any template/signature changes—especially deletes or bulk/marketing sends.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent could send unintended SMS messages, incur costs, contact customers, or delete/change templates and sender IDs if the user gives credentials and the action is not carefully confirmed.
The skill exposes external SMS sending plus account resource creation/update/deletion. The provided artifacts do not add approval, recipient-count limits, consent/cost checks, or safe dry-run guidance before those high-impact actions.
“Send SMS — Send notification or marketing SMS to one or more recipients” ... “Template Management — Create, read, update, and delete” ... “Signature (Sender ID) Management — Create, read, update, and delete”
Require explicit final confirmation before every send, scheduled send, bulk recipient list, marketing message, update, or delete. Show recipients, template ID/content parameters, schedule time, expected impact, and make destructive actions opt-in.
If these credentials are exposed or reused in an unsafe context, someone could send SMS messages or manage templates/signatures on the user’s EngageLab account.
EngageLab account credentials are required for the integration and are used for Basic Authentication. This is purpose-aligned, but the credentials authorize real account actions.
“The user must provide their dev_key and dev_secret ... Authorization: Basic <base64(dev_key:dev_secret)>”
Use least-privileged EngageLab credentials if available, avoid pasting secrets into shared chats or logs, rotate credentials if exposed, and confirm that credentials are only sent to the EngageLab API endpoint.
Users have less external assurance about who maintains the skill or whether it matches official EngageLab guidance.
The implementation is visible and there is no install script, but the artifact metadata does not provide a public source or homepage for provenance verification.
“Source: unknown” and “Homepage: none”
Review the included code and compare endpoints, parameters, and authentication behavior with official EngageLab documentation before using production credentials.