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

agent tool_use skill risk: medium

Agentql Automation via Rube MCP

Instructs on automating Agentql operations through Composio's Agentql toolkit via Rube MCP, including prerequisites, setup steps, tool discovery with RUBE_SEARCH_TOOLS, connection…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["agentql"]
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 Agentql-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `agentql` |
| 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

specific Agentql task description for tool search

e.g. Agentql operations

session_id

existing workflow session identifier

tool_slug REQUIRED

discovered tool identifier from search

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • active agentql connection via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • use_case query
  • session_id
  • tool_slug
  • arguments

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

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 agentql
  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 call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • reuse session IDs within workflow

EXAMPLES

Includes multiple example RUBE tool calls (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) with sample arguments and a quick-reference table.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Agentql connection via RUBE_MANAGE_CONNECTIONS with toolkit agentql
Missing context
  • Target client or environment where the MCP server is configured
  • Example of a concrete Agentql task to illustrate end-to-end usage
Ambiguities
  • Tool call examples use pseudo-syntax rather than exact required format or parameter types.
  • Placeholder 'your specific Agentql task' is not further defined.

QUALITY

OVERALL
0.75
CLARITY
0.78
SPECIFICITY
0.82
REUSABILITY
0.68
COMPLETENESS
0.74

IMPROVEMENT SUGGESTIONS

  • Replace the generic placeholder with a concrete example task and full parameter values.
  • Specify the exact JSON or function-call syntax expected for RUBE_* calls instead of markdown blocks.

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