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

SKILL

lexoffice-automation

Name: lexoffice-automation
Author: Composio

Automate Lexoffice invoices, contacts, and finance 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 primarily a prompt/instruction wrapper with no local secrets required and no direct local code execution shown in the material. However, it relies on external Rube MCP/Composio and a Lexoffice connection, so business data is expected to be sent to remote tooling; overall this is caution rather than high risk. The GitHub open-source source and strong community adoption materially reduce supply-chain concern, though license and maintenance status are not clearly stated here.

CredentialsCaution

The material says the skill itself needs 'no API keys', but it still requires an active Lexoffice connection established via RUBE_MANAGE_CONNECTIONS and an external auth link. So while there is no explicit local env var secret, third-party account authorization tokens are still involved, creating normal credential-scope and misuse considerations.

Network egressCaution

The README explicitly instructs users to add the remote MCP endpoint `https://rube.app/mcp` and execute actions through Composio's Lexoffice toolkit. Queries, connection metadata, tool arguments, and likely Lexoffice business data may be sent through that remote service. No unrelated or clearly suspicious endpoint is shown, but external data egress is inherent here.

Code executionLow risk

The system marks this as prompt-only, and the material only describes a tool-calling workflow. It does not show downloads, installation steps, shell/script execution, or local process spawning; no direct local code execution capability is evidenced here.

Data accessCaution

The stated purpose is to automate Lexoffice operations, and the described capabilities include tool discovery, connection management, multi-execution, and remote workbench actions, implying access to and processing of Lexoffice business records/documents. The material does not show direct local file access or excessive system permissions, but the access scope to third-party SaaS business data should be reviewed under least-privilege principles.

Supply chainLow risk

The source is a GitHub open-source repository, and the system marks it as open-source with strong community trust (64.7k), which is meaningful positive evidence. The skill text itself is auditable, with no obfuscated installer, closed binary, or obvious injection red flag. Still, this appears to be a skills collection rather than the full implementation of this integration, and the license/maintenance status are unclear, so upstream Rube/Composio components should still be verified.

Recommendations

Connect to `rube.app/mcp` only when needed, and review how Composio/Rube handle and store Lexoffice data.
Grant the minimum necessary Lexoffice permissions and prefer testing with a low-sensitivity account first.
Before production use, document and review the authorization scope, session lifecycle, and revocation path exposed by RUBE_MANAGE_CONNECTIONS.
Further verify the source code, license, and recent maintenance status of the upstream Rube MCP and Composio Lexoffice toolkit.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Lexoffice Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/lexoffice

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["lexoffice"]
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 Lexoffice-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `lexoffice`
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 Documint document generation and processing tasks through Rube MCP.

ComposioGet→

$ loading_