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

SKILL

onepage-automation

Name: onepage-automation
Author: Composio

Automate Onepage tasks through Rube MCP by discovering tools and running actions.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source prompt-style wrapper with no direct local secrets requirement or local code execution, and its high community adoption is a positive trust signal. However, it depends on remote Rube MCP/Composio and a Onepage connection to discover and execute external tools, so actual data egress and permission boundaries depend on those external services and warrant attention.

CredentialsCaution

The material states the skill itself needs no API key, but it requires an active `onepage` connection via `RUBE_MANAGE_CONNECTIONS` and completion of an auth flow through a returned link. There is no sign that the skill directly collects local secrets, but it does trigger third-party account authorization, and the token scope/storage details are not described.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio's Onepage toolkit for tool discovery, connection management, and execution. This means task arguments, session IDs, tool queries, and possibly business data are sent to the declared remote service. The endpoint is clearly identified and relevant to the function, but the material does not describe data minimization, retention, or forwarding boundaries.

Code executionLow risk

The system marks it as `prompt-only`, and the material contains no local install scripts, shell commands, dependency builds, or requirements to start local processes. It only describes how to call existing MCP tools, so there is no direct sign of local code execution or expanded system privileges.

Data accessCaution

The skill does not claim direct local file read/write access, but it can perform business operations in Onepage via `RUBE_MULTI_EXECUTE_TOOL`/`RUBE_REMOTE_WORKBENCH` and uses session reuse plus a memory parameter. Its effective data access therefore depends mainly on the Onepage account authorization and remote tool capabilities, with no fine-grained permission details provided.

Supply chainLow risk

The source is an open GitHub repository, the system marks it as `open-source`, and community adoption is very high (~64.9k stars), all of which are strong risk-reducing signals. Although the license and maintenance status are not clearly stated and the skill depends on external Rube/Composio services, the current material shows no obvious supply-chain red flags such as closed-source opaque exfiltration, impersonation, or deceptive provenance.

Recommendations

Only connect to `https://rube.app/mcp` when needed, and verify the Onepage authorization domain, requested scopes, and account identity.
In production, first validate actual accessible data and executable actions with a least-privilege Onepage test account.
Avoid placing unnecessary sensitive data in tool queries, arguments, or memory, and review the remote service's data retention policy.
Check the open-source repository and Composio/Onepage documentation to confirm maintenance status, change history, and the exact permission model.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Onepage Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/onepage

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["onepage"]
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 Onepage-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `onepage`
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 AI/ML API workflows via Rube MCP, checking latest tool schemas first.

ComposioGet→

$ loading_