gleap-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/gleap-automation --openclawGleap 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_CONNECTIONSwith toolkitgleap - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitgleap - 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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/gleap-automation/SKILL.mdView on GitHub Overview
gleap-automation enables automating Gleap operations through Composio's Gleap toolkit using Rube MCP. It emphasizes discovering current tool schemas before execution to avoid outdated slugs and arguments. Always verify an active Gleap connection and reuse sessions when appropriate to streamline workflows.
How This Skill Works
The skill first discovers available Gleap tools with RUBE_SEARCH_TOOLS, then selects a tool slug and required arguments from the returned schema. Next, it ensures the Gleap connection is ACTIVE via RUBE_MANAGE_CONNECTIONS and finally executes the tool with RUBE_MULTI_EXECUTE_TOOL, including memory and the session_id to maintain context.
When to Use It
- When automating recurring Gleap tasks that depend on up-to-date tool schemas
- When integrating Gleap operations into a larger Composio automation workflow
- When you need to confirm an ACTIVE Gleap connection before execution
- When you want to avoid hardcoding tool slugs by first discovering tools
- When handling multi-step Gleap tasks that require session reuse and proper memory handling
Quick Start
- Step 1: RUBE_SEARCH_TOOLS to discover available Gleap tools for your use case
- Step 2: RUBE_MANAGE_CONNECTIONS to ensure the gleap toolkit is ACTIVE
- Step 3: RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and memory, using the session_id from Step 2
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
- Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running workflows
- Use exact field names and types from the search results; avoid guessing
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow or generate new ones for new tasks
Example Use Cases
- Automate a Gleap user feedback collection workflow by discovering relevant tools and executing them in one session
- Automatically triage Gleap issues by discovering tools, validating connection, and executing a batch of tasks
- Sync Gleap task data to an external system after running a tool
- Set up a recurring Gleap task where schemas are fetched at the start of each run
- Onboard a new project by auto-configuring Gleap integration using discovered tool schemas
