PAPI - WhatsApp API
v1.0.0Complete WhatsApp automation API with microservices architecture. Send messages, interactive buttons, lists, carousels, polls, manage instances, groups, catalogs and webhooks. Features Admin Panel (free), Phone Calls, RCS Messaging, SMS, Virtual Numbers (Pro).
⭐ 2· 2k·0 current·0 all-time
byRafa Martins@rafacpti23
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill describes a WhatsApp automation API and all listed endpoints, features and integrations (instances, messages, groups, webhooks, catalog, Chatwoot/Typebot) match that purpose. Minor mismatch: the docs require a Base URL and an API Key but the skill metadata does not declare any required environment variables or a primary credential.
Instruction Scope
SKILL.md provides endpoint descriptions, example requests, webhook and integration configuration. The instructions do not ask the agent to read unrelated system files, environment variables, or to transmit data to unexpected endpoints beyond the documented API and user-provided webhooks.
Install Mechanism
No install specification and no code files are included (instruction-only), so nothing will be written to disk by the skill itself. This minimizes install-time risk.
Credentials
The documentation clearly expects an API Key and Base URL to be configured, and some integration examples require external tokens (e.g., Chatwoot token). However, the skill metadata lists no required env vars or primary credential—this inconsistency means the platform will not prompt for/validate secrets up front even though they are needed in practice.
Persistence & Privilege
The skill does not request persistent/always-on privileges (always: false) and contains no install steps that modify other skills or global agent settings.
Assessment
This skill is basically documentation for a WhatsApp API and appears internally consistent with that purpose. Before installing or using it: 1) Confirm where you will host the 'Base URL' (the API server) and ensure you trust that server (https://papi.api.br is referenced); 2) Plan to provide an API key and any integration tokens (Chatwoot, Typebot) when you configure the skill — note the registry metadata doesn't declare these secrets, so the platform may not automatically request them; 3) If you will accept webhooks, make sure your webhook endpoint is secure and that you understand what events will be posted; 4) Verify compliance with WhatsApp Business policies and data-protection/regulatory requirements for sending messages and storing contact data; 5) If you need higher assurance, request the actual server/source code or a vetted release (signed GitHub release or official vendor package) rather than trusting only these docs.Like a lobster shell, security has layers — review code before you run it.
latestvk97b2r2ybnr8c7dfjhp669x03180r57q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📱 Clawdis