What is required to start automating Needle tasks with this skill?

You need an active Rube MCP connection, RUBE_SEARCH_TOOLS to fetch current tool schemas, and the ability to manage Needle connections via RUBE_MANAGE_CONNECTIONS.

Should I hardcode tool slugs or arguments?

No. The skill emphasizes always discovering tool slugs and their required inputs with RUBE_SEARCH_TOOLS to stay aligned with current schemas.

What happens if tool schemas change?

You should re-run RUBE_SEARCH_TOOLS to retrieve updated slugs and argument names, then adjust your RUBE_MULTI_EXECUTE_TOOL calls accordingly and maintain memory and session continuity.

needle-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Needle Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/needle

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Needle operations through Composio's Needle toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows to ensure compatibility and up-to-date inputs.

How This Skill Works

Connect to Rube MCP and use RUBE_SEARCH_TOOLS to fetch current Needle tool schemas. Verify the Needle connection with RUBE_MANAGE_CONNECTIONS, then execute discovered tools via RUBE_MULTI_EXECUTE_TOOL, supplying exact field names from the schema and including memory. Use a session_id to manage workflow state and avoid hardcoding tool slugs or arguments.

When to Use It

You need to run a Needle workflow without hardcoding tool slugs or input schemas
Automating Needle tasks in an existing pipeline requires up-to-date tool schemas
You must verify that the RUBE_MANAGE_CONNECTIONS status is ACTIVE before execution
You want to adapt to tool schema changes by re-discovering tools instead of guessing inputs
Debugging or auditing Needle automation requires explicit memory handling and session reuse

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys needed)
Step 2: Run RUBE_SEARCH_TOOLS to confirm tool schemas and verify RUBE_MANAGE_CONNECTIONS for the needle toolkit
Step 3: Discover a tool slug, then execute it with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any Needle tool to get current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to tool execution
Use exact field names and types from the search results; avoid hardcoding slugs or args
Include memory in every RUBE_MULTI_EXECUTE_TOOL call (even if empty {})
Reuse session IDs within a single workflow and fetch new ones only for new workflows

Example Use Cases

Automate a Needle data extraction by discovering tools with RUBE_SEARCH_TOOLS and executing the appropriate slug with validated inputs
Integrate Needle tasks into a nightly pipeline by re-fetching tool schemas each run and reusing the session
Validate connectivity and tool availability by running RUBE_MANAGE_CONNECTIONS before any execution
Iterate through multiple Needle operations by bulk-executing discovered tools with RUBE_MULTI_EXECUTE_TOOL
Audit full tool schemas via RUBE_GET_TOOL_SCHEMAS to ensure compatibility before automation

Frequently Asked Questions

Add this skill to your agents