home / skills / composiohq / awesome-claude-skills / benzinga-automation

benzinga-automation skill

safe

/benzinga-automation

This skill automates Benzinga operations via Rube MCP, discovering current tool schemas before executing workflows to ensure up-to-date integrations.

npx playbooks add skill composiohq/awesome-claude-skills --skill benzinga-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: benzinga-automation
description: "Automate Benzinga tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Benzinga Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

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

Overview

This skill automates Benzinga tasks by orchestrating Composio’s Benzinga toolkit through Rube MCP. It guides tool discovery, connection management, and executing toolkit operations reliably. The workflow emphasizes live schema discovery and session-driven execution to avoid brittle automation.

How this skill works

The skill queries the MCP registry with RUBE_SEARCH_TOOLS to retrieve current tool slugs and input schemas, then verifies an active Benzinga connection via RUBE_MANAGE_CONNECTIONS. It executes toolkit actions using RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) with schema-compliant arguments and a session-specific context. Responses and pagination tokens are handled to ensure full results.

When to use it

Automate Benzinga data pulls, alerts, or publishing tasks
Run repeatable Benzinga workflows that must adapt to changing tool schemas
Orchestrate bulk operations or remote workbench jobs against Benzinga
Integrate Benzinga actions into larger multi-tool agent workflows
Test or validate Benzinga tool availability and schemas before production runs

Best practices

Always call RUBE_SEARCH_TOOLS first — tool schemas and slugs can change frequently
Verify Benzinga connection status with RUBE_MANAGE_CONNECTIONS and complete any required auth flow until status is ACTIVE
Pass exact fields and types returned by search results; do not hardcode argument names
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls (can be empty) to maintain expected payload shape
Reuse session_id within a workflow; create new sessions for distinct runs and handle pagination tokens

Example use cases

Discover and call Benzinga tools to fetch breaking news or market alerts for downstream processing
Automate scheduled Benzinga content publishing using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH
Bulk ingest multiple Benzinga data points into a data pipeline while respecting pagination and schema constraints
Validate and refresh Benzinga connection status as part of a pre-run checklist in an automated agent

FAQ

What is the first call I must make before executing anything?

Always run RUBE_SEARCH_TOOLS to fetch the current tool list and input schemas before using any tool slugs or arguments.

What if the Benzinga connection is not ACTIVE?

Call RUBE_MANAGE_CONNECTIONS, follow the returned auth link to complete setup, and confirm the connection shows ACTIVE before executing workflows.

Can I hardcode tool slugs and field names?

No. Tool slugs and schemas can change. Use RUBE_SEARCH_TOOLS to obtain the authoritative schema and slug for each run.