What is fingertip-automation?

Automate Fingertip operations via Rube MCP using the Composio Fingertip toolkit.

Do I need API keys to use Rube MCP?

No API keys are needed; you just add the MCP endpoint (e.g., https://rube.app/mcp) to your client configuration.

Why must I search tools first?

Tool schemas change over time. Searching ensures you use current tool slugs and argument schemas and avoid hardcoding.

fingertip-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Fingertip Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/fingertip

Prerequisites

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

Step 2: Check Connection

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

Overview

Fingertip-automation enables you to automate Fingertip operations through Composio's Fingertip toolkit via Rube MCP. It emphasizes discovering current tool schemas first to avoid hardcoding slugs and arguments, managing a Fingertip connection, and executing tools in a safe, session-based workflow.

How This Skill Works

The workflow starts by verifying MCP connectivity and retrieving up-to-date tool schemas with RUBE_SEARCH_TOOLS. Next, you manage or establish the Fingertip connection using RUBE_MANAGE_CONNECTIONS and ensure the session is ACTIVE. Finally, you execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, supplying the tool slug, exact arguments from the schema, a memory payload, and a session_id.

When to Use It

When you need up-to-date Fingertip tool schemas before authoring or running a workflow
When performing a multi-step Fingertip automation that requires a consistent session
When validating and establishing a Fingertip connection prior to tool execution
When executing a batch of Fingertip tasks across multiple devices (bulk ops)
When debugging tool execution and ensuring schema compliance and pagination

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case: "Fingertip operations" to discover available tools
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ["fingertip"], session_id: "your_session_id" to ensure ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search, memory: {}, session_id: "your_session_id"

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to obtain current tool slugs and input schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from search results; do not hardcode schemas
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow; generate new ones for separate workflows

Example Use Cases

Auto-check Fingertip health on a fleet of devices by discovering tools and executing a health-check tool in a single session
Orchestrate a maintenance workflow across multiple Fingertip tools within one session for a device group
Bulk-run a fingertip operation on 100 devices using RUBE_REMOTE_WORKBENCH and run_composio_tool
Introduce a new Fingertip task and verify its schema with RUBE_GET_TOOL_SCHEMAS before use
Resume a long-running fingertip workflow by reusing an existing session_id and continuing tool executions

Frequently Asked Questions

Add this skill to your agents