Do I need API keys to use this skill?

No API keys are needed. Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and proceed with tool discovery and execution.

What if tool schemas change frequently?

Always fetch current definitions with RUBE_SEARCH_TOOLS before executing. Do not hardcode tool slugs or argument names.

How do I verify readiness before running a workflow?

Confirm that RUBE_SEARCH_TOOLS responds and that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools.

agiled-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/agiled-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Agiled Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/agiled

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["agiled"]
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 Agiled-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `agiled`
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/agiled-automation/SKILL.mdView on GitHub

Overview

Automate Agiled operations using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing any workflow, ensuring schema-compliant, up-to-date automation rather than hardcoding tool slugs.

How This Skill Works

Connect Rube MCP to an active Agiled toolkit and verify RUBE_SEARCH_TOOLS. Discover available tools and their input schemas, then confirm the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, exact argument names from the schema, a memory payload, and a session_id to maintain continuity.

When to Use It

You need to automate recurring Agiled tasks and want to ensure you always use the latest tool schemas
You are integrating Agiled operations into a larger automated pipeline that requires dynamic tool discovery
Tool schemas change frequently and you must fetch current definitions before execution
You want to validate and maintain a reliable connection to Agiled before running workflows
You need to reuse session IDs within a workflow or generate new ones for new workflows

Quick Start

Step 1: Add RUBE MCP endpoint (https://rube.app/mcp) as an MCP server and ensure prerequisites (RUBE_SEARCH_TOOLS available)
Step 2: Run RUBE_SEARCH_TOOLS with use_case set to 'Agiled operations' to discover current tools and schemas
Step 3: Choose a discovered tool_slug and run RUBE_MULTI_EXECUTE_TOOL with memory and a valid session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to fetch up-to-date tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before running any tools
Use exact field names and types from the RUBE_SEARCH_TOOLS results
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow and generate new ones for separate workflows

Example Use Cases

Nightly Agiled data import: discover tools with RUBE_SEARCH_TOOLS, then execute the required slug via RUBE_MULTI_EXECUTE_TOOL using the live schema
Multi-tool Agiled workflow orchestration: connect, search, and sequentially run multiple tools within a single session
Batch Agiled tasks with dynamic slugs: fetch current tool definitions and execute a batch using the discovered slugs
Pre-deployment validation: verify active connection before running a critical Agiled operation
Bulk operations: leverage RUBE_REMOTE_WORKBENCH and run_composio_tool for large-scale Agiled tasks

Frequently Asked Questions

Add this skill to your agents