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

SKILL

ragic-automation

Name: ragic-automation
Author: Composio

Automate Ragic workflows via Rube MCP while checking current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is an open-source prompt-only wrapper and does not itself declare local execution or direct API key collection, so overall risk is relatively low. However, its real usage depends on remote Rube MCP and a subsequent Ragic authorization flow, which introduces third-party data egress and business-data access considerations.

CredentialsCaution

The material says 'No API keys needed,' but actual use requires creating a `ragic` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth flow through a returned auth link. So while no static secret is configured inside the skill, it still involves third-party account authorization/token handling, which carries normal credential-abuse exposure.

Network egressCaution

The README explicitly instructs users to add `https://rube.app/mcp` as an MCP server and to perform discovery, connection, and execution through Composio/Rube remote tools. This means task parameters, session data, and potentially Ragic operation data will be sent to the declared third-party service endpoint. No unrelated or hidden exfiltration endpoint is shown, but normal third-party data egress is present.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no local scripts, install commands, or instructions to spawn processes on the host. Its role is to guide use of existing MCP tools rather than directly obtaining local code-execution capability.

Data accessCaution

The skill’s purpose is to 'Automate Ragic operations' and it executes tools through an authorized Ragic connection. This means that, once authorized, the remote tool can read or modify Ragic business data as part of the workflow. The material does not show requests for local filesystem or unrelated system access, so this is data access aligned with the stated function.

Supply chainLow risk

The source is a public GitHub repository and is marked open-source, with strong community adoption (64.7k stars), which is a clear positive signal. The observed content is primarily README/prompt material, so auditability is relatively good. The missing license declaration and unknown maintenance status are worth noting, but they are not enough on their own to make this high risk.

Recommendations

Only add `https://rube.app/mcp` after verifying trust in Rube/Composio and reviewing their privacy/data-handling terms.
Use a least-privilege Ragic account or a test environment for authorization to avoid unnecessary data access.
Manually review the tool schemas and arguments returned by `RUBE_SEARCH_TOOLS` before execution to reduce the chance of accidental changes to production data.
Regularly review and revoke Ragic/Composio connections and session authorizations that are no longer needed.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Ragic Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ragic

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ragic"]
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 Ragic-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ragic`
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_