$ ~/registry/skill/composiohq-composio-skills-beaconstac-automation

SKILL

beaconstac-automation

Name: beaconstac-automation
Author: Composio

Automate Beaconstac tasks through Rube MCP to streamline QR and marketing workflows.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill appears to be prompt/documentation-only and does not itself declare local execution, file access, or direct secret requirements. Given the open-source source and strong community adoption, overall risk is low; however, its intended use relies on external Rube MCP/Composio services for Beaconstac operations, so users should pay attention to connection scope and data flows.

CredentialsCaution

The material states the skill itself needs no API key, but it requires an active `beaconstac` connection via `RUBE_MANAGE_CONNECTIONS` and directs the user to complete an external auth flow. This means credentials likely reside in the Rube/Composio-to-Beaconstac connection layer; the skill does not explicitly collect secrets itself, but normal third-party account-authorization exposure remains.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and references `composio.dev` docs; searches, connection management, and tool execution would likely send user inputs and Beaconstac operation data to those declared third-party services. The endpoints are known and relevant to the stated function, so this is standard egress rather than a red-flag pattern, but data does leave the local environment.

Code executionLow risk

Based on the provided material, this is a skill/readme that instructs how to call external MCP tools; it does not include executable scripts, install commands, or a requirement to spawn local processes. The described execution capability belongs to the external Rube MCP tooling rather than direct local code-execution privileges requested by the skill itself.

Data accessCaution

The skill’s purpose is to 'Automate Beaconstac operations' and it uses discovered tools to query or modify Beaconstac resources; the exact data scope is not enumerated here and depends on runtime tool schemas and granted permissions. There is no stated local filesystem access, but normal business-level read/write access to Beaconstac account data and objects should be assumed.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (~64.9k stars), which are meaningful risk-reducing signals. What is shown here is skill documentation text rather than a closed-source binary; while the license is undeclared and maintenance status is unknown, the provided material does not show suspicious injection, abandonment indicators, or unrelated dependency red flags.

Recommendations

Before connecting to `rube.app/mcp`, confirm your organization allows Beaconstac-related data to be processed via Composio/Rube and review their privacy and retention policies.
Grant only the minimum Beaconstac permissions required, and regularly review active connections and authorization scope via `RUBE_MANAGE_CONNECTIONS`.
Inspect the tool schemas returned by `RUBE_SEARCH_TOOLS` before execution to ensure they will not trigger unexpected data reads or bulk changes.
Validate the automation flow in a test environment or with a low-privilege account before using it on production data.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "beaconstac-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/beaconstac-automation/SKILL.md
2. Save it as ~/.claude/skills/beaconstac-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Beaconstac 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_CONNECTIONS with toolkit beaconstac
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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit beaconstac
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_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 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

Automate Autom workflows via Rube MCP while checking current tool schemas first.

ComposioGet→

$ loading_