Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
WhatsApp OpenAPI Skill
v1.0.0Operate WhatsApp Business Platform Cloud API through UXC with a curated OpenAPI schema, bearer-token auth, and message/profile guardrails.
⭐ 0· 127·1 current·1 all-time
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, OpenAPI schema, and runtime instructions all align with operating the WhatsApp Business Platform Cloud API via the 'uxc' wrapper. However, the registry metadata claims no required environment variables or primary credential while the SKILL.md explicitly instructs binding a bearer token via WHATSAPP_CLOUD_ACCESS_TOKEN — a direct mismatch between declared requirements and actual instructions.
Instruction Scope
The SKILL.md stays on-purpose: it instructs linking a schema-backed CLI, how to set bearer auth, and which Graph API endpoints to call. It explicitly warns to require user confirmation for message sends and avoids hosting webhooks or managing media uploads. It does require network access to graph.facebook.com and to fetch a curated schema from raw.githubusercontent.com, which is expected for this wrapper but worth noting.
Install Mechanism
This is an instruction-only skill with no install spec, so it does not write arbitrary code to disk or download executables at install time. The included validate.sh is a local check script that requires common tools (rg, jq) but is only for validation.
Credentials
The runtime docs require a bearer access token (WHATSAPP_CLOUD_ACCESS_TOKEN) and phone/waba identifiers, but the skill metadata lists no required env vars or primary credential. Requesting a single WhatsApp bearer token for this functionality is proportionate — the problem is the metadata omission that could hide necessary secret access from reviewers. Also the SKILL.md suggests binding a token with uxc which will grant the skill bearer-token access to graph.facebook.com paths.
Persistence & Privilege
The skill is not marked 'always' and does not request persistent elevated privileges. It does not modify other skills or system-wide settings beyond recommending a uxc auth binding (which is scoped to the Graph API host/path). Autonomous invocation is allowed by default but not excessive here.
What to consider before installing
This skill appears to do what it says (wrap the WhatsApp Cloud API via uxc), but there are a few things to check before installing: 1) The SKILL.md expects you to configure a bearer token in WHATSAPP_CLOUD_ACCESS_TOKEN, but the registry metadata does not declare any required environment variables — confirm you will provide only a least-privilege token and that the omission was accidental. 2) The skill fetches a curated OpenAPI schema from raw.githubusercontent.com and makes requests to graph.facebook.com — if you need to audit network interactions or pin the schema, download and review the JSON locally before use. 3) Ensure the token you provide has limited scope and rotation policies (avoid using long-lived/full-admin tokens). 4) The skill instructs explicit confirmation before sends — verify your agent or human workflow enforces that to avoid accidental outbound messages. If the owner or source is unknown, prefer to review the schema and the validate.sh locally and to test with a non-production token/account first.Like a lobster shell, security has layers — review code before you run it.
latestvk979tes1ngmg3wknsx1c2ss2d9832s5z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.