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

agent tool_use skill risk: medium

Currents API Automation via Rube MCP

Instructs the model to automate Currents API operations through Composio's Rube MCP by first calling RUBE_SEARCH_TOOLS, managing connections with RUBE_MANAGE_CONNECTIONS, and execu…

  • Human review
  • External action: high

SKILL 1 file

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

Automate Currents API operations through Composio's Currents API toolkit via Rube MCP.

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["currents_api"]
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 Currents API-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `currents_api` |
| 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)*

REQUIRED CONTEXT

  • Rube MCP connection
  • active currents_api toolkit connection

OPTIONAL CONTEXT

  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

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 currents_api
  5. If connection is not ACTIVE, follow the returned auth link to complete setup
  6. Confirm connection status shows ACTIVE before running any workflows
  7. Always discover available tools before executing workflows
  8. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_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
  • use exact schemas from search results
  • include memory parameter even if empty

SUCCESS CRITERIA

  • Always search first
  • Verify active connection before execution
  • Use schema-compliant arguments
  • Follow core workflow pattern

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Executing without active connection
  • Ignoring schema from search results
  • Forgetting memory parameter

CAVEATS

Dependencies
  • Rube MCP connected
  • Active Currents API connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target client or environment where Rube MCP is configured
Ambiguities
  • Placeholder "your specific Currents API task" is not further defined or exemplified.
  • Session ID generation and reuse rules are stated but lack concrete examples of valid IDs.

QUALITY

OVERALL
0.76
CLARITY
0.78
SPECIFICITY
0.82
REUSABILITY
0.75
COMPLETENESS
0.72

IMPROVEMENT SUGGESTIONS

  • Replace free-form placeholders with explicit bracketed variables such as {{task_description}} and {{session_id}}.
  • Add one concrete end-to-end example call sequence with sample values.

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