statuscake-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/statuscake-automation --openclawStatuscake Automation via Rube MCP
Automate Statuscake operations through Composio's Statuscake toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/statuscake
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Statuscake connection via
RUBE_MANAGE_CONNECTIONSwith toolkitstatuscake - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitstatuscake - 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: "Statuscake 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 Statuscake task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["statuscake"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Statuscake-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit statuscake |
| 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/statuscake-automation/SKILL.mdView on GitHub Overview
This skill automates Statuscake operations through Composio's Rube MCP and the Statuscake toolkit. It emphasizes discovering current tool schemas before execution to stay aligned with API changes, then connects to Statuscake and runs automated tasks.
How This Skill Works
First, fetch available Statuscake tool schemas using RUBE_SEARCH_TOOLS. Then verify an ACTIVE Statuscake connection with RUBE_MANAGE_CONNECTIONS. Finally execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying memory and the relevant session_id, using the exact field names from the discovered schema to avoid errors.
When to Use It
- Automate routine Statuscake checks after deployments or CI runs
- Orchestrate multiple Statuscake tasks in a single workflow without hardcoding slugs
- Set up a new Statuscake integration or revalidate an existing one programmatically
- Respond to incidents by triggering tests with freshly discovered tool schemas
- Audit and reproduce Statuscake workflows with up-to-date tool schemas before each run
Quick Start
- Step 1: Discover available Statuscake tools with RUBE_SEARCH_TOOLS
- Step 2: Ensure the toolkit 'statuscake' connection is ACTIVE via RUBE_MANAGE_CONNECTIONS
- Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS first to retrieve current tool schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from the search results; do not hardcode slugs
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and handle pagination as needed
Example Use Cases
- After a new deployment, discover Statuscake tools and run an uptime check using the returned tool slug
- Automate a sequence of Statuscake tasks by iterating through tool slugs from the search results with appropriate arguments
- Reconnect a previously inactive Statuscake integration by following the auth flow and rechecking ACTIVE status
- Bulk-run sanity tests on multiple Statuscake jobs by discovering tools and executing them in a single session
- Audit a workflow by re-fetching tool schemas before execution to prevent breaking changes
