$ ~/registry/skill/composiohq-composio-skills-wati-automation

SKILL

wati-automation

Name: wati-automation
Author: Composio

Automate Wati messaging and customer communication tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is essentially operational guidance for using Rube MCP and does not itself declare local execution, environment variables, or direct endpoint configuration, so overall risk is low. The main caveat is that it depends on external Rube/Composio and a Wati account connection, so actual data egress and authorization boundaries depend on those external services.

CredentialsCaution

The material says “No API keys needed,” but it explicitly requires an active `wati` connection via `RUBE_MANAGE_CONNECTIONS` and completion of an auth link, which still implies external account authorization/session credentials. The credential risk mainly sits in the Rube/Composio-to-Wati integration rather than this skill directly collecting env vars.

Network egressCaution

The README explicitly requires connecting to `https://rube.app/mcp` and using Composio’s Wati toolkit, which means business requests and data will be transmitted through external MCP/integration services for the stated purpose. No unrelated or hidden exfiltration endpoint is shown, but third-party data transit should be noted.

Code executionLow risk

The system marks this as `prompt-only`, and the material does not describe spawning local processes, running scripts, or invoking OS capabilities. Its behavior is more like guiding the use of existing MCP tools than executing code on the local machine.

Data accessCaution

There is no stated direct access to the local filesystem, clipboard, or system resources, but the skill is intended to “Automate Wati operations” and may act on connected Wati resources via discovered tools. Its data access scope is therefore mainly external Wati account data and objects rather than local data.

Supply chainLow risk

The source is an open-source GitHub repository with strong community trust (64.7k stars per the system). Combined with its `prompt-only` nature, this gives it reasonably good auditability. The unspecified license and unknown maintenance status add some uncertainty, but not enough to constitute a high-risk red flag.

Recommendations

Only connect your Wati account after confirming you trust Rube/Composio and their data handling practices, and grant the minimum necessary permissions.
Review the exact tool schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid invoking actions beyond the intended scope.
Validate the automation flow in a test or low-privilege Wati environment before using it on production data.
Confirm data residency, log retention, and third-party sharing policies with the service provider.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "wati-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/wati-automation/SKILL.md
2. Save it as ~/.claude/skills/wati-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Wati Automation via Rube MCP

Automate Wati operations through Composio's Wati toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/wati

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Wati connection via RUBE_MANAGE_CONNECTIONS with toolkit wati
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit wati
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Wati operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Wati task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["wati"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Wati-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `wati`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Composio tasks via Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_