retently-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/retently-automation --openclawRetently Automation via Rube MCP
Automate Retently operations through Composio's Retently toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/retently
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Retently connection via
RUBE_MANAGE_CONNECTIONSwith toolkitretently - 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 toolkitretently - 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: "Retently 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 Retently task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["retently"]
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 Retently-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit retently |
| 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/retently-automation/SKILL.mdView on GitHub Overview
Retently Automation via Rube MCP lets you automate Retently operations through Composio's Retently toolkit. It emphasizes using RUBE_SEARCH_TOOLS to fetch current tool schemas and requires an active Retently connection via RUBE_MANAGE_CONNECTIONS with the retently toolkit. Always discover tools first before running workflows to adapt to schema changes.
How This Skill Works
Connect to Rube MCP and verify tool schemas with RUBE_SEARCH_TOOLS. Establish an active Retently connection using RUBE_MANAGE_CONNECTIONS for the retently toolkit. Discover tools, then execute them with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id to maintain context across steps.
When to Use It
- You need to automate recurring Retently operations on a schedule or in response to events.
- Tool schemas may change and you must re-fetch current tool slugs and arguments before running.
- You want to verify and maintain an ACTIVE Retently connection prior to execution.
- You are integrating Retently tasks into broader automation workflows with session reuse.
- You plan to run bulk Retently actions by issuing multiple tools in a single workflow.
Quick Start
- Step 1: Add Retently MCP by configuring https://rube.app/mcp as an MCP server.
- Step 2: Run RUBE_SEARCH_TOOLS with use_case: "Retently operations" to fetch current tool schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkits: ["retently"], then RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and memory.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get up-to-date tool schemas.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the tool schemas returned by search.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
- Reuse session IDs within a workflow to preserve context and avoid re-authentication.
Example Use Cases
- Discover a Retently operation tool slug via RUBE_SEARCH_TOOLS and run it to export NPS scores using RUBE_MULTI_EXECUTE_TOOL.
- Establish a Retently connection with RUBE_MANAGE_CONNECTIONS then execute a tool to update a Retently workflow state.
- Chain multiple Retently tasks in a single workflow with RUBE_MULTI_EXECUTE_TOOL, passing memory between steps.
- Audit tool availability by fetching full schemas with RUBE_GET_TOOL_SCHEMAS and validate compatibility before running.
- Reuse an existing session across related Retently tasks to avoid repeated authentication in a sequence.
