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

SKILL

apilio-automation

Automate Apilio tasks through Rube MCP using discovered current tool schemas.

Stars

★ 73,665

Source

GitHub

Updated

2026-08-28

// securityLow risk

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

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "apilio-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/apilio-automation/SKILL.md
2. Save it as ~/.claude/skills/apilio-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Confirm the latest tool definitions before execution

Developers or automation maintainers can search current Apilio tools and input schemas before running workflows, reducing failures caused by changed fields or tool slugs.

Verify whether the Apilio connection is usable

When a workflow cannot proceed, users can first check the apilio toolkit connection status. If it is not ACTIVE, they can complete authorization using the returned auth link.

Run Apilio automation through a standard workflow

When Apilio operations need to be automated, users can follow the standard pattern of searching tools, reusing the session, checking the connection, and then executing for better reliability.

// docs

AI summary

The documentation explains how to automate Apilio operations through Rube MCP using Composio’s Apilio toolkit. It covers prerequisites, connection setup and activation, the requirement to call RUBE_SEARCH_TOOLS first for current schemas, and the standard workflow using RUBE_MANAGE_CONNECTIONS and RUBE_MULTI_EXECUTE_TOOL. It also highlights common pitfalls such as session reuse, including the memory parameter, schema compliance, and pagination handling.

Show full docs ▾

Apilio Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/apilio

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["apilio"]
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 Apilio-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `apilio`
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

// FAQ

What is this skill?

It automates Apilio-related operations through Rube MCP using Composio’s Apilio toolkit. The docs emphasize searching tools first to get the current schema before execution.

What prerequisites are required?

You need Rube MCP connected and RUBE_SEARCH_TOOLS available. You also need an active apilio connection configured through RUBE_MANAGE_CONNECTIONS.

Why must I search tools first?

Because tool schemas may change, and the docs explicitly say not to hardcode tool slugs or arguments. Searching first provides the latest fields, execution guidance, and known pitfalls.

Automate Apiflash tasks like webpage screenshots and workflow integrations via Rube MCP.

ComposioGet→

$ loading_