beaconstac-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/beaconstac-automation --openclawBeaconstac Automation via Rube MCP
Automate Beaconstac operations through Composio's Beaconstac toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/beaconstac
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Beaconstac connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbeaconstac - 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 toolkitbeaconstac - 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: "Beaconstac 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 Beaconstac task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["beaconstac"]
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 Beaconstac-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit beaconstac |
| 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/beaconstac-automation/SKILL.mdView on GitHub Overview
This skill automates Beaconstac operations through Composio's Beaconstac toolkit via Rube MCP. It emphasizes discovering current tool schemas first, ensuring an ACTIVE Beaconstac connection, and then executing the selected tools to streamline campaigns and repeatable workflows.
How This Skill Works
First, it uses RUBE_SEARCH_TOOLS to fetch up-to-date Beaconstac tool schemas for a given use case. Next, it verifies the connection with RUBE_MANAGE_CONNECTIONS and a selected session, then executes the tool(s) with RUBE_MULTI_EXECUTE_TOOL, including a memory payload. This pattern lets you reuse sessions and consistently apply schema-compliant arguments.
When to Use It
- Automate a sequence of Beaconstac tasks by discovering tools first.
- Establish a Beaconstac connection via Rube MCP and validate ACTIVE status before running workflows.
- Execute a discovered Beaconstac tool with correct arguments derived from tool schemas.
- Perform bulk Beaconstac actions using RUBE_REMOTE_WORKBENCH with run_composio_tool().
- Maintain session continuity across a multi-tool workflow to preserve context.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Beaconstac operations"}] session: {generate_id: true}.
- Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["beaconstac"] session_id: "your_session_id" and verify ACTIVE.
- Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, memory: {} and session_id: "your_session_id".
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the discovery results; avoid hardcoding.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and handle pagination tokens if present.
Example Use Cases
- Discover Beaconstac operation tools with RUBE_SEARCH_TOOLS for a specific use case, then execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with derived arguments.
- Establish and confirm an ACTIVE Beaconstac connection via RUBE_MANAGE_CONNECTIONS before running any workflow.
- Run a Beaconstac tool using arguments that were returned by the tool schemas in the discovery step.
- Bulk automate multiple Beaconstac actions using RUBE_REMOTE_WORKBENCH and run_composio_tool().
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to review schemaRef and keep tooling up to date.
