home / skills / composiohq / awesome-claude-skills / tpscheck-automation

tpscheck-automation skill

safe

/tpscheck-automation

This skill automates Tpscheck tasks via Composio and Rube MCP, ensuring real-time tool discovery and validated connections before execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill tpscheck-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: tpscheck-automation
description: "Automate Tpscheck tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Tpscheck Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/tpscheck](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `tpscheck`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Tpscheck tasks through Composio's Tpscheck toolkit using the Rube MCP interface. It coordinates discovery, connection checks, and multi-step tool execution to run reliable Tpscheck workflows. Always discover tools first to obtain current schemas before executing any operations.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to fetch available tool slugs, input schemas, and execution guidance. It verifies or establishes the Tpscheck connection with RUBE_MANAGE_CONNECTIONS, then runs schema-compliant calls via RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs). Session IDs and memory objects are managed to keep workflows consistent.

When to use it

Automating routine Tpscheck checks or diagnostics across many targets
Running multi-step Tpscheck workflows that require tool discovery and schema-aware inputs
Integrating Tpscheck operations into larger automated pipelines or CI
Performing bulk operations using RUBE_REMOTE_WORKBENCH and run_composio_tool()
When you need reliable execution that adapts to changing tool schemas

Best practices

Always call RUBE_SEARCH_TOOLS first — do not hardcode tool slugs or argument shapes
Verify the Tpscheck connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools
Pass exact field names and types from the returned schema; use RUBE_GET_TOOL_SCHEMAS when needed
Include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls and reuse session IDs within a workflow
Handle pagination tokens on search responses and iterate until all results are retrieved

Example use cases

Discover current Tpscheck tools, validate connection, and run a single diagnostic tool via RUBE_MULTI_EXECUTE_TOOL
Execute a bulk Tpscheck audit across many accounts using RUBE_REMOTE_WORKBENCH + run_composio_tool()
Automate a scheduled Tpscheck health-check pipeline that reuses session IDs and stores results in memory
Fetch full schemas for custom integrations using RUBE_GET_TOOL_SCHEMAS before building a client-side form

FAQ

Do I need an API key to connect to Rube MCP?

No API key is required; add https://rube.app/mcp as an MCP server in your client configuration.

What if the Tpscheck connection is not ACTIVE?

Call RUBE_MANAGE_CONNECTIONS; follow the returned auth link to complete setup, then confirm ACTIVE before proceeding.