grist-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/grist-automation --openclawGrist 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_CONNECTIONSwith toolkitgrist - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitgrist - 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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/grist-automation/SKILL.mdView on GitHub Overview
Grist Automation via Rube MCP lets you orchestrate Grist operations using Composio's Grist toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before each workflow to adapt to changes, and requires an active Rube MCP connection and Grist linkage.
How This Skill Works
The workflow starts by discovering available Grist tools with RUBE_SEARCH_TOOLS, then verifies the Grist connection is ACTIVE with RUBE_MANAGE_CONNECTIONS for toolkit grist. Finally, it executes the selected tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and session_id to preserve context.
When to Use It
- When you need to automate a repetitive Grist operation but want current tool schemas (no hardcoding).
- When establishing or validating a Grist connection before running any workflows.
- When performing a multi-step Grist task that requires discovering tools, then executing with a session.
- When handling paginated tool responses and continuing until complete.
- When performing bulk Grist actions or batches via remote bench tools.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Run RUBE_SEARCH_TOOLS to fetch current Grist tool schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit grist, then execute RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and memory payload.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing to get current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the grist toolkit.
- Use schema-compliant arguments with exact field names and types from the search results.
- Include a memory parameter (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls.
- Reuse session IDs within a workflow and handle pagination by continuing fetches as needed.
Example Use Cases
- Discover Grist operations tools with RUBE_SEARCH_TOOLS and automate creating or updating records using the returned tool slug.
- Validate a Grist schema change by re-running discovery and adapting automation to new fields.
- Connect to Grist and run a sequence of tools to populate a report, ensuring the connection remains ACTIVE.
- Execute a batch of Grist tasks via RUBE_MULTI_EXECUTE_TOOL with a persistent session and memory payload.
- Perform bulk Grist operations using RUBE_REMOTE_WORKBENCH to run multiple tools for a data import task.
