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

SKILL

loyverse-automation

Name: loyverse-automation
Author: Composio

Automate Loyverse operations and data workflows 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 is an open-source, prompt-only instruction set from a relatively trusted source, with no direct local secret requirement or local code execution, so overall risk is low. The main caution is that actual data access and network egress occur through the external Rube MCP and the linked Loyverse account.

CredentialsCaution

The material says “no API keys needed,” but it requires an active Loyverse connection via `RUBE_MANAGE_CONNECTIONS` and completing a returned auth link, which implies third-party account credentials or OAuth authorization. The skill itself does not collect local secrets, but once connected, the MCP tools may act with the linked account's permissions.

Network egressCaution

The README explicitly instructs adding the remote MCP endpoint `https://rube.app/mcp` and executing operations through Composio's Loyverse toolkit, so user inputs, session IDs, tool arguments, and results may flow to external services via Rube/Composio. No hidden or unrelated exfiltration is described, but there is a clear outbound network path.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no auditable local scripts, install commands, or direct host-side execution logic. It guides the use of MCP tools, but the skill itself does not declare any need to spawn local processes or run system commands.

Data accessCaution

The skill is intended to automate Loyverse operations, which implies access to or modification of Loyverse business data once the account is connected; the docs also mention session, memory, pagination, and bulk operations. No local filesystem access is requested, but it should be treated as having practical read/write capability over the connected remote business data.

Supply chainLow risk

There is strong positive evidence: the source is an open GitHub repository and part of the highly adopted `awesome-claude-skills` collection (64.7k stars). The current material is primarily documentation rather than a closed-source binary; although the license and maintenance status are unspecified, that alone is not enough to raise it to high risk without other red flags.

Recommendations

Only connect `rube.app/mcp` from a trusted client, and review its privacy policy, logging retention, and data-handling scope first.
Use the minimum necessary permissions for the Loyverse connection, and regularly review/revoke unused authorizations.
Before production use, test with a non-production account and inspect the actual tools returned by `RUBE_SEARCH_TOOLS` to ensure no unintended write operations are available.
Avoid placing unrelated sensitive data in tool arguments, session fields, or memory.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Loyverse Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/loyverse

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["loyverse"]
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 Loyverse-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `loyverse`
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 Livesession workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_