What is loomio-automation?

A skill that automates Loomio operations via Composio's Loomio toolkit using Rube MCP, anchored by tool discovery first.

What prerequisites are required?

Rube MCP connection, a Loomio connection active with toolkit loomio, and the ability to call RUBE_SEARCH_TOOLS to fetch current schemas.

Is memory required in execute calls?

Yes. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty, to preserve workflow state.

loomio-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Loomio Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/loomio

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Loomio tasks through Composio's Loomio toolkit via Rube MCP. It relies on discovering current tool schemas before execution and requires an active Loomio connection.

How This Skill Works

Technically, you first call RUBE_SEARCH_TOOLS to fetch Loomio tool slugs and input schemas. Then you verify the Loomio connection with RUBE_MANAGE_CONNECTIONS and execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, providing the required arguments and a memory object.

When to Use It

Orchestrate Loomio tasks across projects by discovering current tool schemas and executing the appropriate tool slug.
Trigger Loomio actions automatically in response to external events while ensuring the Loomio connection is ACTIVE.
Integrate Loomio steps into larger Composio workflows by sequencing discovery, connection checks, and multi-tool execution.
Reuse session IDs within a workflow to maintain state and continuity across Loomio operations.
Perform bulk Loomio operations by executing multiple tools in a single session via RUBE_MULTI_EXECUTE_TOOL.

Quick Start

Step 1: Verify RUBE MCP is configured and RUBE_SEARCH_TOOLS responds.
Step 2: Discover Loomio tool slugs and schemas with RUBE_SEARCH_TOOLS.
Step 3: Execute a selected tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch up-to-date tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the tool search results.
Include memory in each RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and only generate new IDs for new runs.

Example Use Cases

Automatically create Loomio discussions when a new ticket is opened in an external system.
Bulk update Loomio poll options based on external data feeds.
Sequence Loomio actions in a single workflow: search tools, connect, and execute.
Monitor Loomio activity and trigger follow-up tasks automatically.
Migrate Loomio tasks between projects by executing a series of tools in one session.

Frequently Asked Questions

Add this skill to your agents