What is tpscheck-automation?

It is a structured approach to automate Tpscheck tasks by discovering current tool schemas, ensuring an ACTIVE Rube MCP connection, and executing tools with schema-compliant arguments.

How do I start using it?

Set up the Rube MCP endpoint, run RUBE_SEARCH_TOOLS to fetch current Tpscheck tool schemas, connect with RUBE_MANAGE_CONNECTIONS, and then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS before execution to fetch updated slugs and arguments; avoid hardcoding tool slugs or schemas.

tpscheck-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Tpscheck Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/tpscheck

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Tpscheck operations using Composio's Rube MCP toolkit. This skill orchestrates discovery of current tool schemas, validates an ACTIVE Tpscheck connection, and executes tools with precise, schema-compliant arguments to streamline workflows.

How This Skill Works

Begin by discovering available Tpscheck tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Then verify the connection with RUBE_MANAGE_CONNECTIONS and set the session. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying memory and the schema-aligned arguments, reusing sessions when possible.

When to Use It

Automating routine Tpscheck tasks without manually updating tool slugs
When tool schemas change and you must fetch updated arguments first
Ensuring an ACTIVE Rube MCP connection before executions
Running bulk Tpscheck operations across multiple tools in one workflow
Reusing a session for sequential Tpscheck tasks to improve speed

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Tpscheck tool schemas and note the tool slugs.
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkit ["tpscheck"] to activate the connection, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug.

Best Practices

Always search tools first before executing any workflow
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new tasks

Example Use Cases

Automate a daily Tpscheck data pull by discovering tools, connecting, and executing the needed tool slug
Run bulk Tpscheck operations across several tasks in a single workflow
Validate tool schemas before live runs by performing a discovery step and checking slugs
Recover from a dropped connection by re-running RUBE_MANAGE_CONNECTIONS and retrying the tool
Paginate through tool results with RUBE_SEARCH_TOOLS and RUBE_GET_TOOL_SCHEMAS to process all items

Frequently Asked Questions

Add this skill to your agents