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

SKILL

grist-automation

Name: grist-automation
Author: Composio

Automate Grist tables and data workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is primarily a prompt/orchestration document and does not itself declare local secrets, code execution, or direct file access. However, it is designed to rely on remote Rube MCP and a Grist connection that can trigger external tool actions, so the overall posture is low-to-moderate risk with attention mainly on network and third-party connection boundaries.

CredentialsCaution

The material states the skill itself requires no local keys, but actual use requires establishing a `grist` connection via `RUBE_MANAGE_CONNECTIONS` and completing an external auth link, which implies credentials exist within the Rube/Composio/Grist integration path. There is no explicit request for users to reveal raw secrets directly, so this is a typical third-party connection caution.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio's remote tool discovery/execution flow. Query contents, session IDs, and subsequent Grist operation requests are likely sent to that declared endpoint and its integration services, which is a normal egress pattern for this type of tool.

Code executionLow risk

Based on the material, this is a prompt-only skill description and does not declare local process spawning, script execution, binary installation, or elevated system permissions. The referenced execution occurs at the remote MCP/tool layer rather than as local code execution by the skill itself.

Data accessCaution

The skill does not declare direct local file read/write, but it can automate operations on external Grist tables/records through an authorized Grist toolkit. The effective data scope depends on the permissions granted in the Grist connection, and no obvious overreaching local data access is stated.

Supply chainLow risk

The source is a GitHub open-source repository, and the system marks it as open-source with 64.9k community trust, which are strong positive trust signals. The current material is mainly README/prompt content rather than an executable package; although license and maintenance status are unclear, that alone is not enough to raise it to high risk.

Recommendations

Only establish the connection after confirming trust in `rube.app/mcp`, Composio, and the target Grist workspace, and review the granted scopes.
Before using real data, validate the workflow with a least-privilege test Grist account to see what actions it actually performs.
Do not place unnecessary sensitive information in tool search parameters or session context.
Prefer to pin and review the actual callable Grist tools where possible, reducing misuse risk from the 'search first, then execute' pattern.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Grist Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/grist

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["grist"]
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 Grist-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `grist`
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 Gigasheet workflows and bulk spreadsheet-like data tasks via Rube MCP.

ComposioGet→

$ loading_