What is the role of RUBE_SEARCH_TOOLS in this skill?

It fetches the current API Ninjas tool schemas so you can use up-to-date slugs and argument names.

Is an active connection required before executing tools?

Yes. Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE for the api_ninjas toolkit before running workflows.

What if tool schemas change after I started a workflow?

Rerun RUBE_SEARCH_TOOLS to refresh slugs and schemas, then adjust your tool execution accordingly.

api-ninjas-automation

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

Files (1)

SKILL.md

2.9 KB

API Ninjas Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/api_ninjas

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates API Ninjas operations through Composio's API Ninjas toolkit using Rube MCP. It enforces discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows to ensure you use up-to-date tool slugs and argument schemas.

How This Skill Works

Set up a Rube MCP connection to the API Ninjas toolkit and verify it's ACTIVE with RUBE_MANAGE_CONNECTIONS. Use RUBE_SEARCH_TOOLS to discover available tools and their input schemas, select a tool_slug, supply exactly named arguments, and execute via RUBE_MULTI_EXECUTE_TOOL, including a memory object (even if empty) and the session_id from the discovery step.

When to Use It

When starting a new API Ninjas automation and needing current tool schemas
When verifying Rube MCP connection and ensuring an ACTIVE status before running tools
When discovering available API Ninjas tools and choosing the right tool_slug for your task
When orchestrating multi-tool workflows in a single session and reusing session IDs
When updating production workflows after tool schemas change to avoid broken integrations

Quick Start

Step 1: Discover available API Ninjas tools with RUBE_SEARCH_TOOLS
Step 2: Connect or validate connection to toolkit api_ninjas using RUBE_MANAGE_CONNECTIONS
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, providing memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoded slugs
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before any execution
Use exact field names and types from the search results rather than guessing
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Discover API Ninjas tools with RUBE_SEARCH_TOOLS, then run a chosen task using the discovered slug and arguments
Establish and validate an ACTIVE api_ninjas connection via RUBE_MANAGE_CONNECTIONS, then execute multiple tools in one session
Handle paginated responses by continuing to fetch using updated tool schemas from RUBE_SEARCH_TOOLS
Refresh tool schemas before deploying a production workflow to avoid mismatches
Bulk-run several API Ninjas tasks using RUBE_REMOTE_WORKBENCH with run_composio_tool()

Frequently Asked Questions

Add this skill to your agents