$ ~/registry/skill/composiohq-composio-skills-pingdom-automation

SKILL

pingdom-automation

Name: pingdom-automation
Author: Composio

Automate Pingdom monitoring and alert tasks through Rube MCP workflows.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is primarily a prompt/workflow guide with no declared local code execution, file access, or built-in secrets, so its baseline risk is relatively low. However, it is intended to connect to third-party Rube MCP and Pingdom for remote actions, so network egress, account linking, and remote data operations still warrant caution.

CredentialsCaution

The material states the skill itself requires no API key, but it requires establishing an active Pingdom connection via `RUBE_MANAGE_CONNECTIONS` and completing a returned auth link, indicating reliance on Pingdom/Composio-side account authorization or tokens. No explicit credential theft behavior is shown, but there is the usual risk associated with third-party delegated access.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and using Composio's Pingdom toolkit, so user requests, session IDs, tool arguments, and related operational data would be sent to external services. The egress appears related to the stated functionality, but it is still third-party remote processing.

Code executionLow risk

Based on the objective check that this is `prompt-only`, the material does not declare spawning local processes, running scripts, installing dependencies, or invoking a system shell. It mainly describes how to call existing MCP tools rather than execute code locally.

Data accessCaution

There is no indication of local filesystem permission requests, but the stated purpose is to automate Pingdom operations and execute queries, bulk actions, and workflows through remote tools. That means it may access and modify monitoring resources and related data in the Pingdom account. This is within the claimed function, but it still calls for least-privilege control.

Supply chainLow risk

The source is a GitHub repository and is flagged as `open-source`, with strong community adoption (64.7k stars), all of which are meaningful risk-reducing signals. Although the license is undeclared, maintenance status is unknown, and the repository appears to be a skill collection rather than a dedicated product repo, the provided material shows no clear malicious, deceptive, or unauditable red flags.

Recommendations

Only connect to `https://rube.app/mcp` and authorize a Pingdom account after confirming you trust Rube/Composio and their data handling practices.
Grant only the minimum necessary Pingdom permissions, and prefer testing with a low-privilege or non-production account first.
Review the actual tool schemas and parameters returned by `RUBE_SEARCH_TOOLS` before execution to avoid unintended remote actions.
Check the third-party services' privacy, logging, and session-management practices, and revoke unused connections regularly.

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 "pingdom-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/pingdom-automation/SKILL.md
2. Save it as ~/.claude/skills/pingdom-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Radar tasks and workflows through Rube MCP integrations.

ComposioGet→

$ loading_