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

SKILL

beamer-automation

Name: beamer-automation
Author: Composio

Automate Beamer workflows to streamline updates, publishing, and team coordination.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is itself an open-source prompt/documentation artifact with no direct local secret requirement and no executable install steps. However, it is designed around external Rube MCP and Beamer connections, so real usage will send task-related data to third-party services; overall this is low-to-moderate risk and warrants attention to external service boundaries.

CredentialsCaution

The material says 'No API keys needed', but it also requires an active Beamer connection via `RUBE_MANAGE_CONNECTIONS` and an auth-link flow, indicating credentials are likely handled by Rube/Beamer or via an OAuth-like mechanism. The skill does not directly request secrets, but it depends on third-party account authorization, so the granted scope should be reviewed.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using the Composio/Beamer toolchain. During search, connection management, and tool execution, task content and arguments will be sent to those declared external services. This is normal egress for an MCP-based tool; no unrelated or hidden endpoints are stated, but operational data should be assumed to leave the local environment.

Code executionLow risk

Based on the provided material, this is a prompt/workflow-documentation style skill with no local scripts, install commands, or steps requiring code execution on the host. The referenced `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH` act through a remote MCP toolchain rather than directly granting this skill local code-execution capability.

Data accessCaution

The skill does not claim direct access to local files or system resources, but it is intended to 'Automate Beamer operations' and executes discovered tools through an external connection. The actual data scope therefore depends on the Beamer account permissions and the discovered tool schemas. Since no least-privilege boundary is defined here, it should be used only with necessary accounts and minimal data scope.

Supply chainLow risk

The source is an open GitHub repository with high community adoption (64.7k stars), both strong risk-reducing factors. The audited artifact itself is essentially a README/skill description and is inspectable; while the license is unspecified, maintenance status is unknown, and real operation depends on external Rube/Composio services, the current material does not show a concrete supply-chain red flag.

Recommendations

Enable it only if you trust the Rube/Composio and Beamer integration, and review the authorization scope carefully.
Use a least-privilege Beamer account and avoid granting unnecessary data or admin permissions.
Before sending sensitive business content, inspect the tools and parameter meanings returned by `RUBE_SEARCH_TOOLS`.
Validate workflows in a test environment first instead of automating production data directly through a third-party MCP.

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 "beamer-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/beamer-automation/SKILL.md
2. Save it as ~/.claude/skills/beamer-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Beamer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/beamer

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["beamer"]
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 Beamer-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `beamer`
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 Beaconstac tasks through Rube MCP to streamline QR and marketing workflows.

ComposioGet→

$ loading_