dock-certs-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/dock-certs-automation --openclawDock Certs Automation via Rube MCP
Automate Dock Certs operations through Composio's Dock Certs toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/dock_certs
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Dock Certs connection via
RUBE_MANAGE_CONNECTIONSwith toolkitdock_certs - 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 toolkitdock_certs - 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: "Dock Certs 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 Dock Certs task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["dock_certs"]
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 Dock Certs-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit dock_certs |
| 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/dock-certs-automation/SKILL.mdView on GitHub Overview
Automate Dock Certs operations through Composio's Dock Certs toolkit via Rube MCP. It orchestrates tool discovery, connection setup, and execution using current tool schemas, ensuring repeatable, error-checked workflows. Always call RUBE_SEARCH_TOOLS first to fetch up-to-date tool slugs and input schemas.
How This Skill Works
The skill first performs RUBE_SEARCH_TOOLS to fetch available Dock Certs tools and their input schemas. It then ensures an ACTIVE Dock Certs connection via RUBE_MANAGE_CONNECTIONS. Finally, it executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments and a memory payload for session continuity.
When to Use It
- When you need to automate recurring Dock Certs tasks using the latest tool schemas.
- When tool schemas change and you must fetch current slugs and inputs before running workflows.
- When setting up a new Dock Certs connection and validating that the connection status is ACTIVE.
- When orchestrating multi-tool workflows that require session management across steps.
- When performing bulk or parallel operations using remote benches or multi-tool execution.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and ensure RUBE_SEARCH_TOOLS responds.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'dock_certs' and activate the connection.
- Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and memory payload to run a task.
Best Practices
- Always run RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
- Use exact field names and types from the search results; do not hardcode slugs or args.
- Always include a memory payload in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a single workflow and generate new ones for separate workflows.
Example Use Cases
- Discover the renew_certificate tool, establish an ACTIVE dock_certs connection, and execute renewal for a batch of certs.
- Fetch statuses for multiple Dock Certs via the appropriate check_status tool found through RUBE_SEARCH_TOOLS, then act on results.
- Run a bulk renewal by issuing multiple tool calls through RUBE_MULTI_EXECUTE_TOOL using the discovered tool slugs.
- Perform a bulk revoke and reissue cycle using RUBE_REMOTE_WORKBENCH run_composio_tool across several certs.
- Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before building a workflow.
