Open Skills Logo
Open Skills

spondyr-automation

Automate Spondyr tasks via Rube MCP (Composio). Always search tools first for current schemas.

Author

@ComposioHQ

Category

Development Tools

Install

Hot:34

Download and extract to your skills directory

Copy command and send to AI Agent for auto-install:

Download and install this skill https://openskills.cc/api/download?slug=composiohq-composio-skills-spondyr-automation&locale=en&source=copy

Spondyr Automation - Automate Spondyr Tasks via Rube MCP

Skills Overview


Spondyr Automation automates Spondyr operations through Composio’s Rube MCP, supporting tool discovery, connection management, and workflow execution.

Use Cases


  • Workflows that need to automate Spondyr task sending: Use RUBE_MULTI_EXECUTE_TOOL to batch-execute Spondyr actions, replacing repetitive manual work.

  • Spondyr tasks requiring MCP integration: No API key needed—connect to and execute operations from the Spondyr toolset directly via Rube MCP endpoints.

  • Scenarios needing dynamic tool architecture discovery: Use RUBE_SEARCH_TOOLS to fetch the current tool architecture in real time, avoiding hard-coded outdated configurations.

    • Core Capabilities


  • Tool Discovery & Architecture Retrieval: Dynamically query available Spondyr tools, input schemas, and recommended execution plans via RUBE_SEARCH_TOOLS to ensure the workflow still works when the tool architecture changes.

  • Connection Management: Use RUBE_MANAGE_CONNECTIONS to manage Spondyr connection status, including connection activation, status checks, and authentication flow.

  • Multi-Tool Execution: Execute multiple Spondyr tools within a single session using RUBE_MULTI_EXECUTE_TOOL, supporting session reuse and memory parameter management.

    • Frequently Asked Questions

    How do I get started with Spondyr Automation?


    First, add https://rube.app/mcp as an MCP server—no API key is required. Then call RUBE_SEARCH_TOOLS to verify Rube MCP availability. Next, use RUBE_MANAGE_CONNECTIONS to activate the Spondyr connection. Once the status is ACTIVE, you can start running workflows.

    Will the tool architecture change? How should I handle it?


    The Spondyr tool architecture may change. The design principle of Spondyr Automation is: “Always prioritize searching for tools.” Before each execution, call RUBE_SEARCH_TOOLS to retrieve the current architecture—do not hard-code tool slugs or parameters. This ensures the workflow continues to run correctly even when the architecture changes.

    Can I batch-execute Spondyr tasks?


    Yes. Use RUBE_MULTI_EXECUTE_TOOL to run multiple tools in a single call, or use RUBE_REMOTE_WORKBENCH together with run_composio_tool() for more complex batch operations. Note that the session ID can be reused within the workflow, but it must include a memory parameter (even if it’s an empty object {}).