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

SKILL

gleap-automation

Name: gleap-automation
Author: Composio

Automate Gleap feedback and task 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 appears to be a prompt/documentation-style wrapper with public source and strong community adoption, so its baseline risk is low. The main caveat is that real actions depend on external Rube MCP and Gleap connections, so actual data egress, permissions, and authentication are delegated to those external services.

CredentialsCaution

The material says “no API keys needed,” but it also requires an active Gleap connection via `RUBE_MANAGE_CONNECTIONS` and completion of a returned auth link. This means credentials are not absent; they are delegated to the external Rube MCP/Gleap authorization flow. This creates normal third-party OAuth/connection-token risk, but no explicit credential theft or abuse red flags are shown.

Network egressCaution

User data and operational requests are expected to be sent to the external endpoint `https://rube.app/mcp` and then handled through the Composio/Gleap toolchain. The docs do not provide detailed downstream data-flow, subprocessors, or minimization details, so this is a normal caution for declared external connectivity rather than a clear anomalous exfiltration red flag.

Code executionLow risk

The system flags it as `prompt-only`; the material only describes steps for invoking external MCP tools and does not show local process spawning, script execution, or requests for system-level execution privileges.

Data accessCaution

The skill docs do not claim direct local file read/write, but its purpose is to “Automate Gleap operations” and it performs queries, bulk operations, and workflows against Gleap resources through an external connection. Data access scope depends on the connected Gleap account permissions, implying normal remote business-data access, with no evidence of excessive local authorization beyond the stated purpose.

Supply chainLow risk

The source is a GitHub open-source repository, and the system marks it as `open-source` with high community adoption (64.7k stars), which are strong risk-reducing signals. Although the license is unspecified and maintenance status is unknown, and the skill depends on external Rube/Composio services, the available material does not show closed-source delivery, untrusted origin, or obvious injection-style red flags.

Recommendations

Before enabling it, verify the privacy policies, data handling scope, and log retention practices of `rube.app/mcp`, Composio, and Gleap.
Use a least-privilege Gleap account or minimal OAuth scopes, avoiding access unrelated to the intended automation tasks.
Test in a non-production project first to validate the tool list returned by `RUBE_SEARCH_TOOLS` and the actual execution boundaries.
Log and audit critical actions initiated through Rube/Composio, especially for bulk execution and remote workbench scenarios.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Gleap Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/gleap

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["gleap"]
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 Gleap-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `gleap`
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 Agiled clients, projects, and workflows through Rube MCP.

ComposioGet→

$ loading_