What is required to use this skill?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, and a Digicert connection must be ACTIVE using the digicert toolkit.

Should I hardcode tool slugs?

No. Always search for current tool schemas with RUBE_SEARCH_TOOLS to get updated slugs and input fields.

What if tool schemas change mid-workflow?

Re-run RUBE_SEARCH_TOOLS to fetch new schemas, update the tool slug and input fields, and continue the workflow, ensuring memory is included in RUBE_MULTI_EXECUTE_TOOL.

digicert-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/digicert-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Digicert Automation via Rube MCP

Automate Digicert operations through Composio's Digicert toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/digicert

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Digicert connection via RUBE_MANAGE_CONNECTIONS with toolkit digicert
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 digicert
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: "Digicert 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 Digicert task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["digicert"]
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 Digicert-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `digicert`
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/digicert-automation/SKILL.mdView on GitHub

Overview

This skill automates Digicert operations via Composio's Digicert toolkit through Rube MCP. It emphasizes discovering current tool schemas first, establishing an ACTIVE Digicert connection, and executing tools using RUBE_MULTI_EXECUTE_TOOL within a verified session.

How This Skill Works

Connect to Digicert with RUBE_MANAGE_CONNECTIONS, fetch the latest tool schemas using RUBE_SEARCH_TOOLS, and pick a tool slug. Then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, ensuring memory is included and the input matches the discovered schema, all within a valid session.

When to Use It

When starting a new Digicert workflow and tool schemas may change.
When you need an ACTIVE connection to Digicert before running tools.
When performing a batch or bulk Digicert operation in a single session.
When you must reuse the same session ID to maintain context across steps.
When tool results require pagination and you must fetch all pages.

Quick Start

Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS responds to fetch tool schemas.
Step 2: Call RUBE_MANAGE_CONNECTIONS with the digicert toolkit and authenticate if required; confirm ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, select a TOOL_SLUG_FROM_SEARCH, and execute via RUBE_MULTI_EXECUTE_TOOL including memory and a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to fetch current tool schemas.
Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Use exact field names and types from the search results; avoid hardcoded slugs.
Always include memory in RUBE_MULTI_EXECUTE_TOOL, even if empty.
Reuse session IDs within a workflow and handle pagination tokens properly.

Example Use Cases

Discover the issue_certificate tool slug from RUBE_SEARCH_TOOLS for a domain and CSR, connect if needed, and issue a certificate via RUBE_MULTI_EXECUTE_TOOL in a single session.
Identify the renew_certificate tool slug from the search results, run bulk renewals for multiple domains in one session, and pass a memory payload to track the batch.
Fetch the get_certificate_status tool slug, query the status of a certificate or set of certificates, and parse results within the same session.
Find the revoke_certificate tool slug and revoke an expired or compromised certificate, ensuring the connection remains ACTIVE throughout.
Audit and validate current tool schemas by running RUBE_GET_TOOL_SCHEMAS to confirm changes before any execution.

Frequently Asked Questions

Add this skill to your agents