What is gender-api-automation used for?

It automates Gender API tasks through Composio's Rube MCP toolkit, always fetching current tool schemas before execution.

Do I need API keys to use this skill?

No API keys are needed for the Rube MCP setup. Add the endpoint https://rube.app/mcp, connect to the gender_api toolkit, and run tools.

How do I handle schema changes or tool updates?

Always run RUBE_SEARCH_TOOLS first to retrieve the latest tool slugs and input schemas, then proceed with connection checks and execution.

gender-api-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Gender API Automation via Rube MCP

Automate Gender API operations through Composio's Gender API toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/gender_api

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates operations against Gender API using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas before execution and managing connections and sessions to run workflows reliably.

How This Skill Works

You start by discovering available Gender API tools with RUBE_SEARCH_TOOLS to get current slugs and input schemas. Next, verify or establish an ACTIVE connection using RUBE_MANAGE_CONNECTIONS with the gender_api toolkit. Finally, execute the chosen tool(s) via RUBE_MULTI_EXECUTE_TOOL, including the memory payload and a session_id to keep state across steps.

When to Use It

When you need up-to-date tool schemas before performing any Gender API task
When you must ensure an ACTIVE connection to the Gender API toolkit
When orchestrating a multi-step workflow that calls multiple gender API tools
When processing a batch of gender checks in a single session
When troubleshooting failures by re-verifying tool availability and connection status

Quick Start

Step 1: Ensure Rube MCP is added as an MCP server and RUBE_SEARCH_TOOLS responds
Step 2: Discover available tools with RUBE_SEARCH_TOOLS for your Gender API task
Step 3: Check the connection with RUBE_MANAGE_CONNECTIONS and then execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, including memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results in your requests
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and revalidate or renew them for new tasks

Example Use Cases

Discover the appropriate Gender API tool with RUBE_SEARCH_TOOLS, connect via RUBE_MANAGE_CONNECTIONS, then run a gender lookup tool using RUBE_MULTI_EXECUTE_TOOL
Process a list of user names by iterating through tools in a single session, leveraging memory for stateful results
When tool schemas change, re-run RUBE_SEARCH_TOOLS to fetch the latest tool_slugs before execution
Execute multiple gender API operations in one go by passing an array of tool_slugs in RUBE_MULTI_EXECUTE_TOOL
After authenticating via the provided link, verify ACTIVE status and proceed with batch gender checks

Frequently Asked Questions

Add this skill to your agents