sslmate-cert-spotter-api-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/sslmate-cert-spotter-api-automation --openclawSslmate Cert Spotter API Automation via Rube MCP
Automate Sslmate Cert Spotter API operations through Composio's Sslmate Cert Spotter API toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/sslmate_cert_spotter_api
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Sslmate Cert Spotter API connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsslmate_cert_spotter_api - 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 toolkitsslmate_cert_spotter_api - 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: "Sslmate Cert Spotter API 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 Sslmate Cert Spotter API task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["sslmate_cert_spotter_api"]
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 Sslmate Cert Spotter API-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit sslmate_cert_spotter_api |
| 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/sslmate-cert-spotter-api-automation/SKILL.mdView on GitHub Overview
Automate Sslmate Cert Spotter API operations through Composio's toolkit using Rube MCP. It streamlines discovery, connection, and execution of Cert Spotter tasks, ensuring you always fetch current tool schemas first. This guide covers prerequisites, setup, and best practices for reliable automation.
How This Skill Works
You start by discovering available Cert Spotter API tools and their schemas with RUBE_SEARCH_TOOLS, then establish or verify a connection via RUBE_MANAGE_CONNECTIONS for the sslmate_cert_spotter_api toolkit, and finally execute selected tools with RUBE_MULTI_EXECUTE_TOOL, providing a memory object and session context. Because tool schemas are dynamic, you must use the exact field names and types returned in the discovery results.
When to Use It
- When starting a new Cert Spotter workflow and need current tool schemas
- When validating/setting up the sslmate_cert_spotter_api connection before runs
- When discovering tools and planning an automated Cert Spotter task sequence
- When executing batch or multi-tool operations with proper memory and session handling
- When debugging automation by checking for schema or pagination issues
Quick Start
- Step 1: Configure Rube MCP as an MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
- Step 2: Call RUBE_MANAGE_CONNECTIONS for toolkit sslmate_cert_spotter_api and activate the connection
- Step 3: Discover tools with RUBE_SEARCH_TOOLS and run a tool with RUBE_MULTI_EXECUTE_TOOL using a session
Best Practices
- Always call RUBE_SEARCH_TOOLS before any run because schemas change
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from discovery results
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow; avoid creating new ones for each step
Example Use Cases
- Automate a routine Cert Spotter scan to identify expiring domains
- Bulk-check a list of domains against the API and compile a report
- Set up a new integration: connect, discover tools, and run a simple workflow
- Migrate from manual API calls to Rube MCP-based automation
- Handle paginated results when listing certificates and continue until complete