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

SKILL

loomio-automation

Name: loomio-automation
Author: Composio

Automate Loomio collaboration workflows and discussion tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source, prompt-only wrapper with no declared local code execution, environment secrets, or direct built-in endpoints, so the overall risk is low. The main consideration is that it directs users to connect a third-party Rube MCP server and authorize Loomio access, which introduces normal external-service and third-party data handling considerations.

CredentialsCaution

The material states there are no local API keys or environment variables, but it requires an active Loomio connection via `RUBE_MANAGE_CONNECTIONS` and an auth link, implying third-party managed connection credentials. No explicit credential-abuse red flags are shown, but this should be treated as normal third-party OAuth/connector exposure.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to execute Loomio tool calls; user inputs and Loomio operation data may therefore transit through that third-party service. This egress is consistent with the stated functionality and is a normal integration behavior rather than a standalone high-risk red flag.

Code executionLow risk

Based on the objective checks, this is a prompt-only skill, and the material does not declare local script execution, process spawning, shell access, or system-level permission requests. Its role is to guide use of existing MCP tools rather than execute code by itself.

Data accessCaution

It does not claim local file reads or access to sensitive host directories, but once Loomio is connected, related discussion/group/workflow data may be accessed or modified within the toolkit’s capabilities. The material does not show overbroad access beyond Loomio automation, but the connected account should still be scoped minimally.

Supply chainLow risk

The source is an open GitHub repository with strong community signals (64.7k stars), which supports auditability and lowers risk; the visible content looks more like skill documentation than an executable binary. The missing license declaration and unknown maintenance status are worth noting, but without other red flags they do not justify a high-risk rating.

Recommendations

Only connect to `https://rube.app/mcp` if you trust Rube/Composio as a third-party processor, and review its privacy and data retention terms.
Authorize Loomio with a least-privilege account or a test workspace to avoid exposing highly sensitive organizational data.
Before use, verify the actual Rube tools and parameter schemas exposed to the model so actions stay within expected scope.
Prefer pinning and reviewing the exact skill version/commit; reassess if future revisions add executable dependencies or closed-source components.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

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

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

ComposioGet→

$ loading_