Do I always need to search tools first?

Yes. Always fetch current tool schemas with RUBE_SEARCH_TOOLS to avoid outdated slugs and fields.

What if the connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then re-check for ACTIVE before executing.

Why include memory in RUBE_MULTI_EXECUTE_TOOL calls?

Memory preserves state across tool steps and is required even if empty to maintain workflow context.

genderapi-io-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/genderapi-io-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Genderapi IO Automation via Rube MCP

Automate Genderapi IO operations through Composio's Genderapi IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/genderapi_io

Prerequisites

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

Step 2: Check Connection

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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/genderapi-io-automation/SKILL.md

View on GitHub

Overview

Automate Genderapi IO operations through Composio's Genderapi IO toolkit via Rube MCP. Always search for current tool schemas before running workflows to avoid broken slugs or fields. This reduces errors and keeps automations aligned with the latest toolkit updates.

How This Skill Works

Connect Rube MCP and verify an active Genderapi IO connection. Discover available tools with RUBE_SEARCH_TOOLS to obtain slugs and input schemas, then verify the connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, correct arguments, and a memory payload.

When to Use It

When you need to automate Genderapi IO tasks and ensure tool schemas are up to date.
When integrating Genderapi IO workflows that require verified active connections before execution.
When you want to reuse a session ID across a multi-step workflow for consistency.
When performing bulk or multi-tool operations via RUBE_REMOTE_WORKBENCH or similar orchestration.
When debugging or updating a workflow after tool schema changes or pagination in responses.

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS is available and discover tools for Genderapi IO.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["genderapi_io"] and ensure ACTIVE.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and handle pagination tokens when present.

Example Use Cases

Discover a Genderapi IO task, connect, and execute the tool using the latest slug and input schema.
Reconnect or re-authenticate when the Genderapi IO connection becomes inactive and re-run the workflow.
Run multiple Genderapi IO operations in a single session using RUBE_MULTI_EXECUTE_TOOL with a shared memory payload.
Bulk fetch paginated results from Genderapi IO by iterating through pages until completion.
Debug a failing workflow by re-running tool discovery to confirm schemas before execution.

Frequently Asked Questions

Add this skill to your agents