What do I need to use Triggercmd automation with Rube MCP?

RUBE_SEARCH_TOOLS availability, a connected Triggercmd toolkit via RUBE_MANAGE_CONNECTIONS, and an ACTIVE connection.

Do tool slugs or arguments change often?

Yes; always call RUBE_SEARCH_TOOLS to fetch current schemas before executing.

Is an API key required?

No API keys needed; add the MCP server endpoint as described.

triggercmd-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/triggercmd-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Triggercmd Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/triggercmd

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["triggercmd"]
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 Triggercmd-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `triggercmd`
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/triggercmd-automation/SKILL.mdView on GitHub

Overview

Automate Triggercmd operations through Composio's Triggercmd toolkit using Rube MCP. This skill relies on discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing a Triggercmd connection with RUBE_MANAGE_CONNECTIONS, and executing tools via RUBE_MULTI_EXECUTE_TOOL.

How This Skill Works

It starts by discovering available Triggercmd tools with RUBE_SEARCH_TOOLS to obtain slugs and input schemas. Then it checks and establishes the Triggercmd connection using RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id.

When to Use It

You need to run a Triggercmd operation from an automated workflow.
Tool schemas have changed, so you must fetch current slugs and fields instead of hardcoding.
You need to verify that the Triggercmd connection is ACTIVE before running tools.
You want to execute multiple Triggercmd tools in a single workflow using multi-execute.
You want to reuse a session ID across steps to maintain context in a workflow.

Quick Start

Step 1: Ensure Rube MCP is connected and call RUBE_SEARCH_TOOLS to fetch current tool schemas.
Step 2: Pick a TOOL_SLUG from the search results and run RUBE_MANAGE_CONNECTIONS to ensure ACTIVE.
Step 3: Execute the tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch updated tool schemas.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
Use the exact field names and types from the search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty).
Reuse session IDs where appropriate and handle pagination tokens from search results.

Example Use Cases

Automate a Wake-on-LAN Triggercmd task by discovering tools, connecting, and executing the 'wake' tool.
Check device status across a fleet by discovering the 'status' tool, connecting, and running it.
Restart a device via Triggercmd in a scheduled workflow with session reuse.
Run multiple Triggercmd tasks in a batch using RUBE_MULTI_EXECUTE_TOOL.
Validate tool schemas during a new workflow by always calling RUBE_SEARCH_TOOLS first.

Frequently Asked Questions

Add this skill to your agents