test-app-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/test-app-automation --openclawTest App Automation via Rube MCP
Automate Test App operations through Composio's Test App toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/test_app
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Test App connection via
RUBE_MANAGE_CONNECTIONSwith toolkittest_app - 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 toolkittest_app - 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: "Test App 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 Test App task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["test_app"]
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 Test App-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit test_app |
| 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/test-app-automation/SKILL.mdView on GitHub Overview
This skill automates Test App operations through Composio's Test App toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to avoid hardcoding tool slugs or arguments. Following the workflow ensures up-to-date tooling and reliable connections.
How This Skill Works
Connect to Rube MCP at https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds to fetch tool schemas. Manage the Test App connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE before executing any workflows; then discover tools, validate schemas, and run tools via RUBE_MULTI_EXECUTE_TOOL, always including memory and session context as needed.
When to Use It
- When you need to automate a specific Test App operation by using the latest tool schemas from RUBE_SEARCH_TOOLS.
- When establishing or validating a Test App connection, ensuring the connection shows ACTIVE before workflows run.
- When reusing an existing session_id to maintain context across multiple tool executions.
- When tool schemas may have changed and you must fetch current tool slugs and arguments before running tasks.
- When executing multiple tools in sequence or in bulk with RUBE_MULTI_EXECUTE_TOOL.
Quick Start
- Step 1: Use RUBE_SEARCH_TOOLS to discover available Test App tools.
- Step 2: Use RUBE_MANAGE_CONNECTIONS to connect the test_app toolkit and confirm ACTIVE.
- Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and proper memory and session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before running workflows to fetch up-to-date tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status prior to tool execution.
- Use exact field names and types from the research results; avoid hardcoding slugs.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if it’s empty.
- Reuse session IDs within a workflow and generate new ones only for new workflows.
Example Use Cases
- Discover a Test App operation with RUBE_SEARCH_TOOLS, then execute the corresponding slug with RUBE_MULTI_EXECUTE_TOOL.
- Connect to the test_app toolkit using RUBE_MANAGE_CONNECTIONS and proceed only when ACTIVE.
- Batch several actions by listing multiple tools in a single RUBE_MULTI_EXECUTE_TOOL call, sharing memory and session_id.
- Maintain state across steps by reusing a session_id across the workflow.
- Handle pagination tokens in RUBE_SEARCH_TOOLS responses to fetch all available tools.
