← LeaderboardThe Skill Leaderboard

agenty-automation

Skill file composio-skills/agenty-automation/SKILL.md in ComposioHQ/awesome-claude-skills. Read the publisher’s upstream source.

Description awaits a fresh source check.

Published by ComposioHQ ↗ComposioHQ/awesome-claude-skills

Try your first task

agenty-automation

Start a fresh conversation. Replace the highlighted placeholders.

Use agenty-automation to prepare and carry out [specific Agenty operation and target details] through an existing active Agenty connection using the current supported schema. Before any consequential external change, show the intended action and wait for my explicit confirmation; then return a concise result summary.

Required inputs

[specific Agenty operation and target details]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: agenty-automationdescription: "Automate Agenty tasks via Rube MCP (Composio). Always search tools first for current schemas."requires:   mcp: [rube]

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`