$ ~/registry/skill/composiohq-composio-skills-sslmate-cert-spotter-api-automation

SKILL

sslmate-cert-spotter-api-automation

Name: sslmate-cert-spotter-api-automation
Author: Composio

Automate SSLMate Cert Spotter certificate monitoring and query workflows via Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

The material itself is an open-source prompt-style instruction set with no direct local code execution requirement or fixed egress endpoint, so overall risk is relatively low. However, actual use depends on third-party Rube MCP and external connection flows, which introduces normal caution around remote tool discovery, connection management, and external API calls.

CredentialsCaution

The page claims 'no API keys', but the README explicitly requires establishing an ACTIVE `sslmate_cert_spotter_api` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth-link flow, indicating real third-party account authorization or token handling may occur. The material does not specify where credentials are stored, their scope, or least-privilege controls.

Network egressCaution

The material requires adding `https://rube.app/mcp` as an MCP server and using Composio/Rube to search tools, manage connections, and execute remote tools, so workflow data and arguments will be sent to the stated third-party service. It may also relay requests to the Sslmate Cert Spotter API, but the documentation does not enumerate exact endpoints or data scope.

Code executionLow risk

System checks mark this as prompt-only, and the document mainly contains usage instructions. It does not describe spawning local processes, running scripts, installing dependencies, or requesting system-level execution permissions; from the material, the main exposure is remote tool invocation rather than local code execution.

Data accessCaution

The documentation does not state any need for local file I/O or broad host permissions, but user input, session identifiers, and execution parameters may be processed by a third-party platform via `RUBE_SEARCH_TOOLS`, `RUBE_MULTI_EXECUTE_TOOL`, and session/memory fields. The material provides no details on data minimization, retention, or visibility.

Supply chainLow risk

There is strong positive evidence here: the source is a GitHub open-source repository, the system marks it as open-source, and community adoption is high (~64.9k stars). The current material appears to be skill documentation rather than an executable binary. Gaps remain: the license is undeclared, maintenance status is unknown, and actual operation depends on external Rube/Composio services whose backend implementation is outside full audit scope.

Recommendations

Before enabling it, verify the actual data flow, log retention, and credential-handling model of Rube/Composio and Sslmate.
Use least-privilege accounts during authorization and connect only the Sslmate resources needed for the task.
Do not place unnecessary sensitive data in queries, memory fields, or tool arguments.
Review the toolkit documentation and authorization pages to confirm external endpoints and permission scope.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Sslmate 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_CONNECTIONS with toolkit sslmate_cert_spotter_api
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 sslmate_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_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 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

Automate Smartproxy workflows via Rube MCP for proxy search and task execution.

ComposioGet→

$ loading_