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

SKILL

lmnt-automation

Name: lmnt-automation
Author: Composio

Automate Lmnt tasks through Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be primarily a prompt/instruction wrapper for Rube MCP rather than a standalone executable tool. It does not declare local secrets, code execution, or direct file access, but it is designed to drive remote MCP tools and an external Lmnt connection, so normal third-party data flow and integration caution still applies.

CredentialsCaution

The material states the skill itself requires no keys, but it requires an ACTIVE `lmnt` connection via RUBE_MANAGE_CONNECTIONS and an auth-link flow, which implies reliance on third-party account authorization/tokens. There is no explicit sign of direct secret harvesting or exposure, but credentials are still involved at the external MCP/integration layer.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to discover and execute Lmnt tools. This means task content, arguments, and session information may be sent to the declared third-party service. The endpoint aligns with the stated purpose, and no clearly unrelated or covert exfiltration red flags are shown.

Code executionLow risk

The objective checks label it as prompt-only, and the material does not declare any need to install executables locally, spawn local processes, or run shell/scripts. The README is mainly operational guidance for invoking existing MCP tools, with no direct request for local code execution privileges.

Data accessCaution

There is no explicit claim of direct local file or system data access. However, via remote tool calls such as RUBE_SEARCH_TOOLS, RUBE_MULTI_EXECUTE_TOOL, and RUBE_REMOTE_WORKBENCH, the effective data access scope depends on the connected Lmnt tools and workflow arguments. No obvious excessive local permission request is shown, but remote business-data access should still be reviewed under least-privilege principles.

Supply chainLow risk

The source is a GitHub open-source repository with strong community adoption (64.7k stars), which are clear risk-reducing signals. The material looks more like a skill definition/README than a closed-source binary. The missing license declaration and unknown maintenance status add some governance uncertainty, but overall the supply-chain posture is still on the lower-risk side given the open-source and widely used source.

Recommendations

Before adding `https://rube.app/mcp`, verify that your organization permits Lmnt-related data to be handled by third-party MCP/Composio services and review their privacy/logging policies.
Use a least-privilege account when connecting `lmnt`, and regularly review/revoke unused authorizations.
Inspect the tool list and parameters returned by `RUBE_SEARCH_TOOLS` before execution to avoid sending sensitive content to unnecessary remote tools.
Prefer pinning a trusted repository version/commit and keep monitoring the repo's maintenance status and license information.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Lmnt Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/lmnt

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["lmnt"]
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 Lmnt-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `lmnt`
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 Landbot bot tasks and workflows through Rube MCP tool calls

ComposioGet→

$ loading_