certifier-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/certifier-automation --openclawCertifier Automation via Rube MCP
Automate Certifier operations through Composio's Certifier toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/certifier
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Certifier connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcertifier - 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 toolkitcertifier - 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: "Certifier 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 Certifier task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["certifier"]
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 Certifier-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit certifier |
| 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/certifier-automation/SKILL.mdView on GitHub Overview
Certifier automation uses Composio's Rube MCP toolkit to orchestrate Certifier operations. It emphasizes discovering current tool schemas first to avoid stale slugs and incorrect arguments. This ensures reliable, schema-compliant automation of issuance, verification, or revocation workflows.
How This Skill Works
The workflow starts by discovering available Certifier tools with RUBE_SEARCH_TOOLS, which returns tool slugs, input schemas, and execution plans. Next, you check the connection via RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, you execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and the schema-compliant arguments from the discovery results. Always include memory and reuse session IDs where appropriate.
When to Use It
- You need to issue, verify, or revoke certificates by automating Certifier tool executions after discovering current schemas.
- Tool schemas may have changed; you must fetch the latest slugs and schemas before building or running a workflow.
- You must confirm that the Certifier connection is ACTIVE before any tool execution.
- You are performing batch or bulk certifier tasks that should run within a single workflow or session.
- You want to reuse a session ID to improve efficiency across multiple Certifier steps in a single automation.
Quick Start
- Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Call RUBE_SEARCH_TOOLS with a Certifier use_case to discover current tool slugs and input schemas.
- Step 3: Call RUBE_MANAGE_CONNECTIONS for toolkits: ["certifier"], then run RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and memory; ensure ACTIVE before executing.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing to get current tool slugs and schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to any tool execution.
- Use exact field names and types from the search results to ensure schema compliance.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Issue a batch of certificates by discovering tools, establishing an active Certifier connection, and executing a tool with the correct, schema-aligned arguments.
- Fetch current Certifier tool schemas and apply them to an automation workflow that performs a verification task.
- Connect the Certifier toolkit and run a renewal task within an active session to avoid authentication hiccups.
- Execute multiple certifier operations in one workflow by batching tool calls with RUBE_MULTI_EXECUTE_TOOL and maintaining memory and session state.
- Reuse a session ID across several Certifier steps in a long-running workflow to maximize efficiency and reduce setup overhead.
