Agent skill

Ip2location Io Automation

Automate Ip2location IO tasks via Rube MCP (Composio). Always search tools first for current schemas.

Get the complete skill folder, including its scripts and reference files.

This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.

Listed 2026-10-06 · Updated 2026-10-06

When to use this skill

Use Ip2location Io Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Ip2location IO tasks via Rube MCP (Composio). Always search tools first for current schemas.

When not to use it

Skip Ip2location Io Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Get the skill files

Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/ip2location-io-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/ip2location-io-automation/ instead.
Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation: 70/100
Practical detail: 68/100
Source evidence: 63/100
Source signals: 80/100

Model compatibility evidence

claude · inferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
chatgpt · untested
No model-specific signal or recorded compatibility test was found.
gemini · untested
No model-specific signal or recorded compatibility test was found.
copilot · untested
No model-specific signal or recorded compatibility test was found.
llama · untested
No model-specific signal or recorded compatibility test was found.
perplexity · untested
No model-specific signal or recorded compatibility test was found.
mistral · untested
No model-specific signal or recorded compatibility test was found.
grok · untested
No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Ip2location IO Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/ip2location_io](https://composio.dev/toolkits/ip2location_io)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Ip2location IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location_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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location_io` 3. If connection is not ACTIVE, follow the returned auth link to complete setup 4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

``` RUBE_SEARCH_TOOLS queries: [{use_case: "Ip2location 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 Ip2location IO task"}] session: {id: "existing_session_id"} ```

### Step 2: Check Connection

``` RUBE_MANAGE_CONNECTIONS toolkits: ["ip2location_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 Ip2location IO-specific use case | | Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location_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](https://composio.dev)*

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.

Open your saved library