What is genderize-automation?

A workflow that automates Genderize tasks via Composio's Rube MCP, ensuring up-to-date tool schemas are used.

What are the prerequisites?

Rube MCP connection, RUBE_SEARCH_TOOLS availability, an active genderize connection via RUBE_MANAGE_CONNECTIONS, and the habit of discovering tools before execution.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas can change; discovering tools avoids hardcoding slugs or arguments and ensures compatibility with current schemas.

genderize-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Genderize Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/genderize

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["genderize"]
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 Genderize-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `genderize`
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/genderize-automation/SKILL.mdView on GitHub

Overview

Automate Genderize operations through Composio's Rube MCP. It emphasizes discovering current tool schemas before execution and managing connections to keep workflows schema-compliant. This enables scalable, reliable genderization tasks with up-to-date tooling.

How This Skill Works

The workflow first uses RUBE_SEARCH_TOOLS to discover available Genderize tools and their input schemas. It then checks the connection status via RUBE_MANAGE_CONNECTIONS for the genderize toolkit and ensures it is ACTIVE. Finally, it executes the selected tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id to enable continuity across steps.

When to Use It

You need to perform a Genderize operation but the tool schemas may have changed, so you must discover current tools first.
You want to avoid hardcoding tool slugs or arguments and rely on dynamic, up-to-date schemas from RUBE_SEARCH_TOOLS.
Setting up a new Genderize workflow requires establishing or rechecking an ACTIVE connection to the genderize toolkit.
Running a multi-step Genderize task where subsequent steps depend on the results of initial tool discovery.
Bulk or sequential Genderize tasks where reusing a session_id improves efficiency and consistency.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys required).
Step 2: Run RUBE_SEARCH_TOOLS with a Genderize use_case to discover current tools and schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS for the genderize toolkit, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting tools to ensure you have current slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status for the genderize toolkit before execution.
Use the exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow when possible; generate new ones only for distinct workflows.

Example Use Cases

Process a list of customer names to determine gender distribution using the latest Genderize tools discovered via RUBE_SEARCH_TOOLS.
Validate and clean a CRM gender field by dynamically selecting the current Genderize tool slugs and schemas.
Import a bulk user dataset and run sequential genderize steps while maintaining a shared session for consistency.
Iterate on a genderize pipeline as tool schemas update, avoiding hardcoded tool references.
Run multiple genderize tasks in a single workflow by reusing a session and memory payload across tools.

Frequently Asked Questions

Add this skill to your agents