Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Certifier Rube MCP Automation Workflow

agent tool_use skill risk: medium

Certifier Rube MCP Automation Workflow

Instructs the model to automate Certifier operations through Composio's toolkit via Rube MCP by first calling RUBE_SEARCH_TOOLS, verifying connections with RUBE_MANAGE_CONNECTIONS,…

  • External action: medium

SKILL 1 file

SKILL.md
---
name: certifier-automation
description: "Automate Certifier tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Certifier Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/certifier](https://composio.dev/toolkits/certifier)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Certifier connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `certifier`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `certifier`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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 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](https://composio.dev)*

INPUTS

use_case REQUIRED

description of the Certifier task to perform

e.g. your specific Certifier task

session_id

existing workflow session identifier

e.g. existing_session_id

REQUIRED CONTEXT

  • Rube MCP connection
  • active Certifier toolkit connection

OPTIONAL CONTEXT

  • specific use case for tool search
  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit certifier
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify active connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Verify Rube MCP connection
  • Establish ACTIVE Certifier connection
  • Discover tools via RUBE_SEARCH_TOOLS before execution
  • Execute only schema-compliant tool calls

FAILURE MODES

  • Hardcoding tool slugs or arguments
  • Skipping connection status check
  • Omitting memory parameter in execute calls
  • Ignoring pagination tokens

CAVEATS

Dependencies
  • RUBE_SEARCH_TOOLS available
  • Active Certifier connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target client or environment (e.g., Claude Desktop, Cursor) for MCP configuration
  • Concrete example of a full successful workflow with real tool slugs and arguments
  • Definition of success criteria or expected response shapes
Ambiguities
  • The exact JSON structure and parameter names for RUBE_* calls are shown inconsistently between prose and code blocks.
  • Placeholder 'your specific Certifier task' is never replaced with a concrete example.
  • 'generate_id: true' syntax is not explained or shown in valid JSON.

QUALITY

OVERALL
0.71
CLARITY
0.78
SPECIFICITY
0.72
REUSABILITY
0.68
COMPLETENESS
0.65

IMPROVEMENT SUGGESTIONS

  • Replace the placeholder use_case with at least one fully-worked example that includes the actual tool_slug returned by search.
  • Add a minimal valid JSON example for each RUBE_* call instead of pseudo-syntax.
  • Specify that all function calls must be emitted as properly formatted JSON objects.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT