What is satismeter-automation?

A skill to automate Satismeter tasks using Composio's Satismeter toolkit via Rube MCP, with tool discovery happening first to ensure current schemas.

What are the prerequisites?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available), an ACTIVE Satismeter connection via RUBE_MANAGE_CONNECTIONS with toolkit 'satismeter', and always search for tool schemas before execution.

Do I need to hardcode tool slugs or arguments?

No. Always search tools first with RUBE_SEARCH_TOOLS to obtain current slugs and input schemas; avoid hardcoding slugs or arguments.

satismeter-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Satismeter Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/satismeter

Prerequisites

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

Step 2: Check Connection

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

Overview

Satismeter-automation orchestrates Satismeter operations through Composio's Satismeter toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before any execution to avoid stale or hardcoded inputs. Prerequisites include a connected Rube MCP, an ACTIVE Satismeter connection through RUBE_MANAGE_CONNECTIONS (toolkit: satismeter), and always calling RUBE_SEARCH_TOOLS first.

How This Skill Works

You first discover available Satismeter tools with RUBE_SEARCH_TOOLS. Next, verify the Satismeter connection using RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying exact schema-compliant arguments and a memory object, using the tool slug obtained from the discovery results.

When to Use It

Setting up a new Satismeter workflow and discovering current tool schemas first
Running a Satismeter task only after RUBE_MANAGE_CONNECTIONS reports ACTIVE
Automating multiple Satismeter operations in a single session
Validating schemas and arguments before tool execution
Handling pagination and retrieving bulk tool results during discovery

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and ensure RUBE_SEARCH_TOOLS responds
Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkit 'satismeter' and confirm ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug

Best Practices

Always call RUBE_SEARCH_TOOLS before scripting to get up-to-date tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the discovery results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Automate a Satismeter survey operation by discovering the tool and executing the corresponding slug with required inputs
Connect to Satismeter via RUBE_MANAGE_CONNECTIONS, verify ACTIVE, then run a task without hardcoding slugs
Execute a sequence of Satismeter tasks in a single session using RUBE_MULTI_EXECUTE_TOOL
Before scripting, fetch current tool schemas with RUBE_SEARCH_TOOLS and adapt your workflow accordingly
Process paginated tool responses during discovery and perform bulk Satismeter operations

Frequently Asked Questions

Add this skill to your agents