$ loading_
Automate L2s tasks with Rube MCP after checking current tool schemas.
This skill appears to be an open-source prompt-only wrapper with no local secrets required, and its source has strong community trust, so the baseline risk is low. However, it is designed around remote Rube MCP usage and downstream external connection authorization, meaning task data and parameters may be sent to third-party services; this warrants caution rather than high risk.
The material says the skill itself requires no local API key, but it requires creating an `l2s` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link if inactive, which implies reliance on third-party connection credentials. The skill does not explicitly collect secrets itself, but there is the ordinary risk of persistent access being granted through external authorization.
The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing discovery/execution through remote calls such as `RUBE_SEARCH_TOOLS`, `RUBE_MULTI_EXECUTE_TOOL`, and `RUBE_REMOTE_WORKBENCH`. This means user task descriptions, arguments, and session data may be sent to Rube/Composio-related services. The endpoint is declared and function-related, so this is a normal egress concern rather than a red-flag unknown exfiltration case.
The system flags this as `prompt-only`, and the material only describes workflows for invoking remote MCP tools; it does not declare local process spawning, script execution, or system-level permission requests. Based on the skill description itself, the local code-execution surface appears limited.
The skill is intended to automate 'L2s operations' and performs concrete actions through remote tools. While the material does not claim direct local file read/write, remote execution may access account or resource data that the user authorizes through the `l2s` connection. There is no clear sign of excessive local access beyond stated purpose, but it should be treated as having operational access to external business data.
The source is an open-source GitHub repository, the system marks it as `open-source`, and community adoption is high (64.7k stars), all of which materially reduce risk. The license and maintenance status are unclear, and the README depends on external Rube/Composio services, so the exact repository contents and recent maintenance should still be verified; however, the available material does not show a supply-chain red flag strong enough for a high-risk rating.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "l2s-automation" skill from askskill: 1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/l2s-automation/SKILL.md 2. Save it as ~/.claude/skills/l2s-automation/SKILL.md 3. Reload skills and tell me it's ready
Automate L2s operations through Composio's L2s toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/l2s
RUBE_MANAGE_CONNECTIONS with toolkit l2sRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit l2sAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "L2s operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific L2s task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["l2s"]
session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
RUBE_SEARCH_TOOLSRUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing toolsmemory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with L2s-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit l2s |
| 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 Cloudlayer tasks via Rube MCP after checking current tool schemas.
Automate Byteforms form tasks and workflow actions through Rube MCP.
Automate Dadata Ru lookups, validation, and data tasks through Rube MCP.
Automate Dialpad calling and collaboration tasks through Rube MCP workflows.
Automate Felt workflows and bulk actions through Rube MCP efficiently.
Automate Cabinpanda tasks through Rube MCP to speed up document workflows.
Automate Lmnt tasks through Rube MCP using current tool schemas first.
Automate Autom workflows via Rube MCP while checking current tool schemas first.
Automate Langbase workflows through Rube MCP using current tool schemas.
Automate Livesession workflows via Rube MCP using current tool schemas first.
Automate Composio tasks via Rube MCP with tool schema lookup first.
Automate AI/ML API workflows via Rube MCP, checking latest tool schemas first.