What is gist-automation?

A skill to automate Gist operations through Composio's Gist toolkit using Rube MCP, with safeguards to always fetch current schemas.

No API keys are required. You connect by adding the MCP endpoint (e.g., https://rube.app/mcp).

How do I ensure current schemas?

Always run RUBE_SEARCH_TOOLS first to fetch up-to-date tool slugs and input schemas; do not hardcode slugs or args.

gist-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Gist Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/gist

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Gist operations through Composio's Gist toolkit via Rube MCP. This skill orchestrates discovery, connection management, and execution of gist tasks, ensuring you always use current tool schemas. Refer to the toolkit docs at composio.dev/toolkits/gist.

How This Skill Works

Connect to Rube MCP and verify RUBE_SEARCH_TOOLS is available. Use RUBE_SEARCH_TOOLS to discover gist-related tools, then establish a gist connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments and memory context.

When to Use It

Automate routine gist tasks (create, update, delete) using up-to-date tool schemas.
Manage multiple gist connections across different accounts.
Perform bulk gist operations driven by discovered tool slugs and schemas.
Validate tool schemas and reuse sessions to streamline workflows.
Audit gist changes by stepping through a sequence of tool executions with a single session.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and connect to the gist toolkit with RUBE_MANAGE_CONNECTIONS; ensure the status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then execute a selected tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and arguments; include memory: {}.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Use exact field names and types from the discovery results for arguments.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow; generate new ones for new workflows.

Example Use Cases

Discover tools for Gist operations and execute an update across several gists using TOOL_SLUG_FROM_SEARCH with the required arguments.
Bulk-create new gists from a template by using a discovered create_gist tool and its schema.
Consolidate content from multiple gists into a summary by sequencing tools discovered via RUBE_SEARCH_TOOLS.
Migrate gist content between accounts by connecting to a second gist toolkit and performing the needed operations.
Schedule a weekly run to clean up or archive old gists by leveraging discovery-driven tool execution with a single session.

Frequently Asked Questions

Add this skill to your agents