← LeaderboardThe Skill Leaderboard

apex27-automation

Automate Apex27 tasks via Rube MCP (Composio). Always search tools first for current schemas.

Published by composio-community ↗composio-community/awesome-codex-skills

Try your first task

apex27-automation

Start a fresh conversation. Replace the highlighted placeholders.

Use apex27-automation to perform [the Apex27 operation and entity details] with the active connected account, using the current discovered schema; summarize the outcome. If the operation would publish, delete data, make a purchase, or change consequential settings, ask for final confirmation before executing it.

Required inputs

  • [the Apex27 operation and entity details]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: apex27-automationdescription: "Automate Apex27 tasks via Rube MCP (Composio). Always search tools first for current schemas."requires:   mcp: [rube]

Apex27 Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/apex27

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Apex27 connection via RUBE_MANAGE_CONNECTIONS with toolkit apex27
  • 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.

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

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Apex27 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 Apex27 task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["apex27"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Apex27-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit apex27
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio