griptape-automation

Automate Griptape operations through the Rube MCP gateway for structured task execution.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill griptape-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: griptape-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/griptape-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill griptape-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of managing Griptape workflows by providing a standardized interface for tool discovery, connection management, and multi-step execution via the Rube MCP gateway.

Core Features & Use Cases

  • Dynamic Tool Discovery: Automatically fetch current tool schemas and execution plans using RUBE_SEARCH_TOOLS.
  • Connection Management: Verify and maintain active Griptape toolkit connections to ensure reliable workflow execution.
  • Multi-Step Execution: Orchestrate complex Griptape tasks by chaining tool calls with session-based memory management.

Quick Start

Use the griptape-automation skill to discover available tools and execute a Griptape workflow for your specific task.

Frequently Asked Questions about griptape-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Griptape tools?

Call the RUBE_SEARCH_TOOLS command with a specific use case query to retrieve available tool slugs, input schemas, and recommended execution plans for your Griptape task.

What should I do if my Griptape connection is inactive?

Use the RUBE_MANAGE_CONNECTIONS command with the 'griptape' toolkit parameter to check your status and follow the provided authentication link to re-establish an active connection.

Why must I call RUBE_SEARCH_TOOLS before executing?

Tool schemas and available slugs change frequently. Searching first ensures you use the most current arguments and field requirements, preventing execution errors caused by outdated hardcoded values.

Can I reuse session IDs for different workflows?

No, you should generate new session IDs for distinct workflows to maintain state isolation, though you should reuse the same session ID within the steps of a single workflow.