$ ~/registry/skill/composiohq-composio-skills-test-app-automation

SKILL

test-app-automation

Name: test-app-automation
Author: Composio

Automate Test App workflows via Rube MCP with schema-aware tool discovery first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill material is primarily prompt/documentation-like and does not itself declare local execution, secrets, or direct file access. However, it is designed to connect to Rube MCP and invoke external tools remotely, which introduces normal remote-operation and data-egress considerations; the high-star open-source GitHub source materially lowers supply-chain risk, though actual runtime tool behavior should still be verified during integration.

CredentialsCaution

The material says 'No API keys needed', but it also requires establishing an ACTIVE `test_app` connection via `RUBE_MANAGE_CONNECTIONS` and possibly following an auth link. This implies runtime third-party authorization or tokens may still be involved even if not exposed directly by the skill, so the granted scope and session misuse surface should be reviewed.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to discover and execute tools; task arguments, session IDs, connection status, and execution requests will be sent to the stated external service. This is normal network egress for a remote MCP setup, and no unrelated or hidden endpoints are disclosed in the material.

Code executionLow risk

Based on the provided material, this is a prompt/workflow instruction and does not declare spawning local processes, executing scripts, or requesting system-level capabilities; its role is mainly to guide calls to remote MCP tools. From the material alone, there is no clear local code-execution red flag.

Data accessCaution

The material does not declare direct read/write access to local files or host resources, but it does send Test App task inputs, tool arguments, and session information to the remote MCP and may access data in the connected Test App account. The effective data-access scope depends on the connected toolkit and granted account permissions, so sensitive input should be minimized.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (about 64.9k stars), which is a significant positive trust signal; the material also appears to be README/skill guidance rather than a closed-source binary. Missing license information and unknown maintenance status are minor audit gaps, but not enough to elevate this to high risk.

Recommendations

Verify the privacy policy, logging retention, and data-handling scope of `rube.app/mcp` and Composio before connecting.
Grant only the minimum permissions needed when authorizing `test_app`, and review/revoke the connection regularly.
Avoid sending unnecessary sensitive data in queries, memory, or tool arguments.
Before production use, inspect the exact tools returned by `RUBE_SEARCH_TOOLS` and confirm their permission boundaries.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "test-app-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/test-app-automation/SKILL.md
2. Save it as ~/.claude/skills/test-app-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Test 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_CONNECTIONS with toolkit test_app
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 test_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_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 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

Automate Bench workflows through Rube MCP using up-to-date tool schemas.

ComposioGet→

$ loading_