$ ~/registry/skill/composiohq-composio-skills-griptape-automation

SKILL

griptape-automation

Name: griptape-automation
Author: Composio

Automate Griptape tasks through Rube MCP using current tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

The skill material itself is mainly a prompt/workflow guide for using Rube MCP/Composio, and its open-source, high-community-trust source lowers overall risk with no clear high-risk red flags. The main caveat is that it depends on an external MCP endpoint and subsequent Griptape connection, so actual data flow and permission scope depend on the remote services and granted account access.

CredentialsCaution

The material states the skill itself requires no API keys, but it requires establishing a `griptape` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link when the connection is not active. This means the skill does not directly take local secrets, but real usage may introduce third-party OAuth/account tokens, so the granted scopes and token custodian should be reviewed.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and then using Composio/Rube to search tools, manage connections, and execute tools; therefore user inputs, session IDs, tool arguments, and results are likely sent to that external service. No additional unrelated or covert destinations are described, but external network egress is clearly present.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description and does not include auditable local install scripts, shell commands, or local process-launch behavior. While it mentions `RUBE_MULTI_EXECUTE_TOOL`/`RUBE_REMOTE_WORKBENCH` for remote tool execution, it does not show direct local system execution permissions being requested.

Data accessCaution

The skill text itself does not declare local file read/write or direct access to local data; however, once remote tools are connected through Rube/Griptape, the actual accessible data scope will depend on the connected account, tool schema, and granted permissions. Because the README emphasizes discovering current schemas before execution, the data surface is dynamically determined and should be reviewed per tool before use.

Supply chainLow risk

The source is an open GitHub repository with high stated community adoption (64.7k stars), which materially lowers supply-chain risk; the material also appears to be documentation/prompt content rather than an executable binary. Caveats remain: no declared license, unknown maintenance status, and real operation depends on external Rube/Composio services, but these do not by themselves justify a high-risk rating.

Recommendations

Before connecting to `https://rube.app/mcp`, verify your organization permits sending prompts, parameters, and results to that third-party service.
When completing the `griptape` authorization flow, review the OAuth/connection scopes and grant only the minimum permissions needed.
Inspect the schema returned by `RUBE_SEARCH_TOOLS` before each execution to avoid sending unnecessary sensitive data to dynamically discovered tools.
Validate the skill in an isolated test environment before using it with production accounts or real business data.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "griptape-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/griptape-automation/SKILL.md
2. Save it as ~/.claude/skills/griptape-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Griptape Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/griptape

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["griptape"]
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 Griptape-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `griptape`
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

Automate Gleap feedback and task workflows through Rube MCP.

ComposioGet→

$ loading_