What is required to start pingdom-automation?

RUBE MCP must be connected, RUBE_SEARCH_TOOLS must respond with Pingdom tool schemas, and a Pingdom connection must be ACTIVE via RUBE_MANAGE_CONNECTIONS.

Do I need API keys for Pingdom tasks?

No API keys are required. Authentication is handled through the MCP setup and Rube connections.

How should I execute a discovered tool?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, supply arguments that match the schema, include memory: {} and a session_id.

pingdom-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Pingdom Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/pingdom

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Pingdom operations through Composio's Pingdom toolkit using Rube MCP. Start by discovering current tool schemas with RUBE_SEARCH_TOOLS, then connect to Pingdom and execute discovered tools in a managed, session-based workflow.

How This Skill Works

This skill uses a 3-step pattern: first, discover available Pingdom tools with RUBE_SEARCH_TOOLS to fetch current slugs and input schemas; second, ensure the Pingdom connection is ACTIVE via RUBE_MANAGE_CONNECTIONS; third, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing exact schema-compliant arguments, a memory payload, and a session_id. Always include memory and reuse sessions when appropriate.

When to Use It

To run a Pingdom task after verifying current tool schemas
Before any workflow to ensure the Pingdom connection is ACTIVE
When executing a discovered tool, ensuring memory and session_id are provided
For multi-tool or bulk Pingdom operations via RUBE_MULTI_EXECUTE_TOOL
When reusing a session across multiple steps within a Pingdom workflow

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case set to a Pingdom task to fetch current tool slugs and schemas
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ["pingdom"] and session_id to verify ACTIVE status
Step 3: RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug, proper arguments, memory: {} and the session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to get the latest tool slugs and schemas
Verify the Pingdom connection shows ACTIVE with RUBE_MANAGE_CONNECTIONS before running tools
Use exact field names and types from the search results; avoid hardcoding slugs
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow to maintain continuity and context

Example Use Cases

Discover Pingdom tasks with RUBE_SEARCH_TOOLS, then create a new uptime check by executing the appropriate tool slug with the required arguments
Check the Pingdom connection status and update an alert threshold by running a validated tool from the current schema
Run multiple Pingdom operations in sequence using RUBE_MULTI_EXECUTE_TOOL within a single session
Fetch tool schemas via RUBE_GET_TOOL_SCHEMAS to compare against local expectations before execution
Handle large tool sets by paginating results and continuing tool discovery until all slugs are retrieved

Frequently Asked Questions

Add this skill to your agents