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

SKILL

landbot-automation

Name: landbot-automation
Author: Composio

Automate Landbot bot tasks and workflows through Rube MCP tool calls

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill itself is an open-source prompt-style wrapper, but its functionality depends on external Rube MCP/Composio and a Landbot connection to perform remote tool actions. Based on the provided material, there is no clear red flag for local code execution or local file access; the main concern is that task data may be sent to third-party services after connection, while the exact data flows and permission scope are not fully disclosed.

CredentialsCaution

The material claims 'no API keys needed,' but it still requires establishing a `landbot` connection via `RUBE_MANAGE_CONNECTIONS` and completing an external auth flow. This means credentials likely exist but are handled through a hosted Rube/Composio connection. That creates the usual sensitivity around third-party managed tokens, but no explicit credential theft or abuse red flag is shown.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Landbot-related services to discover and execute tools; user task content, arguments, session IDs, and connection state will likely be sent to those declared third-party endpoints. The material does not list unrelated or suspicious egress targets, so this is a standard caution for declared remote data transfer.

Code executionLow risk

From the material, this is a prompt/workflow instruction-style skill and does not require installing executables locally, starting local processes, or granting shell/system privileges. Execution occurs through MCP tool calls rather than local code execution. No execution capability beyond a typical prompt-only skill is described.

Data accessCaution

The skill is intended to automate Landbot operations, and the use of `RUBE_MULTI_EXECUTE_TOOL`, bulk operations, and session reuse implies it can read/write remote bot or workflow-related data within the authorized Landbot scope. The material does not indicate local file access, but it also does not define a clear least-privilege boundary, so the granted connection scope should be reviewed carefully.

Supply chainLow risk

The source is an open GitHub repository with high community adoption (64.7k stars), which are strong risk-reducing signals. The material is mainly README/prompt content and does not expose suspicious install scripts or closed-source binaries; the remaining caveats are the undeclared license, unknown maintenance status, and the fact that the external Rube/Composio services are not fully auditable from this repository alone.

Recommendations

Before connecting Landbot, review the exact scopes requested by the Rube/Composio authorization flow and use a least-privilege account.
Avoid sending unnecessary sensitive data in tool arguments, and confirm that your organization accepts third-party processing via `rube.app`/Composio.
Validate `RUBE_SEARCH_TOOLS` outputs and execution behavior in a test environment first to avoid unintended changes to production Landbot resources.
If possible, review the relevant privacy policy, data retention details, and how connection tokens are managed.

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 "landbot-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/landbot-automation/SKILL.md
2. Save it as ~/.claude/skills/landbot-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Landbot Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/landbot

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Landbot connection via RUBE_MANAGE_CONNECTIONS with toolkit landbot
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 landbot
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: "Landbot 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 Landbot task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["landbot"]
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 Landbot-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `landbot`
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 Botsonic tasks and workflows through Rube MCP integrations.

ComposioGet→

$ loading_