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

SKILL

grafbase-automation

Name: grafbase-automation
Author: Composio

Automate Grafbase workflows via Rube MCP with schema-aware tool discovery first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be primarily a prompt/workflow guide. It is open-source with strong community trust and declares no local secrets or direct remote endpoints, so overall risk is relatively low. However, actual operations depend on external Rube MCP and Grafbase connections, so real data egress and permission boundaries are determined by the connected MCP service and granted account access.

CredentialsCaution

The material says no API keys are needed to add Rube MCP, but it also requires establishing an active Grafbase connection via RUBE_MANAGE_CONNECTIONS and completing an auth-link flow. This suggests the skill itself does not directly request local secrets, but it relies on external account authorization, with token handling and scope not described in detail.

Network egressCaution

The documentation explicitly requires connecting to the remote MCP endpoint https://rube.app/mcp and performing actions through the Composio/Grafbase toolchain. User inputs, tool arguments, and results are likely relayed through that service. The egress target and purpose are aligned with the stated functionality, but the material does not provide detailed data-handling information.

Code executionLow risk

Based on the provided material, this is a prompt-style skill document that mainly instructs users to search for tools before calling existing MCP tools. It does not describe spawning local processes, running arbitrary scripts, or requesting system-level execution privileges.

Data accessCaution

The skill does not claim direct local file read/write access, but it can perform Grafbase automation/operations through an external MCP. The actual data scope depends on the discovered tools, the connected Grafbase account permissions, and the executed workflow; the material does not define a least-privilege boundary.

Supply chainLow risk

The source is an open-source GitHub repository with very high community adoption (64.7k stars), which is a strong risk-reducing signal. The visible content is more like README/prompt material than an executable package. Although the license and maintenance status are not clearly stated, there are no concrete supply-chain red flags in the provided material.

Recommendations

Before connecting, verify the privacy policy, log retention, and data-handling practices of rube.app/mcp and Composio.
Use a least-privilege Grafbase account/connection and grant only the scopes required for the intended tasks.
For first-time use, validate the exact tools and parameters in a low-sensitivity or test environment before running real workflows.
Regularly review external connection status and authorized sessions, and remove unused Grafbase integrations.

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 "grafbase-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/grafbase-automation/SKILL.md
2. Save it as ~/.claude/skills/grafbase-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Grafbase Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/grafbase

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["grafbase"]
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 Grafbase-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `grafbase`
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 Grist tables and data workflows through Rube MCP.

ComposioGet→

$ loading_