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

SKILL

lodgify-automation

Name: lodgify-automation
Author: Composio

Automate Lodgify operations through Rube MCP to streamline property management tasks.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

The skill material itself is open-source, prompt/documentation-only, and does not require local secrets or local code execution, so overall risk is relatively low. However, its real functionality depends on external Rube MCP and a Lodgify connection, which introduces normal third-party data egress and account-access exposure that should be treated with caution.

CredentialsCaution

The material says there are no local API keys, but the README explicitly requires creating an active `lodgify` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth-link flow. This indicates Lodgify/third-party credentials are involved in practice, though managed by Rube/Composio rather than entered directly in the skill. Review third-party credential handling, scope, and revocation.

Network egressCaution

The README explicitly instructs adding the remote MCP endpoint `https://rube.app/mcp` and using it for tool discovery, connection management, and execution. User inputs, session IDs, tool arguments, and potentially Lodgify business data may be relayed through this third-party service. This is a normal MCP pattern, but it conflicts with the metadata claiming no remote endpoint, so the real data flow should be verified before use.

Code executionLow risk

Based on the provided material, this is a prompt/instruction-style skill and does not include auditable local scripts, install commands, or host-level execution steps. There is no indication that it launches local processes, runs shell commands, or requests extra system privileges.

Data accessCaution

The skill is intended to 'Automate Lodgify operations' and supports executing Lodgify tools via `RUBE_MULTI_EXECUTE_TOOL`/`RUBE_REMOTE_WORKBENCH`. Once the connection is active, it may read or modify data in the connected Lodgify account. The material does not expose fine-grained permission boundaries, so least-privilege access should be enforced on the connected account.

Supply chainCaution

Positive signals include a GitHub open-source source and strong community adoption (64.7k stars), which materially reduce supply-chain risk. However, this skill appears to be more of a cataloged instruction item, while actual execution depends on externally hosted Rube MCP and Composio/Lodgify integrations; the license is unspecified and maintenance status is unknown, so ongoing verification is still warranted.

Recommendations

Verify the real remote endpoints and data flow before enabling it: confirm whether traffic goes only to `rube.app` or is further relayed to Composio/Lodgify.
Use a least-privilege Lodgify account for the connection, and ensure the OAuth/connection can be revoked, rotated, and audited.
Review the privacy policy, permission scopes, and log-retention practices for Rube MCP and the Composio Lodgify toolkit.
If used in an enterprise setting, test `RUBE_MULTI_EXECUTE_TOOL` first against non-production or sanitized data to confirm actual read/write scope.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Lodgify Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/lodgify

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["lodgify"]
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 Lodgify-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `lodgify`
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 Composio tasks via Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_