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

SKILL

agenty-automation

Name: agenty-automation
Author: Composio

Automate Agenty tasks via Rube MCP after checking current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is primarily an open-source prompt/instruction document and does not itself require local secrets, code execution, or local data access. However, it is designed to route actions through remote Rube MCP/Composio and an Agenty connection, so the main concerns are the external service chain rather than the document itself.

CredentialsCaution

The material claims 'no API keys', but it explicitly requires establishing an Agenty connection via `RUBE_MANAGE_CONNECTIONS` and completing an external auth flow if inactive. This implies third-party account authorization/tokens are involved, even if the skill itself does not directly collect them. This is a normal external-connection credential scenario with no explicit signs of credential theft.

Network egressCaution

The README points to a remote MCP endpoint at `https://rube.app/mcp` and uses Composio/Rube to search tools, manage connections, and execute tools. User inputs and workflow parameters are therefore likely sent to these declared remote services. This is standard declared network behavior, and the material does not show exfiltration to unrelated or hidden endpoints.

Code executionLow risk

Per the system checks, this is prompt-only. The material does not include executable install scripts, shell commands, or requirements to start local processes; it only describes how to call existing MCP tools. No local code-execution privilege is requested by the skill itself.

Data accessLow risk

The document does not declare any ability to read/write local files, databases, or system resources, nor does it request filesystem permissions. Its apparent data plane is through remote Agenty/Composio workflows rather than direct access to local data.

Supply chainLow risk

The source is a GitHub open-source repository with very strong community adoption (64.7k stars), both of which materially reduce risk. The material itself is also just documentation rather than a binary or dependency package. The missing license declaration and unknown maintenance status are worth noting, but they do not by themselves justify a high-risk rating.

Recommendations

Before connecting, verify the privacy policy, data handling scope, and authorization domains for rube.app, Composio, and Agenty.
Grant only the minimum necessary permissions to the Agenty account and periodically review/revoke third-party connections.
Inspect the tool names, parameters, and target actions returned by `RUBE_SEARCH_TOOLS` before execution to avoid unintended high-impact operations.
Validate workflows in a test account or low-sensitivity environment before using production data.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Agenty Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/agenty

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["agenty"]
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 Agenty-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `agenty`
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_