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

SKILL

retently-automation

Name: retently-automation
Author: Composio

Automate Retently feedback and survey workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill itself is an open-source prompt-only artifact and does not directly require local secrets, code execution, or file access. However, it is designed to route usage through remote Rube MCP and downstream Retently/Composio connections, so real use introduces external network access and third-party authorization, making it a low-to-moderate caution case rather than high risk.

CredentialsCaution

The material says 'No API keys needed,' but it also requires an ACTIVE `retently` connection via `RUBE_MANAGE_CONNECTIONS` and completion of an auth link. This indicates third-party account authorization/tokens are involved, even if the skill does not directly collect secrets or expose them as environment variables.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing operations through Composio's Retently toolkit. User task parameters, session IDs, and tool-call contents are therefore expected to be sent to these declared external services. The egress is clearly identified, with no evidence of unrelated or covert exfiltration in the provided material.

Code executionLow risk

The system marks it as prompt-only, and the content is mainly workflow guidance and usage instructions. The material does not show any requirement to install binaries locally, run scripts, spawn local processes, or request system-level execution privileges.

Data accessCaution

The skill does not declare local file read/write, but its purpose is to 'Automate Retently operations' and it supports bulk/workflow execution through remote tools. That implies access to and processing of data within the connected Retently account. Based on the material, there is no sign of local data permissions beyond its stated purpose.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (about 64.9k stars). The audited artifact itself is only a skill description rather than a closed-source executable payload. While the license is unspecified and maintenance status is unknown, the available positive signals keep overall supply-chain risk low.

Recommendations

Before connecting, verify the privacy policy, data handling scope, and revocation process for rube.app and Composio/Retently.
Authorize only the necessary Retently account/workspace, and prefer least privilege plus test data for validation.
Before using `RUBE_MULTI_EXECUTE_TOOL` or bulk operations, manually review the discovered tool schemas and the exact parameters to be sent.
Regularly review and revoke unused Retently/Composio connections and sessions.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Retently 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_CONNECTIONS with toolkit retently
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 retently
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_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 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

Automate ActiveCampaign tasks through Rube MCP for faster marketing operations.

ComposioGet→

$ loading_