home / skills / composiohq / awesome-claude-skills / loomio-automation

loomio-automation skill

safe

/loomio-automation

This skill helps you automate Loomio tasks via Rube MCP by discovering current tool schemas before executing workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill loomio-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.8 KB

---
name: loomio-automation
description: "Automate Loomio tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Loomio Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/loomio](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `loomio`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Loomio tasks through Composio’s Loomio toolkit using the Rube MCP gateway. It provides a repeatable pattern to discover tools, verify Loomio connections, and execute toolkit operations reliably. The skill emphasizes always discovering current tool schemas first to avoid runtime errors.

How this skill works

First call RUBE_SEARCH_TOOLS to fetch available Loomio tool slugs, input schemas, and recommended execution plans. Confirm an active Loomio connection via RUBE_MANAGE_CONNECTIONS, then run toolkit actions with RUBE_MULTI_EXECUTE_TOOL (including a memory object and session ID). For bulk operations, use RUBE_REMOTE_WORKBENCH and run_composio_tool() as recommended.

When to use it

Automating Loomio group, proposal, or vote management tasks from an external agent
Building repeatable workflows that call Loomio toolkit operations programmatically
Integrating Loomio actions into multi-step agent processes that require tool discovery and connection checks
Running bulk operations across many Loomio groups or proposals
When you need robust schema-aware calls to avoid breaking changes in the Loomio toolkit

Best practices

Always call RUBE_SEARCH_TOOLS first to get the current tool slugs and exact input schemas
Verify Loomio connection status with RUBE_MANAGE_CONNECTIONS and complete any required auth flow before executing tools
Include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls and reuse session IDs within a workflow
Respect exact field names and types from the returned schema; do not hardcode arguments
Handle pagination tokens and iterate until responses are complete for list operations

Example use cases

Create a Loomio proposal from a summary generated by an agent, using the discovered create-proposal tool schema
Close or archive proposals in bulk for governance housekeeping via RUBE_REMOTE_WORKBENCH
Fetch group membership and send targeted updates, ensuring paginated member lists are fully retrieved
Trigger votes and collect results programmatically as part of a decision workflow
Automate connection setup checks and surface actionable auth links if the Loomio connection is not ACTIVE

FAQ

Do I need API keys to use Rube MCP for Loomio?

No API keys are required for the Rube MCP endpoint; add the MCP server URL in your client configuration and use the Rube MCP calls.

What if tool schemas change after I hardcode arguments?

Always call RUBE_SEARCH_TOOLS before executing. If schemas change, update arguments to match the returned schema to avoid errors.