simplesat-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/simplesat-automation --openclawSimplesat Automation via Rube MCP
Automate Simplesat operations through Composio's Simplesat toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/simplesat
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Simplesat connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsimplesat - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitsimplesat - 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: "Simplesat 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 Simplesat task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["simplesat"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Simplesat-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit simplesat |
| 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/simplesat-automation/SKILL.mdView on GitHub Overview
Automate Simplesat operations through Composio's Simplesat toolkit via Rube MCP. The workflow emphasizes discovering current tool schemas first and validating an ACTIVE connection before running tasks. This makes integrations resilient to schema changes and reduces the risk of misconfigured tool calls.
How This Skill Works
The tool uses RUBE_SEARCH_TOOLS to discover available Simplesat tools and their input schemas, then verifies the connection with RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE status. When a tool slug is selected, it executes the task with RUBE_MULTI_EXECUTE_TOOL, passing exact schema-compliant arguments and a memory payload within a session_id. Always include a session_id and memory even if empty to enable reliable workflow reuse.
When to Use It
- Need to automate a specific Simplesat task by first discovering current tools with RUBE_SEARCH_TOOLS
- Prepare and verify an ACTIVE Simplesat connection via RUBE_MANAGE_CONNECTIONS before running any tool
- Execute a discovered tool slug using RUBE_MULTI_EXECUTE_TOOL with the required arguments and memory
- Reuse a single session_id across related workflow steps to maintain context and continuity
- Handle tool discovery with pagination tokens to ensure you fetch all available tools and schemas
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify reachability via RUBE_SEARCH_TOOLS
- Step 2: Connect to the Simplesat toolkit using RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, pick a tool slug from the results, and run it via RUBE_MULTI_EXECUTE_TOOL with a session_id and a memory payload
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing to get current tool slugs and schemas
- Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before any tool execution
- Use exact field names and types from the discovery results; avoid hardcoding
- Include memory payload in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
- Reuse session_id within a workflow and fetch fresh results when starting a new session
Example Use Cases
- Nightly batch: discover tools, establish an ACTIVE connection, and run a chosen Simplesat task via TOOL_SLUG_FROM_SEARCH, then store results
- Triggered workflow: on new survey creation, discover the appropriate tool and execute it to send reminders
- Multi-tool batch: in a single session, export results and push them to a dashboard using two discovered tool slugs
- Discovery with pagination: implement a loop to fetch all tools across pages until no tokens remain
- Connection health check: monitor RUBE_MANAGE_CONNECTIONS; re-auth if not ACTIVE and retry execution
