griptape-automation

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

Install

Hot:15

Download and extract to your skills directory

Copy command and send to OpenClaw for auto-install:

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

Griptape Automation Skills

Skill Overview


By automating Griptape task execution with Rube MCP, you can discover tools, manage connections, and perform batch operations without needing an API key.

Use Cases


  • Claude Code/MCP Client Integration: In AI clients that support MCP, call Griptape tools directly without additional API key configuration—just add the Rube MCP server endpoint to get started.
  • Batch Griptape Task Automation: Use RUBE_MULTI_EXECUTE_TOOL to execute multiple Griptape operations at once, suitable for scenarios that require handling large volumes of tasks, such as batch data processing and multi-workflow orchestration.
  • Dynamic Tool Discovery and Execution: When tool schemas may change, first use RUBE_SEARCH_TOOLS to retrieve the latest tool definitions, then execute the operations. This avoids call failures caused by hardcoding.
  • Core Features


  • Fast Connection Without a Key: Add https://rube.app/mcp as an MCP server, then manage Griptape connections via RUBE_MANAGE_CONNECTIONS—no API key required.
  • Dynamic Tool Discovery: Use RUBE_SEARCH_TOOLS to fetch the available tool list, input schema, and execution plan in real time, ensuring calls match the current API version.
  • Session-Based Batch Execution: Supports session reuse and memory parameter passing, allowing multiple related operations to be executed within the same session via RUBE_MULTI_EXECUTE_TOOL.
  • Common Questions

    Does Rube MCP require payment?


    Rube MCP is free to use; you only need to add the server endpoint. However, connecting to the Griptape service may require the appropriate permissions for your Griptape account, depending on Griptape’s pricing policies.

    Why must I call RUBE_SEARCH_TOOLS first?


    Griptape tool schemas can be updated at any time. Hardcoding tool definitions can cause calls to fail. RUBE_SEARCH_TOOLS returns the latest tool slugs, parameter structures, and known pitfalls to ensure successful execution.

    How do I verify whether the Griptape connection succeeded?


    After calling RUBE_MANAGE_CONNECTIONS, check whether the returned connection status is ACTIVE. If it’s not activated, it will return an authorization link—complete the authorization and the connection will work normally.