How does stannp-automation ensure tool schemas stay up-to-date?

Always fetch current schemas via RUBE_SEARCH_TOOLS before executing to avoid stale slugs and argument types.

What should I do if RUBE_MANAGE_CONNECTIONS reports a non-ACTIVE status?

Follow the returned auth link, re-check status until ACTIVE before running workflows.

Is including memory mandatory in multi-execute calls?

Yes—memory must be included, even if empty, to preserve execution context and support pagination.

stannp-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Stannp Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/stannp

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Stannp workflows via Composio's Stannp toolkit using Rube MCP. This skill always fetches current tool schemas before execution to keep automations aligned with up-to-date capabilities and avoids hard-coded tool slugs.

How This Skill Works

RUBE_SEARCH_TOOLS fetches available Stannp tools and their input schemas. RUBE_MANAGE_CONNECTIONS ensures an ACTIVE connection for the Stannp toolkit. RUBE_MULTI_EXECUTE_TOOL runs the selected tool with memory and schema-compliant arguments.

When to Use It

Scale repetitive Stannp campaigns by automating tool runs with current schemas.
Start a new Stannp workflow only after fetching up-to-date tool schemas via RUBE_SEARCH_TOOLS.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the Stannp toolkit before execution.
Bulk process multiple Stannp tasks with RUBE_MULTI_EXECUTE_TOOL and a proper memory payload.
Reuse a session ID across related Stannp tasks to speed up processing; create new IDs for new campaigns.

Quick Start

Step 1: Run RUBE_SEARCH_TOOLS with use_case: 'Stannp operations' and session: {generate_id: true}.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ['stannp'] and session_id from Step 1 results.
Step 3: Run RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and arguments from Step 1, memory: {}, session_id: 'your_session_id'.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate new IDs for new campaigns and watch for pagination.

Example Use Cases

Automate sending a batch of personalized postcards by discovering a tool slug from RUBE_SEARCH_TOOLS and executing with generated arguments.
Identify the Stannp tooling options via RUBE_SEARCH_TOOLS and run a selected tool with campaign data.
After ensuring an ACTIVE Stannp connection, execute a sequence of tools in a single session to streamline a campaign.
Process a queue of postcard orders using RUBE_MULTI_EXECUTE_TOOL with a memory payload that tracks progress.
Iterate through all available templates by handling pagination in tool schema responses and triggering multiple tools for a campaign.

Frequently Asked Questions

Add this skill to your agents