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

SKILL

gist-automation

Name: gist-automation
Author: Composio

Automate GitHub Gist creation, lookup, and management through Rube MCP.

Stars

★ 73,665

Source

GitHub

Updated

2026-08-28

// securityCaution

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

Summary

Overall this is a prompt/documentation-only skill with no keys and no declared remote endpoint; it is open source and widely used, so no concrete high-risk red flags are evident. The main caution is its reliance on Rube MCP/Composio connections, which introduces normal network and data-sharing boundaries.

CredentialsLow risk

No keys, tokens, or environment variables are required, and the material does not show any credential collection or forwarding logic, so credential misuse risk is low.

Network egressCaution

The skill uses Rube MCP/Composio external tool connections and explicitly asks to search tools and verify connection status first; this is normal networked behavior, but it does entail expected egress of task data to declared endpoints.

Code executionLow risk

This is a prompt-only skill with no shown ability to spawn local processes, run scripts, or invoke system commands, so no extra code-execution privilege is evident.

Data accessCaution

Its purpose is automating Gist operations, so it may read or modify related Gist data; however, there is no sign of overbroad access to local files or unrelated resources, making this expected-scope data access.

Supply chainCaution

The source is a GitHub open-source repository with high community adoption (64.7k stars), which materially lowers supply-chain risk; however, the license is unspecified and maintenance status is unknown, so some caution remains.

Recommendations

Enable this skill only when Gist automation is needed, and connect accounts following least-privilege principles.
Verify the actual data flow and authorization scope of Rube/Composio, and avoid sending unnecessary sensitive content.
Check tool schemas and connection status before use to prevent misuse or calling the wrong tool.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Composio tasks via Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_