home / skills / composiohq / awesome-claude-skills / needle-automation

needle-automation skill

safe

/needle-automation

This skill automates Needle tasks via Rube MCP by discovering current tool schemas first, ensuring active connections, and executing tools safely.

npx playbooks add skill composiohq/awesome-claude-skills --skill needle-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.8 KB

---
name: needle-automation
description: "Automate Needle tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Needle Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/needle](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `needle`
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: "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](https://composio.dev)*

Overview

This skill automates Needle tasks through Composio’s Rube MCP to run Needle toolkit operations reliably. It guides discovery of current tool schemas, connection management, and safe multi-tool execution patterns. The focus is on calling RUBE_SEARCH_TOOLS first, verifying connections, and using schema-compliant arguments for stable automation.

How this skill works

The skill queries Rube MCP for available Needle tools and their input schemas using RUBE_SEARCH_TOOLS, then verifies an active Needle connection via RUBE_MANAGE_CONNECTIONS. Once tools and connection status are confirmed, it executes operations with RUBE_MULTI_EXECUTE_TOOL (including a memory object and session ID). It also supports pagination-aware discovery and bulk operations through RUBE_REMOTE_WORKBENCH.

When to use it

Automate repeatable Needle operations (provisioning, configuration, or orchestration).
Before running any Needle workflow to fetch the current tool schema and execution plan.
When integrating Needle into multi-step composio workflows or orchestrations.
During CI/CD or scheduled jobs that need deterministic Needle task behavior.
When you must avoid hardcoded tool slugs or outdated argument schemas.

Best practices

Always call RUBE_SEARCH_TOOLS first and use the returned schema fields and types.
Verify toolkit connection status with RUBE_MANAGE_CONNECTIONS and follow any auth links until status is ACTIVE.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs for related workflow steps; generate new session IDs for separate workflows.
Inspect search responses for pagination tokens and fetch remaining pages before assuming discovery is complete.

Example use cases

Discover available Needle operations for a given environment and generate an execution plan.
Programmatically connect and authenticate the Needle toolkit via RUBE_MANAGE_CONNECTIONS during onboarding.
Execute a sequence of Needle tools with RUBE_MULTI_EXECUTE_TOOL for a multi-step deployment.
Run bulk Needle tasks using RUBE_REMOTE_WORKBENCH and run_composio_tool() for mass provisioning.
Fetch full schemas with RUBE_GET_TOOL_SCHEMAS to validate tool inputs before execution.

FAQ

Do I need API keys to use Rube MCP?

No API keys are required. Add the MCP endpoint (https://rube.app/mcp) to your client configuration to connect.

What if a tool schema changes after I coded against it?

Always call RUBE_SEARCH_TOOLS before execution; use the returned schema fields and types rather than hardcoding slugs or arguments. Pagination and schemaRef lookups may be needed to get full details.