pingdom-automation
Automate Pingdom tasks via Rube MCP (Composio). Always search tools first for current schemas.
Best use case
pingdom-automation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Automate Pingdom tasks via Rube MCP (Composio). Always search tools first for current schemas.
Teams using pingdom-automation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/pingdom-automation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How pingdom-automation Compares
| Feature / Agent | pingdom-automation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Automate Pingdom tasks via Rube MCP (Composio). Always search tools first for current schemas.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Pingdom Automation via Rube MCP
Automate Pingdom operations through Composio's Pingdom toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/pingdom](https://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.
1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pingdom`
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: "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](https://composio.dev)*Related Skills
vercel-automation
Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.
typless-automation
Automate Typless tasks via Rube MCP (Composio). Always search tools first for current schemas.
shopify-automation
Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas.
pdfless-automation
Automate Pdfless tasks via Rube MCP (Composio). Always search tools first for current schemas.
ocr-web-service-automation
Automate OCR Web Service tasks via Rube MCP (Composio). Always search tools first for current schemas.
lessonspace-automation
Automate Lessonspace tasks via Rube MCP (Composio). Always search tools first for current schemas.
go-to-webinar-automation
Automate GoToWebinar tasks via Rube MCP (Composio). Always search tools first for current schemas.
browserless-automation
Automate Browserless tasks via Rube MCP (Composio). Always search tools first for current schemas.
backendless-automation
Automate Backendless tasks via Rube MCP (Composio). Always search tools first for current schemas.
securitytrails-automation
Automate Securitytrails tasks via Rube MCP (Composio). Always search tools first for current schemas.
onesignal-user-auth-automation
Automate Onesignal User Auth tasks via Rube MCP (Composio). Always search tools first for current schemas.
hackernews-automation
Automate Hackernews tasks via Rube MCP (Composio). Always search tools first for current schemas.