Gist Automation

What This Skill Does

This skill automates operations within Gist using Composio's Gist toolkit via Rube MCP. It is designed for users who need to programmatically interact with Gist for tasks like creating and managing code snippets. The skill requires an active Gist connection and Rube MCP setup.

When to Use

• Create new Gists.
• Retrieve Gist content.
• Update existing Gists.
• List user's Gists.
• Automate code sharing.
• Manage code snippets programmatically.

Key Features

Uses Rube MCP for automation. Requires active Gist connection. Discovers available tools via RUBE_SEARCH_TOOLS. Checks connection status via RUBE_MANAGE_CONNECTIONS. Executes tools with RUBE_MULTI_EXECUTE_TOOL. Provides setup and usage instructions.

Manual Installation

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

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: {}

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

Powered by Composio